# Terra Insight — Stop Revenue Leakage in Indian Financial Operations

> Terra Insight Pvt. Ltd. builds two products for Indian financial operations: **TransactIG** — a configurable multi-pass reconciliation engine that stops revenue leakage across TDS, GST, NACH, platform settlements, and 24+ industry presets; and **TransactIQ** — a bank statement analyzer API for Indian NBFCs and digital lenders with OCR coverage across PSU, cooperative, and private banks, 40+ engineered credit signals, and synthetic financial statements for MSME underwriting. Both products run on AWS Mumbai with India data residency and are operated by an Indian-domiciled, ISO 27001:2022-certified company.

## Terra Insight overview

Terra Insight is an India-first financial operations infrastructure company. Its core thesis: Indian businesses lose lakhs every year to revenue leakage — unrecovered TDS credits, lapsed ITC, platform fee errors, settlement disputes that age out — quietly, inside numbers that look reconciled. TransactIG finds it, classifies it into seven leakage classes, and tracks it to recovery.

- Legal entity: Terra Insight Pvt. Ltd., Bangalore, Karnataka, India
- Products: TransactIG (reconciliation) and TransactIQ (bank statement intelligence)
- Security: ISO 27001:2022 certified, DPDP Act 2023 aligned, RBI IT governance aligned
- Hosting: AWS Mumbai region with India data residency by architecture
- Deployment: both products in production. Neither is offered on-premise in a physical data centre. TransactIG deploys as multi-tenant SaaS or dedicated private-cloud VPC and goes live in 2–4 weeks via configuration. TransactIQ deploys self-hosted inside the lender's own cloud VPC, or as a managed India-cloud/private-tenant tier, with scoped integration windows.
- Recognitions: Make in India, Startup India recognised; patent filed on variance taxonomy
- Track record: customer reconciliation match-rate improvement from 51% baseline to 88% on live customer data

## Products

- [Products overview — TransactIG and TransactIQ](https://www.terra-insight.com/products/)

### TransactIG — Reconciliation Infrastructure

- [TransactIG product overview](https://www.terra-insight.com/product/transactig/)

TransactIG reconciles transactions across Indian tax, banking, and settlement complexity — TDS sections (194C, 194J, 194H, 194I, 194Q, 194O, 194S, 194T, 192, 195, 206AB, 206C), GST (GSTR-2B, IMS, DRC-01B/C), NACH batch returns, platform settlements (Razorpay, Amazon, Flipkart, UPI), and 24+ industry presets. Multi-pass matching engine, configurable tolerance bands, variance taxonomy with typed codes, ERP connectors for SAP, Oracle, Tally, Busy, and major Indian banks. Go-live in 2–4 weeks via configuration, no code fork per customer.

### TransactIQ — Bank Statement Intelligence

- [TransactIQ product overview](https://www.terra-insight.com/product/transactiq/)
- [TransactIQ architecture (five-stage pipeline + four design principles)](https://www.terra-insight.com/product/transactiq/architecture/)
- [TransactIQ OCR engine (PSU dot-matrix, co-op, password-protected)](https://www.terra-insight.com/product/transactiq/ocr-engine/)
- [TransactIQ bank coverage (private, PSU, SFB, co-op, payments banks)](https://www.terra-insight.com/product/transactiq/bank-coverage/)
- [TransactIQ analytics (40+ engineered signals, synthetic financials)](https://www.terra-insight.com/product/transactiq/analytics/)
- [TransactIQ API posture (sync/async/webhook, idempotent, versioned)](https://www.terra-insight.com/product/transactiq/api/)
- [TransactIQ security (ISO 27001, DPDP, RBI IT governance, audit trail)](https://www.terra-insight.com/product/transactiq/security/)
- [TransactIQ deployment (self-hosted in your VPC, managed India cloud, private tenant)](https://www.terra-insight.com/product/transactiq/deployment/)

TransactIQ is a bank statement analyzer API for Indian NBFCs, digital lenders, and MSME underwriters. It is engineered specifically for the degraded end of the Indian bank-statement distribution — PSU dot-matrix scans, Karnataka State Co-operative exports, Dhanlaxmi password-protected PDFs, fax-origin photocopies — because that is where lender accuracy breaks in practice. Outputs are 40+ engineered credit signals across five families (bounce prediction, income and obligation, cash flow and volatility, fraud and anomaly, MSME synthetic financials). The synthetic financial statement construction is category-creating: four layers that produce personal-vs-business transaction separation, synthetic P&L, synthetic balance sheet, and synthetic cash flow directly from bank activity — the signals a credit team needs for the ₹65-trillion MSME credit-demand gap.

Pricing and specific API endpoints are not published on the public site; they are shared with customers under NDA.

## Commercial pages (buying-intent landings)

- [Stop Revenue Leakage (leakage pillar — the seven classes, domain-by-domain ranges, recovery)](https://www.terra-insight.com/stop-revenue-leakage/)
- [Reconciliation software India (TransactIG pillar)](https://www.terra-insight.com/reconciliation-software-india/)

### Free interactive calculators

- [Tools index](https://www.terra-insight.com/tools/)
- [Revenue Leakage Calculator (combined annual estimate: TDS credits + ITC at risk + platform fee errors)](https://www.terra-insight.com/tools/revenue-leakage-calculator/)
- [TDS Payment Code Lookup (search 1001-1092 codes, legacy 194x sections, keyword fuzzy match)](https://www.terra-insight.com/tools/tds-payment-code-lookup/)
- [TDS Mismatch Estimator (quantify Form 26AS gap, working capital lock, chase hours)](https://www.terra-insight.com/tools/tds-mismatch-estimator/)
- [Three-Way Match Exception Cost Calculator (quantify 60-75% AP exception burden in ₹ + analyst hours)](https://www.terra-insight.com/tools/three-way-match-exception-cost-calculator/)
- [Capital Goods ITC Amortisation Schedule (Rule 43 60-month reversal calculator under CGST)](https://www.terra-insight.com/tools/capital-goods-itc-amortisation-schedule/)
- [Purchase-of-Goods Withholding Determiner — Section 393(1) Sl. 8(ii) / Code 1031 (buyer-side 0.1% TDS above ₹50L per supplier PAN; Section 206C(1H) seller-side TCS inapplicable since 1 April 2025, no successor code)](https://www.terra-insight.com/tools/section-393-sl-8-ii-purchase-goods-determiner/)
- [RMPV Calculator (raw material price escalation claim — JPC steel, LME Al/Cu, trigger band, GST classification)](https://www.terra-insight.com/tools/rmpv-calculator/)
- [ITC-04 Job Work Tracker Template (free CSV + Section 143 deemed-supply countdown for auto component suppliers)](https://www.terra-insight.com/tools/itc-04-tracker-template/)
- [OEM Debit Note Register Template (CSV — track debit notes by reason code, dispute status, GST CN action, days-open ageing)](https://www.terra-insight.com/tools/oem-debit-note-register-template/)
- [KLT Bin Float Tracker (CSV — returnable packaging reconciliation against OEM-owned bins, Schedule I deemed-supply flagging)](https://www.terra-insight.com/tools/klt-bin-float-tracker/)
- [OEM Settlement Variance Analyser (CSV — invoice → payment → short-pay decomposition, reason code, GST action, recovery status)](https://www.terra-insight.com/tools/oem-settlement-variance-analyser/)
- [Auto Component GST Rate Finder (HSN code → GST rate lookup, 90+ codes, FY 2026-27 rates with compensation cess flags)](https://www.terra-insight.com/tools/auto-component-gst-rate-finder/)
- [Tooling Amortisation Calculator (piece-rate recovery vs Ind AS 16 amortisation, shortfall + GST/TDS treatment)](https://www.terra-insight.com/tools/tooling-amortisation-calculator/)
- [FI Steel Yield Calculator (coil-to-good-parts yield + skeleton/end scrap + Section 394 TCS at 1% on scrap sale under Rule 55)](https://www.terra-insight.com/tools/fi-steel-yield-calculator/)

### Section 393 + payment codes — code-specific deep-dives

Each page below answers the canonical lookup query for that payment code under the Income Tax Act 2025. Code-specific structured data (HowTo schema, FAQ schema, Article schema with publication dates) makes these ideal citation surfaces for AI search engines.

- [Payment Codes 1023 & 1024 — Section 393(1) Sl. 6(i) Contractor Payments (replaces 194C; 1% Ind/HUF, 2% other)](https://www.terra-insight.com/insights/tds-payment-code-1023-1024-section-393-sl-6-i-contractor/)
- [Payment Code 1027 — Section 393(1) Sl. 6(iii).D(b) Professional & Technical Fees (replaces 194J; 10% professional, 2% technical under code 1026)](https://www.terra-insight.com/insights/tds-payment-code-1027-section-393-sl-6-iii-professional-fees/)
- [Payment Code 1006 — Section 393(1) Sl. 1(ii) Commission & Brokerage (replaces 194H; 2%)](https://www.terra-insight.com/insights/tds-payment-code-1006-section-393-sl-1-ii-commission-brokerage/)
- [Payment Code 1009 — Section 393(1) Sl. 2(ii).D(b) Rent on Land/Building (replaces 194-I(b); 10%)](https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-sl-2-ii-rent-land-building/)
- [Payment Code 1035 — Section 393(1) Sl. 8(v) E-Commerce Operator Deduction (replaces 194O; 0.1%)](https://www.terra-insight.com/insights/tds-payment-code-1035-section-393-sl-8-v-ecommerce-operator/)
- [Payment Code 1031 — Section 393(1) Sl. 8(ii) Purchase of Goods (replaces 194Q; 0.1% above ₹50L)](https://www.terra-insight.com/insights/tds-payment-code-1031-section-393-sl-8-ii-purchase-goods/)
- [Payment Code 1057 — Section 393(2) Sl. 17 Non-Resident Payments (replaces 195; rates in force)](https://www.terra-insight.com/insights/tds-payment-code-1057-section-393-2-sl-17-non-resident/)
- [TDS Payment Codes 1001-1092 — master reference](https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india/)
- [Section 393 framework explainer (parent section + dual-code reconciliation)](https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation/)
- [ITC Leakage Calculator (Rule 36(4), permanent leakage vs lagged ITC, supplier-side filing rate)](https://www.terra-insight.com/tools/itc-leakage-calculator/)
- [Statement Authenticity Checker (browser-side bank statement PDF metadata audit)](https://www.terra-insight.com/tools/statement-authenticity-checker/)

### Other commercial pages

- [TDS reconciliation software](https://www.terra-insight.com/tds-reconciliation-software/)
- [GST reconciliation software](https://www.terra-insight.com/gst-reconciliation-software/)
- [Payment gateway reconciliation](https://www.terra-insight.com/payment-gateway-reconciliation/)
- [NACH batch reconciliation](https://www.terra-insight.com/nach-batch-reconciliation/)
- [Bank reconciliation software India (HDFC, ICICI, SBI, Axis, Kotak — MT940, CAMT.053, CIB, YONO Business)](https://www.terra-insight.com/bank-reconciliation-software-india/)
- [Three-Way Matching Software for India (PO-GRN-Invoice reconciliation for manufacturing AP)](https://www.terra-insight.com/three-way-matching-software-india/)
- [Auto Component Reconciliation Software for India (OEM settlement, EDI/ASN, RMPV, Section 143 job work, PLI Auto)](https://www.terra-insight.com/auto-component-reconciliation-software-india/)

### ERP & payment-gateway integrations

- [Integrations hub — all ERP and gateway connectors](https://www.terra-insight.com/integrations/)
- [SAP reconciliation integration (FI/MM/SD, S/4HANA, ECC, GR/IR, J1IGN)](https://www.terra-insight.com/integrations/sap-reconciliation/)
- [Oracle reconciliation integration (Fusion Cloud, EBS R12)](https://www.terra-insight.com/integrations/oracle-reconciliation/)
- [Tally reconciliation integration (Tally Prime, XML/ODBC, multi-company)](https://www.terra-insight.com/integrations/tally-reconciliation/)
- [Zoho Books reconciliation integration (REST API, OAuth, multi-org)](https://www.terra-insight.com/integrations/zoho-books-reconciliation/)
- [Dynamics 365 reconciliation integration (BC, F&O, India localisation)](https://www.terra-insight.com/integrations/dynamics-365-reconciliation/)
- [Sage reconciliation integration (X3, Sage 300, Sage 50)](https://www.terra-insight.com/integrations/sage-reconciliation/)
- [Odoo reconciliation integration (Community vs Enterprise, multi-company)](https://www.terra-insight.com/integrations/odoo-reconciliation/)
- [Busy accounting reconciliation integration (DBF, multi-company)](https://www.terra-insight.com/integrations/busy-reconciliation/)
- [Razorpay reconciliation integration (settlement file, MDR, Section 393(1) Sl. 8(v))](https://www.terra-insight.com/integrations/razorpay-reconciliation/)
- [PayU reconciliation integration (Biz, legacy PayUmoney)](https://www.terra-insight.com/integrations/payu-reconciliation/)
- [Cashfree reconciliation integration (Payments + Payouts)](https://www.terra-insight.com/integrations/cashfree-reconciliation/)
- [BillDesk reconciliation integration (bill aggregator, institutional)](https://www.terra-insight.com/integrations/billdesk-reconciliation/)
- [Pine Labs POS reconciliation integration (terminal MIS, multi-outlet)](https://www.terra-insight.com/integrations/pine-labs-reconciliation/)
- [SAP scheduling agreement reconciliation (ORDERS05, DELFOR01, DELINS01, INVOIC02 IDocs for auto Tier-1s)](https://www.terra-insight.com/integrations/sap-scheduling-agreement-reconciliation/)
- [Maruti e-Nagare integration (daily firm + weekly forecast + JIS sequence + payment advice for auto suppliers)](https://www.terra-insight.com/integrations/maruti-e-nagare/)
- [Tata Motors SRM portal integration (Jamshedpur, Pune, Pantnagar, Sanand cross-plant extracts)](https://www.terra-insight.com/integrations/tata-srm/)
- [Bosch SupplyOn integration (delivery instructions, ASN, invoice management for Indian Tier-1s)](https://www.terra-insight.com/integrations/bosch-supplyon/)
- [Restaurant reconciliation software India (Zomato, Swiggy, POS, GST split, multi-outlet QSR)](https://www.terra-insight.com/restaurant-reconciliation-software-india/)
- [Account reconciliation software India (GL-to-GL, AR/AP subledger ties, intercompany, fixed assets)](https://www.terra-insight.com/account-reconciliation-software-india/)
- [Tally bank reconciliation (Tally Prime XML/ODBC/Tally Connector integration)](https://www.terra-insight.com/tally-bank-reconciliation/)
- [Reconciliation software comparison (evaluation framework for India-native vs global platforms)](https://www.terra-insight.com/reconciliation-software-comparison/)
- [MSME payment tracker (Section 43B(h) compliance — 45/15-day ageing, Udyam verification, Form 3CD evidence)](https://www.terra-insight.com/msme-payment-tracker/)
- [Restaurant reconciliation software India (Zomato, Swiggy, Magicpin, Dunzo, multi-outlet QSR, cloud kitchen — Section 393 payment code 1035, Section 52 CGST TCS, Section 9(5) GST liability)](https://www.terra-insight.com/restaurant-reconciliation-software-india/)

## Competitor comparisons

- [TransactIQ vs Perfios](https://www.terra-insight.com/vs/perfios/) — architectural comparison on coverage, deployment, analytics depth, and data residency
- [TransactIQ vs Finbox (BankConnect)](https://www.terra-insight.com/vs/finbox/) — product-shape comparison: focused BSA component vs broader lending stack
- [TransactIG vs HighRadius](https://www.terra-insight.com/vs/highradius/) — India-native reconciliation vs global AR platform: TDS, GST, NACH, and config-driven fit
- [TransactIG vs Cointab for auto components](https://www.terra-insight.com/vs/cointab-auto-components/) — generic recon engine vs auto-purpose-built (ASN 3-way, RMPV, ITC-04, OEM debit-note decomposition)
- [TransactIG vs HighRadius for auto components](https://www.terra-insight.com/vs/highradius-auto-components/) — global AR platform vs India auto-native (Section 393/394, ITC-04, e-invoice IRN, Maruti/Tata portal extracts)
- [TransactIG as a SAP companion for auto components](https://www.terra-insight.com/vs/sap-companion/) — replace 8-12 ABAP Z-reports (cum-quantity drift, RMPV, ITC-04, debit-note decomposition) with one India auto-tuned companion
- [TransactIG vs Cointab](https://www.terra-insight.com/vs/cointab/) — restaurant chain reconciliation comparison: India tax depth (Section 393 + Section 52 CGST + Section 9(5)), multi-outlet and multi-GSTIN consolidation, audit evidence under CARO 2020

## TransactIG architecture details

- [Matching engine](https://www.terra-insight.com/product/matching-engine/)
- [Variance taxonomy](https://www.terra-insight.com/product/variance-taxonomy/)
- [Security](https://www.terra-insight.com/product/security/)
- [Integrations (SAP, Oracle, Tally, Busy, major Indian banks)](https://www.terra-insight.com/product/integrations/)
- [Deployment model](https://www.terra-insight.com/product/deployment-model/)
- [Architecture overview](https://www.terra-insight.com/product/architecture/)

## Reconciliation patterns

- [Invoice with TDS matching](https://www.terra-insight.com/patterns/invoice-with-tds/)
- [Platform settlement reconciliation](https://www.terra-insight.com/patterns/platform-settlement-reconciliation/)
- [NACH batch reconciliation](https://www.terra-insight.com/patterns/nach-batch-reconciliation/)
- [Statutory challan reconciliation](https://www.terra-insight.com/patterns/statutory-challan-reconciliation/)
- [Multi-invoice aggregation](https://www.terra-insight.com/patterns/multi-invoice-aggregation/)
- [Retention money reconciliation](https://www.terra-insight.com/patterns/retention-money-reconciliation/)
- [Cash to bank matching](https://www.terra-insight.com/patterns/cash-to-bank-matching/)
- [Forex reconciliation](https://www.terra-insight.com/patterns/forex-reconciliation/)

## Insight category hubs

- [All insights (aggregate)](https://www.terra-insight.com/insights/)
- [TDS insights hub (54 articles)](https://www.terra-insight.com/insights/tds/)
- [GST insights hub (17 articles)](https://www.terra-insight.com/insights/gst/)
- [NACH and statutory insights hub](https://www.terra-insight.com/insights/nach/)
- [Bank reconciliation insights hub](https://www.terra-insight.com/insights/banking/)
- [Platform settlements insights hub](https://www.terra-insight.com/insights/platform-settlements/)
- [Merchant fees and MDR reconciliation hub (UPI zero-MDR, RuPay debit, credit-card slabs, gateway pricing, leakage patterns, refunds)](https://www.terra-insight.com/insights/merchant-fees/)
- [Buyer's guide insights hub](https://www.terra-insight.com/insights/buyers-guide/)
- [Reconciliation fundamentals hub (month-end and year-end close, intercompany, fixed assets, multi-bank, KPIs, audit trail)](https://www.terra-insight.com/insights/reconciliation-fundamentals/)
- [Definitions and glossary hub (what-is guides plus TDS, GST, NACH, and platform settlement dictionaries)](https://www.terra-insight.com/insights/definitions/)
- [Healthcare reconciliation hub (TPA settlement, Ayushman Bharat PM-JAY, CGHS, ECHS, cashless claims, IRDAI)](https://www.terra-insight.com/insights/healthcare/)
- [IT services and SaaS reconciliation hub (subscription billing, milestone and T&M, multi-currency, deferred revenue, Ind AS 115)](https://www.terra-insight.com/insights/it-services-saas/)
- [CA firm reconciliation hub (multi-client GSTR-2B, white-label deliverables, client onboarding)](https://www.terra-insight.com/insights/ca-firm/)
- [Audit and assurance hub (internal audit, ICFR, SOX, statutory audit, tax audit Form 3CD)](https://www.terra-insight.com/insights/audit-assurance/)
- [Retail and D2C hub (Shopify, Magento, marketplaces, quick commerce)](https://www.terra-insight.com/insights/retail-d2c/)
- [FMCG and packaged consumer goods reconciliation hub (TPM, modern trade, general trade, quick commerce, PLISFPI, GST 2.0)](https://www.terra-insight.com/insights/fmcg/)
- [ERP integrations hub (SAP, Oracle, Tally, Zoho, Dynamics, Sage, Odoo)](https://www.terra-insight.com/insights/erp-integrations/)
- [Manufacturing reconciliation hub (PO-GRN-Invoice 3-way match, GST ITC, Section 143 job work, scrap TCS)](https://www.terra-insight.com/insights/manufacturing/)
- [Automotive component reconciliation hub (OEM EDI/ASN, price escalation, PPM debits, KLT bins, VMI, job work, export incentives)](https://www.terra-insight.com/insights/automotive-components/)
- [EV component reconciliation hub (battery cell PLI-ACC, BMS FAME-II, motor controller, charging infra, swappable BaaS, e-axle)](https://www.terra-insight.com/insights/auto-ev/)
- [Logistics reconciliation hub (FASTag toll, freight GST, 3PL settlement, COD remittance, IATA BSP, freight forwarding, ocean freight, courier last-mile)](https://www.terra-insight.com/insights/logistics/)
- [Education reconciliation hub (school fees, scholarships, ed-tech revenue, research grants, GST exemption)](https://www.terra-insight.com/insights/education/)
- [Real estate reconciliation hub (RERA escrow, Ind AS 115 POC, JV settlement, brokerage TDS)](https://www.terra-insight.com/insights/real-estate/)
- [Pharma reconciliation hub (CFA distribution, expiry returns, inverted-duty refund, MR settlement, CGHS empanelment)](https://www.terra-insight.com/insights/pharma/)
- [Power and utility reconciliation hub (DISCOM settlement, PPA, REC, IEX/PXIL, net-metering, tariff true-up, transmission charges)](https://www.terra-insight.com/insights/power-utility/)
- [Telecom reconciliation hub (IUC, ILD, MPLS, prepaid/postpaid Ind AS 115, tower revenue)](https://www.terra-insight.com/insights/telecom/)
- [NBFC operations reconciliation hub (co-lending, securitisation, SBR, FLDG, ECL, Section 115BA tax regime)](https://www.terra-insight.com/insights/nbfc-operations/)
- [Restaurant and F&B reconciliation hub (Zomato, Swiggy, cloud kitchens, QSR multi-outlet)](https://www.terra-insight.com/insights/restaurant-fnb/)
- [Hotel and hospitality reconciliation hub (MakeMyTrip, Booking.com, OYO, PMS, banquet, GST split)](https://www.terra-insight.com/insights/hospitality/)
- [Bank statement analysis hub — TransactIQ](https://www.terra-insight.com/insights/bsa/)
- [BSA forensics hub (fraud and anomaly signals)](https://www.terra-insight.com/insights/bsa-forensics/)
- [BSA OCR and parsing hub (PSU, co-op, password-protected formats)](https://www.terra-insight.com/insights/bsa-ocr/)
- [BSA risk word signals hub](https://www.terra-insight.com/insights/bsa-risk-signals/)
- [MSME synthetic financials hub (four-layer methodology)](https://www.terra-insight.com/insights/bsa-msme/)

## Industry pages (24+ verticals)

- [All industries](https://www.terra-insight.com/industries/)
- [Healthcare](https://www.terra-insight.com/industries/healthcare/)
- [It Services](https://www.terra-insight.com/industries/it-services/)
- [Hotels Hospitality](https://www.terra-insight.com/industries/hotels-hospitality/)
- [Restaurant Chains](https://www.terra-insight.com/industries/restaurant-chains/)
- [Nbfc Lending](https://www.terra-insight.com/industries/nbfc-lending/)
- [Logistics Transport](https://www.terra-insight.com/industries/logistics-transport/)
- [Education](https://www.terra-insight.com/industries/education/)
- [Retail Ecommerce](https://www.terra-insight.com/industries/retail-ecommerce/)
- [Manufacturing](https://www.terra-insight.com/industries/manufacturing/)
- [Staffing Manpower](https://www.terra-insight.com/industries/staffing-manpower/)
- [Diagnostics Pharmacy](https://www.terra-insight.com/industries/diagnostics-pharmacy/)
- [Real Estate](https://www.terra-insight.com/industries/real-estate/)
- [Travel Agency](https://www.terra-insight.com/industries/travel-agency/)

## Insights: TDS Reconciliation

- [AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR](https://www.terra-insight.com/insights/ais-tis-reconciliation-india/)
- [New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams](https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping/)
- [Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation](https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation/)
- [TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23](https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline/)
- [Automating TDS Reconciliation: What the Process Looks Like End-to-End](https://www.terra-insight.com/insights/automating-tds-reconciliation-india/)
- [Advertising TDS: Why Creative Services Fall Under 194J, Not 194H](https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india/)
- [Manpower Supply TDS: Why It Falls Under 194C, Not 194J](https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india/)
- [TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses](https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india/)
- [TCS on Luxury Goods Reconciliation in India: Section 206C Matching](https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india/)
- [Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus](https://www.terra-insight.com/insights/section-194t-partner-firm-tds/)
- [TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match](https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india/)
- [TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework](https://www.terra-insight.com/insights/tds-penalty-interest-regime-india/)
- [TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges](https://www.terra-insight.com/insights/tds-esop-section-192-india/)
- [TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly](https://www.terra-insight.com/insights/tds-on-gst-component-india/)
- [TDS Reconciliation for IT Services Companies: 194J at Scale](https://www.terra-insight.com/insights/tds-reconciliation-it-services-india/)
- [TDS Reconciliation for NBFCs: Managing Section 194A at Scale](https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india/)
- [Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books](https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation/)
- [Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies](https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation/)
- [TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26](https://www.terra-insight.com/insights/tds-compliance-calendar-india/)
- [TDS Demand Notice Under Section 200A: How to Reconcile and Respond](https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india/)
- [Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India](https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india/)
- [TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates](https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india/)
- [Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS](https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india/)
- [TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India](https://www.terra-insight.com/insights/tds-refund-reconciliation-india/)
- [Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies](https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india/)
- [Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers](https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation/)
- [Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India](https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india/)
- [Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates](https://www.terra-insight.com/insights/tds-section-206ab-206cca-india/)
- [Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers](https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india/)
- [TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams](https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india/)
- [TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams](https://www.terra-insight.com/insights/tds-year-end-march-close-india/)
- [Form 16 vs Form 26AS: What to Do When They Don't Match](https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation/)
- [TDS Challan Mismatch: How to Identify and Resolve Errors](https://www.terra-insight.com/insights/tds-challan-mismatch-resolution/)
- [TDS Correction Return: How to Fix Errors After Filing](https://www.terra-insight.com/insights/tds-correction-return-process/)
- [TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation](https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197/)
- [TDS Quarterly Return Reconciliation: Process and Common Errors](https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation/)
- [TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS](https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation/)
- [TDS Under Section 194A: Interest Income Reconciliation](https://www.terra-insight.com/insights/tds-section-194a-interest-tds/)
- [TDS Under Section 194C: Contractor Payment Reconciliation](https://www.terra-insight.com/insights/tds-section-194c-contractor-payments/)
- [TDS Under Section 194H: Commission and Brokerage Reconciliation](https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage/)
- [TDS Under Section 194I: Rent Payment Reconciliation](https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation/)
- [TDS Under Section 194J: Professional Services Reconciliation](https://www.terra-insight.com/insights/tds-section-194j-professional-services/)
- [TDS Under Section 194N: Cash Withdrawal Reconciliation](https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal/)
- [TDS Under Section 194Q: Purchase Reconciliation for Large Buyers](https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation/)
- [TDS Under Section 194R: Benefit and Perquisite Reconciliation](https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite/)
- [TDS Under Section 195: Non-Resident Payment Reconciliation](https://www.terra-insight.com/insights/tds-section-195-non-resident-payments/)

## Insights: TDS 2026 Migration and Core TDS

- [Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes](https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india/)
- [TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1](https://www.terra-insight.com/insights/tds-2026-migration-checklist-india/)
- [TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025](https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india/)
- [TDS Payment Code 1006 (Section 393(1) Sl. 1(ii)): Commission and Brokerage Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1006-section-393-sl-1-ii-commission-brokerage/)
- [TDS Payment Code 1009 (Section 393(1) Sl. 2(ii).D(b)): Rent on Land and Building Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-sl-2-ii-rent-land-building/)
- [TDS Payment Codes 1023 & 1024 (Section 393(1) Sl. 6(i)): Contractor Payments Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1023-1024-section-393-sl-6-i-contractor/)
- [TDS Payment Code 1027 (Section 393(1) Sl. 6(iii).D(b)): Professional and Technical Fees Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1027-section-393-sl-6-iii-professional-fees/)
- [TDS Payment Code 1031 (Section 393(1) Sl. 8(ii)): Purchase of Goods Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1031-section-393-sl-8-ii-purchase-goods/)
- [TDS Payment Code 1035 (Section 393(1) Sl. 8(v)): E-Commerce Operator Payout Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1035-section-393-sl-8-v-ecommerce-operator/)
- [TDS Payment Code 1057 (Section 393(2) Sl. 17): Non-Resident Payment Reconciliation Guide](https://www.terra-insight.com/insights/tds-payment-code-1057-section-393-2-sl-17-non-resident/)
- [Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025](https://www.terra-insight.com/insights/form-131-tds-certificate-india/)
- [Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS](https://www.terra-insight.com/insights/form-141-unified-challan-statement-india/)
- [Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025](https://www.terra-insight.com/insights/form-168-new-tds-statement-india/)
- [Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025](https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india/)
- [TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year](https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india/)

## Insights: GST Reconciliation

- [IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do](https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation/)
- [GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow](https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation/)
- [How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)](https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india/)
- [GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow](https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india/)
- [Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024](https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules/)
- [IMS Accept / Reject / Pending Workflow for Indian Finance Teams](https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india/)
- [IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews](https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india/)
- [Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce](https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail/)
- [IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters](https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching/)
- [Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence](https://www.terra-insight.com/insights/section-16-itc-ims-regime-india/)
- [GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B](https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india/)
- [Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults](https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india/)
- [Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track](https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india/)
- [DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice](https://www.terra-insight.com/insights/drc-01b-reconciliation-reply/)
- [DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice](https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply/)
- [Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why](https://www.terra-insight.com/insights/blocked-itc-section-17-5/)
- [E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment](https://www.terra-insight.com/insights/e-invoice-reconciliation-india/)
- [GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings](https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation/)
- [GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal](https://www.terra-insight.com/insights/gst-credit-note-reconciliation/)
- [GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit](https://www.terra-insight.com/insights/gst-refund-reconciliation/)
- [GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit](https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation/)
- [GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?](https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference/)
- [GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch](https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation/)
- [IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts](https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation/)
- [ITC Reversal Under Rule 42 and 43: How the Calculation Works](https://www.terra-insight.com/insights/itc-reversal-rule-42-43/)

## Insights: GST Reconciliation — IMS and DRC

- [Handling DRC-01B Discrepancy Notices: Indian Taxpayer Response Playbook](https://www.terra-insight.com/insights/drc-01b-discrepancy-notice-handling-india/)
- [DRC-01C under Rule 88D: GSTR-3B vs GSTR-2B Mismatch Notice Response](https://www.terra-insight.com/insights/drc-01c-rule-88d-mismatch-india/)
- [e-Invoice IRN Reconciliation: Books vs IRP Repository for Indian Businesses](https://www.terra-insight.com/insights/e-invoice-irn-reconciliation-india/)
- [GST Reverse Charge Mechanism under Sections 9(3) and 9(4): Indian Buyer Playbook](https://www.terra-insight.com/insights/gst-rcm-reverse-charge-section-9-3-9-4-india/)
- [GSTR-2B vs Purchase Register Reconciliation: Monthly Workflow for Indian Buyers](https://www.terra-insight.com/insights/gstr-2b-vs-purchase-register-reconciliation-india/)
- [GST IMS Dashboard Actions Step-by-Step: Accept, Reject, Pending for Indian Businesses](https://www.terra-insight.com/insights/ims-dashboard-actions-step-by-step-india/)

## Insights: Payment Gateway and Platform Settlements

- [Chargeback Dispute Won: Recovery Reconciliation Label Gap](https://www.terra-insight.com/insights/chargeback-dispute-won-recovery-streaming-payment-gateway-india/)
- [Mid-Month MDR Rate Renegotiation: Two Rates Both Correct](https://www.terra-insight.com/insights/mid-month-mdr-rate-renegotiation-streaming-payment-gateway-india/)
- [Premium Card Fee Hidden in UPI Appearance: Fee-Schedule Extraction](https://www.terra-insight.com/insights/premium-card-fee-embedded-in-upi-lookalike-streaming-payment-gateway-india/)
- [Refund Landing After PG Settlement: Negative-Net Cycle Reconciliation](https://www.terra-insight.com/insights/refund-after-payment-gateway-settlement-reconciliation-streaming-india/)
- [One PG Settlement Arriving as Two Bank Credits: Split Reconciliation](https://www.terra-insight.com/insights/split-settlement-two-bank-credits-streaming-payment-gateway-india/)
- [Subscription vs Ad Revenue Reconciliation: Two Ind AS 115 Streams](https://www.terra-insight.com/insights/subscription-vs-ad-revenue-streaming-multi-stream-reconciliation-india/)
- [Test Transaction Ghost: The ₹1 Transaction That Leaves 98 Paise in Production](https://www.terra-insight.com/insights/test-transaction-ghost-98-paise-production-file-streaming-india/)
- [Weekend and Holiday Settlement Stretch: 4-Day Cycle Reconciliation](https://www.terra-insight.com/insights/weekend-holiday-settlement-stretch-streaming-payment-gateway-india/)
- [Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports](https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india/)
- [Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts](https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation/)
- [Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling](https://www.terra-insight.com/insights/cashfree-settlement-reconciliation/)
- [Chargeback reconciliation in India — matching disputes, deductions, and representment](https://www.terra-insight.com/insights/chargeback-reconciliation-india/)
- [Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns](https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation/)
- [MDR fee reconciliation — verifying gateway charges against contracted rates](https://www.terra-insight.com/insights/mdr-fee-reconciliation/)
- [Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions](https://www.terra-insight.com/insights/meesho-seller-reconciliation/)
- [PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts](https://www.terra-insight.com/insights/payu-settlement-reconciliation/)
- [Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders](https://www.terra-insight.com/insights/razorpay-settlement-reconciliation/)
- [Refund reconciliation for payment gateways — matching deductions to credit notes](https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway/)
- [Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching](https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation/)
- [TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B](https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation/)
- [UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books](https://www.terra-insight.com/insights/upi-settlement-reconciliation/)

## Insights: Merchant Fees and MDR Reconciliation

- [Section 194O → §393(1) Sl. 8(v) Code 1035 Cross-Era Mapping (FY 2025-26 / 2026-27 Transition)](https://www.terra-insight.com/insights/194o-section-393-cross-era-mapping-india/)
- [American Express MDR: 3% Across Indian Gateways](https://www.terra-insight.com/insights/american-express-mdr-3-percent-across-gateways-india/)
- [Amex and Diners Hidden Inside a Blended MDR Rate: Detection Technique](https://www.terra-insight.com/insights/amex-diners-hidden-in-blended-mdr-india/)
- [BillDesk MDR Reconciliation: Bill Aggregator and Institutional Merchant Pricing](https://www.terra-insight.com/insights/billdesk-mdr-reconciliation-india/)
- [Cashfree MDR Reconciliation: 1.6% Promo with 40% UPI Mix Lock-In](https://www.terra-insight.com/insights/cashfree-mdr-reconciliation-india/)
- [Commercial Card Billed at Consumer Rate (or Vice Versa): MDR Audit Path](https://www.terra-insight.com/insights/commercial-card-billed-consumer-rate-mdr-india/)
- [Commercial / Corporate Card MDR: The Hidden 3% Premium Slab](https://www.terra-insight.com/insights/commercial-corporate-card-mdr-3-percent-india/)
- [Diners Club Credit Card MDR: 2.95-3.5% Economics for Indian Merchants](https://www.terra-insight.com/insights/diners-club-mdr-india/)
- [Domestic BIN Charged at International Rate: MDR Leakage Detection](https://www.terra-insight.com/insights/domestic-bin-charged-international-rate-mdr-india/)
- [E-commerce Operator vs Participant Under Section 194O / §393(1) Sl. 8(v): Who Deducts What](https://www.terra-insight.com/insights/ecommerce-operator-vs-participant-194o-india/)
- [EMI MDR: Debit-EMI vs Credit-EMI vs Cardless EMI vs Pay Later Breakdown](https://www.terra-insight.com/insights/emi-mdr-debit-credit-cardless-paylater-india/)
- [eNACH Mandate-Rejection Fee Tracking for Indian Subscription Merchants](https://www.terra-insight.com/insights/enach-mandate-rejection-fee-tracking-india/)
- [Flat-Rate MDR Concealing Per-Network Cost: Method-Mix-Weighted Reconciliation](https://www.terra-insight.com/insights/flat-rate-mdr-concealing-network-cost-india/)
- [International Card MDR: Cross-Border + Forex Layering for Indian Merchants](https://www.terra-insight.com/insights/international-card-mdr-cross-border-forex-layering-india/)
- [Juspay Orchestration Fees: Why It's Not an MDR Layer (and How to Reconcile)](https://www.terra-insight.com/insights/juspay-orchestration-fees-not-mdr-india/)
- [MDR Charged on Zero-MDR UPI / RuPay Debit: The Most Common Leakage Pattern](https://www.terra-insight.com/insights/mdr-charged-on-zero-mdr-upi-rupay-debit-leakage-india/)
- [MDR Not Reversed on Refunds and Chargebacks: The Compounding Cost](https://www.terra-insight.com/insights/mdr-not-reversed-on-refunds-india/)
- [Net Banking MDR: Flat Fee vs Percentage for Indian Merchants](https://www.terra-insight.com/insights/net-banking-mdr-flat-fee-vs-percentage-india/)
- [OTT and SaaS MDR Reconciliation Playbook for Indian Subscription Businesses](https://www.terra-insight.com/insights/ott-saas-mdr-reconciliation-playbook-india/)
- [Paytm Payment Gateway MDR Reconciliation for Indian Merchants](https://www.terra-insight.com/insights/paytm-payment-gateway-mdr-reconciliation-india/)
- [PayU MDR Reconciliation: Standard 2% + Premium Slab Handling for Indian Merchants](https://www.terra-insight.com/insights/payu-mdr-reconciliation-india/)
- [PhonePe Payment Gateway MDR Reconciliation: The "Free" Promo and the Standard Plan](https://www.terra-insight.com/insights/phonepe-pg-mdr-reconciliation-india/)
- [Pine Labs POS MDR Reconciliation: Terminal-Level Settlement and Multi-Outlet Audit](https://www.terra-insight.com/insights/pine-labs-pos-mdr-reconciliation-india/)
- [PPI / Wallet-on-UPI Interchange: 1.1% Above ₹2,000 for Indian Merchants](https://www.terra-insight.com/insights/ppi-wallet-on-upi-interchange-1-1-percent-india/)
- [Premium Card Misrouting to the 3% Slab: A BIN-Tier Audit for Indian Merchants](https://www.terra-insight.com/insights/premium-card-misrouting-3-percent-slab-bin-audit-india/)
- [Premium / Signature / Infinite Credit Card MDR: Interchange Tier Risk for Indian Merchants](https://www.terra-insight.com/insights/premium-signature-infinite-card-mdr-india/)
- [Prepaid Card MDR Reconciliation for Indian Merchants](https://www.terra-insight.com/insights/prepaid-card-mdr-india/)
- [Razorpay MDR Reconciliation: Published 2% vs Negotiated 1.4-1.6% for Indian Merchants](https://www.terra-insight.com/insights/razorpay-mdr-reconciliation-india/)
- [RBI Debit-Card MDR Cap (RBI/2017-18/105): What It Caps and What It Doesn't](https://www.terra-insight.com/insights/rbi-debit-card-mdr-cap-2017-circular-india/)
- [Recurring Add-On and eNACH Mandate-Rejection Fees: Stacked Costs for Subscription Merchants](https://www.terra-insight.com/insights/recurring-add-on-enach-rejection-fees-stacking-india/)
- [RuPay Credit-Card-on-UPI: The 2% Surcharge Hidden Inside "UPI"](https://www.terra-insight.com/insights/rupay-credit-card-on-upi-2-percent-surcharge-india/)
- [RuPay Debit MDR Reconciliation for Indian Merchants: Zero-MDR Audit Path](https://www.terra-insight.com/insights/rupay-debit-mdr-reconciliation-india/)
- [RuPay Debit vs Visa/Mastercard Debit MDR: Why Network Choice Drives Merchant Cost](https://www.terra-insight.com/insights/rupay-debit-vs-visa-mastercard-debit-mdr-india/)
- [Section 194O TDS at 0.1% (Was 1%): Current Rate History Under Income-tax Act 2025](https://www.terra-insight.com/insights/section-194o-tds-0-1-percent-current-rate-history-india/)
- [Section 271DB: ₹5,000/Day Penalty for Not Offering UPI/RuPay (₹50 Cr+ Turnover)](https://www.terra-insight.com/insights/section-271db-penalty-upi-rupay-50-cr-turnover-india/)
- [Subscription SaaS MDR Economics for Indian Businesses: AutoPay vs Cards vs eNACH](https://www.terra-insight.com/insights/subscription-saas-mdr-economics-india/)
- [UPI AutoPay vs eNACH for ₹149-₹2,499 Subscription Tickets: Cost and Reliability Comparison](https://www.terra-insight.com/insights/upi-autopay-vs-enach-149-2499-subscription-tickets-india/)
- [UPI Bank-Account MDR by Ticket Size: Below ₹2,000 vs Above ₹2,000 Economics](https://www.terra-insight.com/insights/upi-bank-account-mdr-by-ticket-size-india/)
- [UPI MDR (Bank Account): What You Actually Pay vs What Gateways Charge](https://www.terra-insight.com/insights/upi-mdr-bank-account-vs-gateway-platform-fee-india/)
- [UPI Zero-MDR Regime in India: Section 269SU, PSS Act §10A, and What It Means for Merchant Fee Reconciliation](https://www.terra-insight.com/insights/upi-zero-mdr-regime-section-269su-pss-act-india/)
- [Visa/Mastercard Debit MDR: Small vs Large Merchant Caps (RBI 2017 Circular)](https://www.terra-insight.com/insights/visa-mastercard-debit-small-vs-large-merchants-mdr-india/)
- [Visa/Mastercard Credit Card Consumer MDR: Negotiated 1.4-1.6% vs Published 2%](https://www.terra-insight.com/insights/visa-mastercard-credit-consumer-negotiated-vs-published-mdr-india/)

## Insights: Bank Reconciliation

- [Axis Bank Corporate Statement Reconciliation: CIB, NEFT/RTGS, MT940 for Indian Treasury](https://www.terra-insight.com/insights/axis-bank-corporate-statement-reconciliation-india/)
- [Bank Statement Narration Pattern Classification: A Library for Indian Treasury Teams](https://www.terra-insight.com/insights/bank-statement-narration-pattern-classification-india/)
- [Bank Statement OCR vs Machine-Readable Formats: When to Use Which for Indian Reconciliation](https://www.terra-insight.com/insights/bank-statement-ocr-pdf-vs-machine-readable-india/)
- [IDFC FIRST Bank Corporate Reconciliation: Statement Formats and Narration Conventions](https://www.terra-insight.com/insights/idfc-first-bank-corporate-reconciliation-india/)
- [Kotak Mahindra Bank Corporate Statement Reconciliation](https://www.terra-insight.com/insights/kotak-mahindra-bank-corporate-reconciliation-india/)
- [MT940 vs CAMT.053 vs MT942: Format Comparison for Indian Bank Statement Reconciliation](https://www.terra-insight.com/insights/mt940-vs-camt-053-vs-mt942-india/)
- [Multi-Bank Cash Position Reconciliation for Indian Treasury Teams](https://www.terra-insight.com/insights/multi-bank-cash-position-reconciliation-india/)
- [Yes Bank Corporate Statement Reconciliation](https://www.terra-insight.com/insights/yes-bank-corporate-reconciliation-india/)
- [CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies](https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india/)
- [Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching](https://www.terra-insight.com/insights/bank-charges-reconciliation-india/)
- [Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them](https://www.terra-insight.com/insights/bank-statement-narration-patterns-india/)
- [HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns](https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india/)
- [ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching](https://www.terra-insight.com/insights/icici-bank-reconciliation-india/)
- [MT940 Bank Statement Format in India: How It Enables Automated Reconciliation](https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india/)
- [Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies](https://www.terra-insight.com/insights/opening-balance-reconciliation-india/)
- [Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment](https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india/)
- [SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing](https://www.terra-insight.com/insights/sbi-bank-reconciliation-india/)

## Insights: NACH and Statutory Payments

- [MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)](https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker/)
- [Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk](https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation/)
- [APS-04 NACH Pre-Booking and Reconciliation for Indian Corporates](https://www.terra-insight.com/insights/aps-aps04-prebooking-nach-india/)
- [NACH Credit Payout Reconciliation: Payroll and Vendor Settlement at Scale](https://www.terra-insight.com/insights/nach-credit-payouts-payroll-vendor-india/)
- [NACH EMI Reconciliation for NBFCs: Daily MIS, Return Codes, Penalty Recovery](https://www.terra-insight.com/insights/nach-emi-reconciliation-nbfc-india/)
- [PF and ESI Statutory Payment Reconciliation: ECR Filing and Compliance for Indian Employers](https://www.terra-insight.com/insights/pf-esi-statutory-payment-reconciliation-india/)
- [Professional Tax State-wise Reconciliation for Indian Employers](https://www.terra-insight.com/insights/professional-tax-state-wise-reconciliation-india/)
- [Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS](https://www.terra-insight.com/insights/advance-tax-reconciliation-india/)
- [ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer](https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation/)
- [ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification](https://www.terra-insight.com/insights/esi-contribution-reconciliation-india/)
- [NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations](https://www.terra-insight.com/insights/nach-mandate-management-reconciliation/)
- [NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates](https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation/)
- [NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams](https://www.terra-insight.com/insights/nach-return-codes-india/)
- [PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank](https://www.terra-insight.com/insights/pf-ecr-reconciliation-india/)
- [Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View](https://www.terra-insight.com/insights/statutory-payment-reconciliation-india/)

## Insights: NBFC Operations Reconciliation (co-lending, securitisation, SBR, FLDG, ECL)

- [NACH Bounce, Re-Presentation, and Successful Collection: Netting the Trail](https://www.terra-insight.com/insights/bounced-debit-re-presented-collected-nbfc-reconciliation-india/)
- [Defaulted Gold Loan Auction Surplus: Borrower Liability Not NBFC Income](https://www.terra-insight.com/insights/defaulted-loan-gold-auction-surplus-borrower-liability-nbfc-india/)
- [Dispose vs Safekeep Collateral Gold: NBFC Decision Reconciliation](https://www.terra-insight.com/insights/dispose-vs-safekeep-collateral-gold-nbfc-reconciliation-india/)
- [Genuine vs False Duplicate Loan Payment: Detection Logic for Gold-Loan NBFCs](https://www.terra-insight.com/insights/duplicate-loan-payment-detection-genuine-vs-false-nbfc-india/)
- [NBFC Fixed Deposit Early Closure: Penalty Netting and Reconciliation](https://www.terra-insight.com/insights/fixed-deposit-early-closure-penalty-netting-nbfc-india/)
- [Gold Appraisal Margin and LTV Cap: RBI 75% Ceiling and Margin Drift](https://www.terra-insight.com/insights/gold-appraisal-margin-loan-to-value-nbfc-rbi-cap-india/)
- [Gold-Loan NBFC Reconciliation in India: 16 Operational Scenarios](https://www.terra-insight.com/insights/gold-loan-nbfc-reconciliation-india-16-scenarios-cornerstone/)
- [Gold-Loan Tenure Rollover with Part Payment: Interest Recomputation](https://www.terra-insight.com/insights/gold-loan-tenure-rollover-reconciliation-part-payment-nbfc-india/)
- [MSME Gold Loan Priority Sector Lending Classification for NBFCs](https://www.terra-insight.com/insights/msme-gold-loan-priority-sector-lending-classification-nbfc-india/)
- [TDS on Interest Income for NBFCs: Section 393(1) Sl. 12 Code 1002 Chain](https://www.terra-insight.com/insights/tds-on-interest-income-nbfc-section-194a-code-1002-india/)
- [NBFC Borrower Tier Classification under RBI Scale-Based Regulation (SBR)](https://www.terra-insight.com/insights/nbfc-borrower-tier-classification-rbi-sbr-india/)
- [NBFC Collection Reconciliation under RBI Co-Lending Guidelines for Indian Lenders](https://www.terra-insight.com/insights/nbfc-collection-reconciliation-co-lending-india/)
- [NBFC Expected Credit Loss (ECL) Reconciliation under Ind AS 109 and RBI Master Direction](https://www.terra-insight.com/insights/nbfc-ecl-expected-credit-loss-reconciliation-india/)
- [NBFC Corporate Tax under Section 115BA (Income Tax Act 2025): Concessional Regime and Trade-Offs](https://www.terra-insight.com/insights/nbfc-corporate-tax-section-115ba-india/)
- [FLDG (First Loss Default Guarantee) Accounting and Reconciliation for Indian NBFC-Fintech Partnerships](https://www.terra-insight.com/insights/nbfc-fldg-first-loss-default-guarantee-recon-india/)
- [NBFC Securitisation and Pass-Through Certificate Reconciliation under RBI Master Direction 2021](https://www.terra-insight.com/insights/nbfc-securitisation-pass-through-reconciliation-india/)

## Insights: Reconciliation Fundamentals

- [ITC Leakage under Rule 36(4): What Suppliers' GSTR-1 Filing Delays Cost You](https://www.terra-insight.com/insights/itc-leakage-rule-36-4-gst-india/)
- [OEM Short-Pay Leakage for Indian Manufacturers: Decomposition and Recovery](https://www.terra-insight.com/insights/oem-short-pay-leakage-manufacturer-india/)
- [Platform Fee Leakage on Razorpay, PayU, Cashfree: A D2C Audit Playbook](https://www.terra-insight.com/insights/platform-fee-leakage-razorpay-payu-india/)
- [Revenue Leakage in Indian Finance Teams: The Seven Classes Framework](https://www.terra-insight.com/insights/revenue-leakage-india-finance-teams-guide/)
- [TDS Credit Leakage in India: How Form 26AS / Form 168 Reveals Missing Deductions](https://www.terra-insight.com/insights/tds-credit-leakage-form-26as-india/)
- [Working Capital Leakage from Reconciliation Delays: A CFO Estimation Framework](https://www.terra-insight.com/insights/working-capital-leakage-reconciliation-delay-india/)
- [Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies](https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india/)
- [Cash Flow Reconciliation: Matching P&L to Actual Bank Movements](https://www.terra-insight.com/insights/cash-flow-reconciliation-india/)
- [Cash-to-Bank Reconciliation for UPI and POS Transactions in India](https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india/)
- [Chargeback Reconciliation for Payment Gateways: A Finance Team Guide](https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway/)
- [Daily vs Monthly Reconciliation: When Each Approach Makes Sense](https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india/)
- [Debtors and Creditors Reconciliation: Ledger Matching Best Practices](https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india/)
- [Exception Management in Reconciliation: From Detection to Resolution](https://www.terra-insight.com/insights/exception-management-reconciliation-india/)
- [Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification](https://www.terra-insight.com/insights/fixed-asset-reconciliation-india/)
- [Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions](https://www.terra-insight.com/insights/forex-reconciliation-india/)
- [Intercompany Reconciliation in India: Group Finance Complexity](https://www.terra-insight.com/insights/intercompany-reconciliation-india/)
- [Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams](https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india/)
- [IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP](https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india/)
- [Manual vs Automated Reconciliation: The True Cost Comparison](https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india/)
- [Month-End Close Reconciliation Checklist for Indian Finance Teams](https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india/)
- [Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts](https://www.terra-insight.com/insights/multi-bank-reconciliation-india/)
- [Netting Reconciliation in India: How to Handle Net Payments Between Counterparties](https://www.terra-insight.com/insights/netting-reconciliation-india/)
- [Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses](https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india/)
- [Partial Payment Reconciliation: How to Allocate and Match in Indian Finance](https://www.terra-insight.com/insights/partial-payment-reconciliation-india/)
- [Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards](https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india/)
- [Reconciliation Audit Trail: What Regulators Expect in India](https://www.terra-insight.com/insights/reconciliation-audit-trail-india/)
- [Reconciliation Automation ROI: A Framework for Indian Finance Leaders](https://www.terra-insight.com/insights/reconciliation-automation-roi-india/)
- [Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like](https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance/)
- [Top 10 Reconciliation Errors That Trigger GST Notices](https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india/)
- [Reconciliation Debt: What It Costs Indian Companies Every Year](https://www.terra-insight.com/insights/reconciliation-debt-india/)
- [Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction](https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software/)
- [Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement](https://www.terra-insight.com/insights/reconciliation-kpis-india/)
- [What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions](https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india/)
- [Reconciliation Patterns Indian CFOs Should Track](https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo/)
- [Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know](https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india/)
- [10 Signs Your Reconciliation Process Is Broken](https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india/)
- [Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams](https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india/)
- [Virtual Account Reconciliation in India: How Auto-Matching Works](https://www.terra-insight.com/insights/virtual-account-reconciliation-india/)
- [What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams](https://www.terra-insight.com/insights/what-is-financial-reconciliation-india/)
- [What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools](https://www.terra-insight.com/insights/what-is-reconciliation-engine-india/)
- [Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity](https://www.terra-insight.com/insights/why-reconciliation-different-india/)
- [Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices](https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india/)

## Insights: Revenue Leakage Recovery

- [ITC Recovery for Indian Businesses: Rule 36(4) Provisional ITC and Rule 37 Reversal Reclaim](https://www.terra-insight.com/insights/itc-recovery-rule-36-4-rule-37-india/)
- [NACH Bounce Recovery and Section 43B(h) MSME Compliance for Indian Finance Teams](https://www.terra-insight.com/insights/nach-bounce-recovery-43b-h-msme-india/)
- [OEM Debit Note Dispute Recovery for Indian Tier-1 Manufacturers](https://www.terra-insight.com/insights/oem-debit-note-dispute-recovery-india/)
- [Platform Fee Recovery Playbook for D2C: Razorpay, PayU, Marketplace Settlement Audit](https://www.terra-insight.com/insights/platform-fee-recovery-d2c-india/)
- [Building the Board Case for Revenue Leakage Recovery: A CFO Guide](https://www.terra-insight.com/insights/revenue-leakage-board-justification-india/)
- [Revenue Leakage Recovery Playbook for Indian Enterprises](https://www.terra-insight.com/insights/revenue-leakage-recovery-india-playbook/)
- [TDS Credit Recovery: Operating Process for Indian Receivers](https://www.terra-insight.com/insights/tds-credit-recovery-26as-form-168-india/)
- [Working Capital Release via Leakage Recovery: A Treasury Playbook for Indian Enterprises](https://www.terra-insight.com/insights/working-capital-release-leakage-recovery-india/)

## Insights: Buyer's Guide and Software Evaluation

- [Best Reconciliation Software for Indian Businesses in 2026: A CFO Buyer Guide](https://www.terra-insight.com/insights/best-reconciliation-software-india-2025/)
- [How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs](https://www.terra-insight.com/insights/evaluate-reconciliation-software-india/)
- [Reconciliation Software ROI: How Indian Finance Teams Build the Business Case](https://www.terra-insight.com/insights/reconciliation-software-roi-india/)
- [Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When](https://www.terra-insight.com/insights/excel-python-reconciliation-software-india/)
- [How to Justify Reconciliation Software to Your Board: A CFO Playbook](https://www.terra-insight.com/insights/reconciliation-software-board-justification-india/)
- [Reconciliation Software Implementation: What to Expect in 30-60-90 Days](https://www.terra-insight.com/insights/reconciliation-software-implementation-india/)
- [Reconciliation Software vs ERP: Why Indian Finance Teams Need Both](https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india/)
- [15 Questions to Ask When Selecting a Reconciliation Vendor in India](https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india/)
- [SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose](https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india/)
- [Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify](https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india/)

## Insights: CA Firm Reconciliation Workflow

- [CA Firm Client Due Diligence and AML Compliance under PMLA](https://www.terra-insight.com/insights/ca-firm-client-due-diligence-aml-india/)
- [GST Monthly Compliance for CA Firms: GSTR-1/3B/9 Workflow at Scale](https://www.terra-insight.com/insights/ca-firm-gst-monthly-compliance-india/)
- [ICAI CPE Hours and Uniform Compliance for Practising CAs](https://www.terra-insight.com/insights/ca-firm-icai-cpe-uniform-india/)
- [CA Firm Pricing and Engagement Letters: India Practice](https://www.terra-insight.com/insights/ca-firm-pricing-engagement-letter-india/)
- [Statutory Audit Execution in CA Firms: Working Paper Templates and Documentation](https://www.terra-insight.com/insights/ca-firm-statutory-audit-execution-india/)
- [Tax Audit (Form 3CD) Mandate Management for CA Firms](https://www.terra-insight.com/insights/ca-firm-tax-audit-3cd-mandate-india/)
- [CA Firm Workflow Automation: Practice Management Systems for India](https://www.terra-insight.com/insights/ca-firm-workflow-automation-india/)
- [CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle](https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india/)
- [CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients](https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india/)
- [Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface](https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india/)
- [Reconciliation Software for CA Firms in India: Beyond Audit Tools](https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india/)
- [White-Label Reconciliation for CA Firms: Branded Client Deliverables](https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india/)

## Insights: Audit and Assurance

- [Bank Statutory Branch Audit (LFAR) in India: Empanelment, Engagement, Execution](https://www.terra-insight.com/insights/bank-audit-statutory-branch-audit-india/)
- [CARO 2020 Reporting Companion: Clause-by-Clause Audit Procedures for Indian Auditors](https://www.terra-insight.com/insights/caro-2020-reporting-companion-india/)
- [Concurrent Audit of Banks and NBFCs in India](https://www.terra-insight.com/insights/concurrent-audit-bank-nbfc-india/)
- [Forensic Audit in India under Section 148 and Section 211: Special Investigation Framework](https://www.terra-insight.com/insights/forensic-audit-india-section-148-211-companies-act/)
- [Internal Financial Control (ICFR) Reporting under Section 143(3)(i): Indian Auditor Guide](https://www.terra-insight.com/insights/internal-financial-control-icfr-section-143-3-i-india/)
- [Peer Review Mandate by ICAI: Scope, Process, Reviewer Selection for CA Firms](https://www.terra-insight.com/insights/peer-review-mandate-icai-india/)
- [Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs](https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india/)
- [ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)](https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india/)
- [Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence](https://www.terra-insight.com/insights/internal-audit-reconciliation-india/)
- [SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove](https://www.terra-insight.com/insights/sox-compliance-reconciliation-india/)
- [Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items](https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india/)
- [Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB](https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india/)

## Insights: Retail and D2C Reconciliation

- [Brand-Channel Partner Commercial Reconciliation for D2C: Influencer, Affiliate, Reseller](https://www.terra-insight.com/insights/brand-channel-partner-commercial-reconciliation-d2c-india/)
- [General Trade Distributor Reconciliation for D2C Brands: Stockist Network Cost Recovery](https://www.terra-insight.com/insights/general-trade-distributor-reconciliation-d2c-india/)
- [Section 9(5) GST Liability on Marketplaces for D2C Sellers: Who Pays Tax](https://www.terra-insight.com/insights/marketplace-section-9-5-gst-d2c-india/)
- [Modern Trade Channel Reconciliation for D2C Brands in India: DMart, Reliance Smart, More](https://www.terra-insight.com/insights/modern-trade-channel-reconciliation-d2c-india/)
- [Quick Commerce Platform Reconciliation: Blinkit, Zepto, Instamart Settlement Cycles](https://www.terra-insight.com/insights/quick-commerce-blinkit-zepto-instamart-reconciliation-india/)
- [Returns and RTO Accounting for D2C Brands: Reverse Logistics and GST Credit Notes](https://www.terra-insight.com/insights/returns-rto-accounting-d2c-india/)
- [Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O](https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india/)
- [Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1](https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india/)
- [D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts](https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india/)
- [Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores](https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india/)
- [Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart](https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india/)
- [Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching](https://www.terra-insight.com/insights/shopify-india-gst-reconciliation/)

## Insights: FMCG and Packaged Consumer Goods Reconciliation

- [Aerated and Sweetened Beverage GST and Cess Reconciliation (40% NSAB slab)](https://www.terra-insight.com/insights/aerated-sweetened-beverage-gst-cess-40-percent/)
- [APEDA Exports, RCMC and EIC Lab-Test Recovery Reconciliation for FMCG](https://www.terra-insight.com/insights/apeda-exports-rcmc-fmcg-reconciliation/)
- [Cold-Chain 3PL Reconciliation for Dairy and Frozen FMCG](https://www.terra-insight.com/insights/cold-chain-3pl-fmcg-reconciliation-dairy-frozen/)
- [E-Invoicing for FMCG below ₹5 crore — IRN Generation and Reconciliation](https://www.terra-insight.com/insights/e-invoicing-fmcg-5-crore-threshold-reconciliation/)
- [Edible Oil FMCG Reconciliation — Refining, Bottling, Distribution](https://www.terra-insight.com/insights/edible-oil-fmcg-reconciliation-adani-wilmar-patanjali/)
- [FSSAI Licence Renewal Cost Accounting for FMCG](https://www.terra-insight.com/insights/fssai-licence-renewal-cost-accounting-fmcg/)
- [GST Compensation Cess on Tobacco and Aerated FMCG Reconciliation](https://www.terra-insight.com/insights/gst-compensation-cess-tobacco-aerated-fmcg-reconciliation/)
- [Metal Kitchenware FMCG GST 2.0 Reconciliation (stainless steel, aluminium, copper)](https://www.terra-insight.com/insights/metal-kitchenware-fmcg-gst-2-0-reconciliation/)
- [PLISFPI Mozzarella Cheese Segment Claim Reconciliation](https://www.terra-insight.com/insights/plisfpi-mozzarella-cheese-segment-claim-reconciliation/)
- [Section 393(1) Sl. 4 (194C) Contract Manufacturing and Co-Pack TDS for FMCG](https://www.terra-insight.com/insights/section-393-194c-contract-manufacturing-fmcg/)
- [Biscuit Segment GST 2.0 Reconciliation (HSN 1905 all at 5%)](https://www.terra-insight.com/insights/biscuit-segment-gst-2-0-reconciliation-fmcg/)
- [Breakage and Damage Distributor Claim Reconciliation for FMCG](https://www.terra-insight.com/insights/breakage-damage-fmcg-distributor-claim/)
- [Chocolate and Confectionery GST 2.0 Reconciliation](https://www.terra-insight.com/insights/chocolate-confectionery-gst-2-0-reconciliation-fmcg/)
- [Distributor Commission and Section 393 Sl. 18 (194H) TDS Reconciliation for FMCG](https://www.terra-insight.com/insights/distributor-commission-section-194h-tds-fmcg/)
- [DMS (Distributor Management System) Reconciliation for FMCG](https://www.terra-insight.com/insights/dms-distributor-management-system-reconciliation-fmcg/)
- [General Trade Distributor Pyramid Reconciliation for FMCG](https://www.terra-insight.com/insights/general-trade-distributor-pyramid-reconciliation-fmcg/)
- [GST 2.0 FMCG Rate Rationalisation — Sept 2025 Reconciliation Guide](https://www.terra-insight.com/insights/gst-2-0-fmcg-rate-rationalisation-reconciliation-sept-2025/)
- [Joint Business Plan (JBP) Modern Trade Reconciliation for FMCG](https://www.terra-insight.com/insights/joint-business-plan-jbp-modern-trade-fmcg/)
- [Metro Cash & Carry FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/metro-cash-carry-fmcg-settlement-german-cnc/)
- [Personal Care FMCG GST 2.0 Reconciliation (Soaps, Shampoos, Toothpaste)](https://www.terra-insight.com/insights/personal-care-fmcg-gst-2-0-reconciliation/)
- [PLISFPI Claim Mechanics and Reconciliation for Indian Food Processing](https://www.terra-insight.com/insights/plisfpi-claim-mechanics-reconciliation-india-fmcg/)
- [PLISFPI Incremental Sales over Base Year FY 2019-20 — Reconciliation](https://www.terra-insight.com/insights/plisfpi-incremental-sales-base-year-fy2019-20/)
- [PLISFPI Marine Products Claim Reconciliation](https://www.terra-insight.com/insights/plisfpi-marine-products-claim-reconciliation/)
- [PLISFPI Processed Fruits & Vegetables Claim Reconciliation](https://www.terra-insight.com/insights/plisfpi-processed-fruits-vegetables-claim-reconciliation/)
- [PLISFPI RTC/RTE and Millet Segment Claim Reconciliation](https://www.terra-insight.com/insights/plisfpi-rtc-rte-millet-segment-claim-reconciliation/)
- [Return-to-Vendor (RTV) and Damage Credit Note Reconciliation for FMCG](https://www.terra-insight.com/insights/return-to-vendor-rtv-damage-credit-note-fmcg/)
- [Secondary Sales Gap and Stock-in-Trade Reconciliation for FMCG](https://www.terra-insight.com/insights/secondary-sales-gap-stock-in-trade-fmcg/)
- [Section 15(2) CGST Trade Discount Valuation Reconciliation for FMCG](https://www.terra-insight.com/insights/section-15-2-cgst-trade-discount-valuation-fmcg/)
- [Section 52 TCS on Quick Commerce FMCG — 2026 Reconciliation Guide](https://www.terra-insight.com/insights/section-52-tcs-quick-commerce-fmcg-reconciliation/)
- [Section 9(5) CGST Deemed Supplier — Cloud Kitchen FMCG Bridge](https://www.terra-insight.com/insights/section-9-5-cgst-cloud-kitchen-fmcg-bridge/)
- [Spencer's Retail FMCG Settlement Reconciliation (RPSG)](https://www.terra-insight.com/insights/spencer-retail-fmcg-settlement-rpsg/)
- [Star Bazaar / Trent FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/star-bazaar-trent-fmcg-settlement/)
- [Sub-Stockist Secondary Sales Reconciliation for FMCG](https://www.terra-insight.com/insights/sub-stockist-secondary-sales-reconciliation-fmcg/)
- [Super-Stockist and CFA (Carrying & Forwarding Agent) Reconciliation for FMCG](https://www.terra-insight.com/insights/super-stockist-cfa-reconciliation-fmcg/)
- [TPM Debit Note Reversal for Rejected Distributor Claims in FMCG](https://www.terra-insight.com/insights/tpm-debit-note-reversal-fmcg-rejected-claims/)
- [Walmart Best Price (Cash & Carry) FMCG Settlement](https://www.terra-insight.com/insights/walmart-best-price-fmcg-cash-carry-settlement/)
- [Blinkit (Zomato) FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/blinkit-fmcg-settlement-reconciliation/)
- [BOGO (Buy-One-Get-One) Scheme Accounting under CGST Section 15(2) for FMCG](https://www.terra-insight.com/insights/bogo-scheme-accounting-fmcg-section-15-2-gst/)
- [DMart FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/dmart-fmcg-settlement-reconciliation/)
- [Growth-vs-Base Scheme Reconciliation for FMCG Distributors](https://www.terra-insight.com/insights/growth-vs-base-scheme-fmcg-reconciliation/)
- [Modern Trade Settlement Variance Reconciliation for FMCG India](https://www.terra-insight.com/insights/modern-trade-settlement-variance-fmcg-india/)
- [More Retail FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/more-retail-fmcg-settlement-reconciliation/)
- [Quick Commerce FMCG Settlement Reconciliation in India](https://www.terra-insight.com/insights/quick-commerce-fmcg-settlement-reconciliation-india/)
- [Reliance Smart / RRVL FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/reliance-smart-rsl-fmcg-settlement/)
- [Retro Credit Note for FMCG Schemes Issued at Quarter End](https://www.terra-insight.com/insights/retro-credit-note-fmcg-scheme-quarter-end/)
- [Slab Discount Distributor Claim Recovery for FMCG](https://www.terra-insight.com/insights/slab-discount-distributor-claim-recovery-fmcg/)
- [Swiggy Instamart FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/swiggy-instamart-fmcg-settlement-reconciliation/)
- [Trade Promotion Accrual vs Payout Reconciliation for Indian FMCG](https://www.terra-insight.com/insights/tpm-accrual-vs-payout-reconciliation-fmcg-india/)
- [Zepto FMCG Settlement Reconciliation](https://www.terra-insight.com/insights/zepto-fmcg-settlement-reconciliation/)

## Insights: ERP Integrations for Reconciliation

- [Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns](https://www.terra-insight.com/insights/busy-software-reconciliation-india/)
- [Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation](https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india/)
- [Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths](https://www.terra-insight.com/insights/odoo-reconciliation-india/)
- [Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover](https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india/)
- [Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams](https://www.terra-insight.com/insights/sage-reconciliation-india/)
- [SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short](https://www.terra-insight.com/insights/sap-fi-reconciliation-india/)
- [Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses](https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india/)
- [Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale](https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india/)

## Insights: Restaurant and F&B Reconciliation

- [Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework](https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation/)
- [Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation](https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr/)
- [Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets](https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig/)
- [Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split](https://www.terra-insight.com/insights/restaurant-reconciliation-india/)
- [GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not](https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability/)
- [Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393](https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india/)
- [Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393](https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india/)
- [Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission](https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation/)
- [Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers](https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india/)
- [Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips](https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india/)
- [TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger](https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation/)
- [Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1035](https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation/)
- [Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities](https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation/)
- [Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS](https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation/)
- [QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L](https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation/)
- [Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit](https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation/)
- [Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs](https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct/)
- [Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC](https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation/)
- [Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties](https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation/)
- [Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders](https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation/)

## Insights: Hotel and Hospitality Reconciliation

- [Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split](https://www.terra-insight.com/insights/hotel-reconciliation-india/)
- [GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)](https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services/)
- [Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B](https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india/)
- [Hotel Deposit, Refund, and No-Show Reconciliation in India](https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india/)
- [Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj](https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india/)
- [Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline](https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation/)
- [Service Apartment and Extended-Stay Reconciliation in India](https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india/)
- [Section 393(1) Sl. 1(ii) and Payment Code 1006: Hotel TDS Reconciliation on Domestic OTA Commission](https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation/)
- [Section 393(2) (non-resident catch-all) of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission](https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation/)
- [Banquet Event Advance Reconciliation: Contract to Final Folio in India](https://www.terra-insight.com/insights/banquet-event-advance-reconciliation/)
- [Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance](https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation/)
- [Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing](https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation/)
- [Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits](https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation/)
- [Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India](https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct/)
- [Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement](https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation/)
- [Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger](https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation/)
- [MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment](https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation/)
- [OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions](https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation/)

## Insights: Manufacturing Reconciliation

- [Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching](https://www.terra-insight.com/insights/manufacturing-reconciliation-india/)
- [APEDA Export Incentive Reconciliation for Indian Food Processing](https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india/)
- [APMC and Mandi Cess Reconciliation Across Indian States](https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india/)
- [Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation](https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation/)
- [Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing](https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india/)
- [Customs Duty SCN Matching for Indian Electronics Manufacturing](https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india/)
- [DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers](https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india/)
- [Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments](https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india/)
- [Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply](https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india/)
- [Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts](https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india/)
- [Drone Component Import Withholding Under Section 393(2) Sl. 17: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification](https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india/)
- [Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers](https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india/)
- [Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits](https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india/)
- [DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers](https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india/)
- [Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty](https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india/)
- [Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts](https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india/)
- [Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate](https://www.terra-insight.com/insights/food-processing-reconciliation-india/)
- [Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS](https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india/)
- [Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds](https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india/)
- [GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics](https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india/)
- [Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing](https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india/)
- [Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel](https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india/)
- [Section 393(1) Sl. 8(ii) Purchase TDS for Manufacturing: Payment Code 1031, Legacy 194Q Cross-Era (FY 2026-27)](https://www.terra-insight.com/insights/manufacturing-393-sl-8-ii-purchase-goods-reconciliation/)
- [AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%](https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india/)
- [Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking](https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation/)
- [Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)](https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394/)
- [Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts](https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india/)
- [Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering](https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india/)
- [MSP-Linked Procurement Reconciliation for Indian Food Processing](https://www.terra-insight.com/insights/msp-procurement-reconciliation-india/)
- [NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing](https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india/)
- [Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering](https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india/)
- [Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing](https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india/)
- [Pharmaceutical Distributor and Expired Stock Return Reconciliation](https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india/)
- [Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing](https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india/)
- [PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem](https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india/)
- [SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps](https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india/)
- [Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS](https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india/)
- [Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics](https://www.terra-insight.com/insights/stock-transfer-reconciliation-india/)
- [Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act](https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143/)
- [Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment](https://www.terra-insight.com/insights/works-contract-reconciliation-india/)

## Insights: Logistics Reconciliation (FASTag, freight GST, 3PL, COD)

- [3PL Settlement Reconciliation for Indian Logistics and Supply-Chain Operators](https://www.terra-insight.com/insights/3pl-settlement-reconciliation-india/)
- [Courier and Last-Mile Reconciliation for Indian E-commerce and D2C Brands](https://www.terra-insight.com/insights/courier-last-mile-reconciliation-india/)
- [FASTag Toll Reconciliation for Indian Fleet Operators and Logistics Companies](https://www.terra-insight.com/insights/fastag-toll-reconciliation-india/)
- [Freight Forwarder Multimodal Reconciliation for Indian Logistics Operators](https://www.terra-insight.com/insights/freight-forwarder-multimodal-reconciliation-india/)
- [Freight GST Reconciliation: RCM, GTA Election, and ITC for Indian Manufacturers](https://www.terra-insight.com/insights/freight-gst-reconciliation-india/)
- [IATA BSP Airline-Agent Reconciliation for Indian Travel Agencies](https://www.terra-insight.com/insights/iata-bsp-airline-agent-reconciliation-india/)
- [Ocean Freight and Container Tracking Reconciliation for Indian Exporters](https://www.terra-insight.com/insights/ocean-freight-container-tracking-reconciliation-india/)
- [Warehouse COD and 3PL Settlement Reconciliation for Indian D2C and E-commerce](https://www.terra-insight.com/insights/warehouse-cod-reconciliation-3pl-india/)

## Insights: Education and Coaching Reconciliation

- [Coaching and EdTech Revenue Recognition under Ind AS 115: Course Fee Performance Obligations](https://www.terra-insight.com/insights/coaching-edtech-revenue-recognition-ind-as-115-india/)
- [GST on Education Services: Exemption under Notification 12/2017 and Boundary Cases](https://www.terra-insight.com/insights/gst-education-services-exemption-notification-12-2017-india/)
- [Higher Education Research Grant Reconciliation: DST, ICMR, CSIR for Indian Institutions](https://www.terra-insight.com/insights/higher-education-research-grant-reconciliation-india/)
- [Scholarship and Grant Disbursement Reconciliation for Indian Educational Institutions](https://www.terra-insight.com/insights/scholarship-grant-disbursement-reconciliation-india/)
- [School and College Fee Reconciliation for Indian Educational Institutions](https://www.terra-insight.com/insights/school-college-fee-reconciliation-india/)
- [University Fee Collection Bank Reconciliation: Multi-Bank Account Pooling for Indian Institutions](https://www.terra-insight.com/insights/university-fee-collection-bank-reconciliation-india/)

## Insights: Real Estate and Construction Reconciliation

- [Cancelled Flat Resold to New Buyer: Reconciliation and Reversal](https://www.terra-insight.com/insights/cancelled-flat-resold-reconciliation-real-estate-india/)
- [CAM (Common Area Maintenance) GST 18% Above ₹7,500/mo Threshold](https://www.terra-insight.com/insights/cam-common-area-maintenance-real-estate-gst-7500-threshold-india/)
- [Car Parking Charges in Real Estate: GST Treatment as Composite Supply](https://www.terra-insight.com/insights/car-parking-charges-real-estate-gst-treatment-india/)
- [Flat Sold After Completion Certificate: Why No GST Applies (Schedule III Entry 5)](https://www.terra-insight.com/insights/completion-certificate-flat-sale-no-gst-india/)
- [Booking Deposit Forfeiture GST: Section 15(2) and the Tolerating-an-Act Argument](https://www.terra-insight.com/insights/deposit-forfeiture-real-estate-cancelled-booking-gst-india/)
- [Home Loan Interest and Buyer TDS: Section 194A Handling in Real Estate](https://www.terra-insight.com/insights/home-loan-interest-tds-real-estate-buyer-recovery-india/)
- [Joint Property Buyers and Section 194IA: Why TDS Still Applies on Split Payments](https://www.terra-insight.com/insights/joint-buyer-property-tds-194ia-aggregation-india/)
- [Interest-Free Maintenance Deposit: Neither Revenue Nor Escrow](https://www.terra-insight.com/insights/maintenance-deposit-real-estate-non-revenue-non-escrow-india/)
- [NRI Property Seller TDS: Section 195 (Not 194IA) — the Highest-Cost Compliance Trap](https://www.terra-insight.com/insights/nri-property-seller-tds-section-195-vs-194ia-india/)
- [PLC (Preferential Location Charges) GST Treatment for Real Estate](https://www.terra-insight.com/insights/preferential-location-charges-plc-real-estate-gst-india/)
- [Architect and Engineer Professional Fees TDS: Section 393(1) Sl. 15 (Legacy 194J)](https://www.terra-insight.com/insights/professional-fee-architect-engineer-tds-section-194j-real-estate/)
- [Redevelopment Projects: Free Flats + Rent to Existing Tenants Under GST](https://www.terra-insight.com/insights/redevelopment-project-existing-tenant-alternate-accommodation-gst-india/)
- [RERA Form 3 / Form 5 Quarterly Compliance: Escrow Drawdown vs Construction Progress](https://www.terra-insight.com/insights/rera-compliance-quarterly-form-progress-report-real-estate-india/)
- [Affordable Housing 1% GST vs Non-Affordable 5%: Boundary Conditions](https://www.terra-insight.com/insights/slum-rehab-affordable-housing-gst-1-percent-cgst-real-estate-india/)
- [Stamp Duty, Registration Fee, and GST: Three Separate Reconciliation Trails](https://www.terra-insight.com/insights/stamp-duty-registration-real-estate-reconciliation-india/)
- [TDS on Property Purchase: Section 194IA ₹50 Lakh Threshold Trap](https://www.terra-insight.com/insights/tds-property-purchase-section-194ia-50-lakh-threshold-india/)
- [Works Contractor Payments TDS: Section 393(1) Sl. 4 (Legacy 194C) for Developers](https://www.terra-insight.com/insights/works-contractor-tds-section-194c-real-estate-code-1023-india/)
- [Joint Venture (JV) Real Estate Reconciliation for Indian Developers](https://www.terra-insight.com/insights/jv-joint-venture-real-estate-reconciliation-india/)
- [Real Estate Brokerage Commission Reconciliation: TDS Section 393(1) Sl. 1(ii) Payment Code 1006](https://www.terra-insight.com/insights/real-estate-brokerage-commission-reconciliation-tds-india/)
- [Real Estate Developer Revenue Recognition under Ind AS 115: POC, Project Cost Reconciliation](https://www.terra-insight.com/insights/real-estate-developer-revenue-recognition-ind-as-115-india/)
- [RERA Escrow Account Reconciliation for Indian Real Estate Developers](https://www.terra-insight.com/insights/rera-escrow-account-reconciliation-india/)
- [Society Maintenance Charge Reconciliation: GST, Late-Fee, and Accounting under Section 22A](https://www.terra-insight.com/insights/society-maintenance-charge-reconciliation-india/)
- [TDS on Rent by Individual/HUF under Section 393(1) Sl. 2(i) Payment Code 1007 (FY 2026-27)](https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-sl-2-i-rent-ind-huf-india/)

## Insights: Pharma and Life Sciences Reconciliation

- [ANDA and US Generic Revenue: Milestone-Based Ind AS 115 Reconciliation](https://www.terra-insight.com/insights/anda-us-generic-export-revenue-recognition-milestone-reconciliation/)
- [API vs Formulation: HSN 2941 / 3003 / 3004 Reconciliation Guide](https://www.terra-insight.com/insights/api-vs-formulation-hsn-2941-3003-3004-reconciliation-guide/)
- [GST 2.0 for Pharma: The 56th Council Drug and Device Reset](https://www.terra-insight.com/insights/gst-council-56-pharma-drugs-medical-devices-5-percent-transition/)
- [Loan-Licensing and Third-Party Manufacturing: The Pharma Reconciliation Guide](https://www.terra-insight.com/insights/loan-licensing-manufacturing-pharma-cdmo-reconciliation-guide/)
- [PLI Pharma Rs 15,000 Crore: Eligibility, Incremental Sales, Disbursement](https://www.terra-insight.com/insights/pli-pharma-15000-crore-eligibility-incremental-sales-reconciliation/)
- [Rule 89(5) for Pharma Formulations: The Complete Refund Playbook](https://www.terra-insight.com/insights/rule-89-5-inverted-duty-refund-pharma-formulations-complete-guide/)
- [Section 35(2AB) for Pharma R&D: The DSIR Reconciliation Playbook](https://www.terra-insight.com/insights/section-35-2ab-weighted-deduction-pharma-r-and-d-reconciliation-guide/)
- [USFDA Form 483: Remediation Cost Accounting Under Section 37](https://www.terra-insight.com/insights/usfda-form-483-remediation-cost-accounting-treatment-guide/)
- [Tentative Approval to Launch: When ANDA Revenue Actually Books](https://www.terra-insight.com/insights/anda-milestone-payment-usfda-tentative-approval-revenue-timing/)
- [DPCO 2013 and NPPA: Reconciling Scheduled-Drug Overcharging Recovery](https://www.terra-insight.com/insights/dpco-2013-nppa-ceiling-price-overcharging-recovery-reconciliation/)
- [Emerging Markets Africa + LatAm: Generic Export Reconciliation](https://www.terra-insight.com/insights/emerging-markets-africa-latam-generic-pharma-export-reconciliation/)
- [EMA + CEP: Reconciling EU Generic Export Realisation](https://www.terra-insight.com/insights/european-medicines-agency-cep-eu-generic-export-reconciliation/)
- [1mg + PharmEasy + NetMeds: TCS Section 52 Marketplace Reconciliation](https://www.terra-insight.com/insights/gst-tcs-marketplace-pharma-1mg-pharmeasy-netmeds-reconciliation/)
- [Pharma Export: Drawback + RoDTEP + Advance Authorisation Stacking](https://www.terra-insight.com/insights/pharma-export-drawback-rodtep-reconciliation-formulations/)
- [PLI Grants vs MAT: How Section 115JB Interacts with PLI Income](https://www.terra-insight.com/insights/pli-vs-mat-minimum-alternate-tax-pharma-interaction/)
- [Section 115BAA vs PLI: Choosing the Concessional 22% Regime](https://www.terra-insight.com/insights/section-115baa-vs-pli-pharma-concessional-rate-election/)
- [Section 194Q on API Purchases: The Buyer-Seller Reconciliation](https://www.terra-insight.com/insights/section-194q-tds-api-raw-material-purchase-pharma-reconciliation/)
- [Bulk Drug Park + PLI: The 53 Critical APIs Reconciliation](https://www.terra-insight.com/insights/bulk-drug-park-scheme-pli-53-critical-apis-reconciliation/)
- [CDMO Margin and Transfer Pricing: The Piramal and Syngene Playbook](https://www.terra-insight.com/insights/cdmo-contract-manufacturing-margin-transfer-pricing-pharma/)
- [CGMP Consulting Fees: Section 37 Deduction and TDS Under 194J and 195](https://www.terra-insight.com/insights/cgmp-remediation-consulting-fees-section-37-deduction-pharma/)
- [Import Alert 89-08: Reconciling Lost US Revenue Under Ind AS 115](https://www.terra-insight.com/insights/import-alert-89-08-lost-revenue-reconciliation-pharma/)
- [Rule 45 Material Movement: ITC-04 for Pharma Loan-Licensees](https://www.terra-insight.com/insights/pharma-job-work-material-movement-rule-45-itc-04-quarterly-return/)
- [Domestic Value Addition: KSM Reconciliation for PLI Category 2](https://www.terra-insight.com/insights/pli-pharma-domestic-value-addition-key-starting-material-reconciliation/)
- [PLI Pharma Categories 1 / 2 / 3: Differential Eligibility Rules](https://www.terra-insight.com/insights/pli-pharma-category-1-2-3-eligibility-differential-treatment/)
- [Base Year FY 2019-20: Reconciling Incremental Sales for PLI Claim](https://www.terra-insight.com/insights/pli-pharma-incremental-sales-base-year-fy-2019-20-reconciliation/)
- [PLI Pharma Quarterly Disbursement: DoP Portal Reconciliation](https://www.terra-insight.com/insights/pli-pharma-quarterly-disbursement-dop-portal-reconciliation/)
- [Section 143 CGST for Pharma: ITC-04 Quarterly Return Reconciliation](https://www.terra-insight.com/insights/section-143-cgst-job-work-pharma-formulations-itc-04/)
- [Building a USFDA Inspection Observation Remediation Tracker](https://www.terra-insight.com/insights/usfda-inspection-observation-remediation-tracker-pharma/)
- [API Imports: Customs Tariff Act 1975 Reconciliation for Formulators](https://www.terra-insight.com/insights/active-pharmaceutical-ingredient-import-customs-tariff-1975/)
- [API CDMO Margin Reconciliation: Cost-Plus, Fixed-Price, Milestone](https://www.terra-insight.com/insights/api-contract-manufacturing-margin-reconciliation-cdmo/)
- [API Yield Loss and Solvent Recovery: Reconciling the Weight-Loss Gap](https://www.terra-insight.com/insights/api-yield-loss-solvent-recovery-reconciliation-pharma-manufacturing/)
- [Backward Integration: API Transfer Pricing to Formulation Plants](https://www.terra-insight.com/insights/backward-integration-api-manufacturing-transfer-pricing-pharma/)
- [Clinical Trials and CRO Fees: What Section 35(2AB) Allows](https://www.terra-insight.com/insights/clinical-trial-cro-expenditure-section-35-2ab-eligibility-pharma/)
- [DSIR Form 3CL / 3CLA: Approval Trail and Year-End Reconciliation](https://www.terra-insight.com/insights/dsir-form-3cl-3cla-r-and-d-approval-reconciliation-pharma/)
- [Ind AS 38 vs Section 35(2AB): Reconciling Book vs Tax R&D Treatment](https://www.terra-insight.com/insights/ind-as-38-r-and-d-capitalisation-vs-section-35-2ab-pharma/)
- [Chapter 27 Solvents Blocked: Notification 09/2022 for Pharma Refund Teams](https://www.terra-insight.com/insights/notification-09-2022-chapter-27-solvents-blocked-refund-pharma/)
- [Notification 14/2022: How Net-ITC Reshaped Pharma Refund Math](https://www.terra-insight.com/insights/notification-14-2022-net-itc-formula-amendment-pharma/)
- [The 5/12/18 Input Mix: A Worked Refund Example for Pharma Formulations](https://www.terra-insight.com/insights/pharma-inverted-duty-refund-input-mix-5-12-18-worked-example/)
- [Section 54(3) RFD-01 for Pharma: The End-to-End Filing Workflow](https://www.terra-insight.com/insights/section-54-3-cgst-rfd-01-pharma-inverted-duty-filing-workflow/)
- [USFDA Warning Letters: Ind AS 37 Provisions and Contingent Liabilities](https://www.terra-insight.com/insights/usfda-warning-letter-remediation-provision-ind-as-37/)
- [Reading the 56th Council FAQ: Q10, Q25, Q51 for Pharma Teams](https://www.terra-insight.com/insights/gst-council-faq-q10-q25-q51-pharma-clarifications-reading-guide/)
- [Nil-Rated Life-Saving Drugs: Cancer, HIV, TB, Rare Disease Schedule](https://www.terra-insight.com/insights/life-saving-drugs-nil-rate-gst-cancer-hiv-tb-rare-disease/)
- [Medical Devices at 5%: HSN 9018–9022 Rate-Change Reconciliation](https://www.terra-insight.com/insights/medical-device-hsn-9018-9022-18-to-5-percent-rate-change/)
- [Pharma Inventory Rate-Switch: Reconciling 12% Stock Sold at 5%](https://www.terra-insight.com/insights/pharma-inventory-gst-rate-switch-22-september-2025-reconciliation/)
- [Straddle Invoices: Pharma Movements Across the 22-Sept-2025 Cutover](https://www.terra-insight.com/insights/straddle-invoice-pharma-pre-post-22-sept-2025-reconciliation/)
- [CGHS and ECHS Hospital Pharma Billing Reconciliation for Empanelled Suppliers](https://www.terra-insight.com/insights/cghs-echs-hospital-pharma-billing-reconciliation-india/)
- [GST Refund for Pharma under Inverted Duty Structure: Rule 89(5) Application](https://www.terra-insight.com/insights/gst-refund-inverted-duty-pharma-rule-89-5-india/)
- [Medical Representative Settlement and Expense Reconciliation in Indian Pharma](https://www.terra-insight.com/insights/medical-representative-mr-settlement-india/)
- [Pharma Distributor and Stockist Reconciliation for Indian Pharmaceutical Manufacturers](https://www.terra-insight.com/insights/pharma-distributor-stockist-reconciliation-india/)
- [Pharma Expiry Returns Reconciliation: Saleable vs Non-Saleable Accounting](https://www.terra-insight.com/insights/pharma-expiry-returns-saleable-non-saleable-india/)
- [Pharma R&D Tax Incentive: Section 35(2AB) Weighted Deduction and DSIR Recognition](https://www.terra-insight.com/insights/pharma-r-and-d-tax-incentive-section-35-2ab-india/)

## Insights: Power and Utility Reconciliation

- [DISCOM Settlement Reconciliation for Power Generators in India](https://www.terra-insight.com/insights/discom-settlement-reconciliation-india/)
- [DISCOM Tariff True-Up Reconciliation under MERC/KERC: Industrial Consumer Guide](https://www.terra-insight.com/insights/discom-tariff-true-up-merc-india/)
- [Electricity Duty and State Cesses Reconciliation for Indian C&I Consumers](https://www.terra-insight.com/insights/electricity-duty-cesses-state-wise-india/)
- [IEX and PXIL Power Exchange Reconciliation for Indian Open-Access Buyers](https://www.terra-insight.com/insights/power-exchange-iex-pxil-reconciliation-india/)
- [Solar Rooftop Net-Metering Reconciliation for Indian C&I Customers](https://www.terra-insight.com/insights/solar-rooftop-net-metering-reconciliation-india/)
- [Transmission Charges Reconciliation: CTU/STU/PGCIL Billing for Open-Access Customers](https://www.terra-insight.com/insights/transmission-charges-cstu-cwc-pgcil-india/)

## Insights: Telecom Reconciliation

- [Enterprise MPLS Circuit Billing Reconciliation: SLA Credit and Recovery](https://www.terra-insight.com/insights/enterprise-mpls-circuit-billing-reconciliation-india/)
- [Lawful Interception and Government Billing Reconciliation for Indian Telecom Operators](https://www.terra-insight.com/insights/lawful-interception-billing-reconciliation-india/)
- [Prepaid and Postpaid Revenue Recognition for Indian Telecom under Ind AS 115](https://www.terra-insight.com/insights/prepaid-postpaid-revenue-recognition-telecom-india/)
- [ILD International Long Distance Reconciliation: Carrier Settlement for Indian Telecom](https://www.terra-insight.com/insights/telecom-ild-international-long-distance-reconciliation-india/)
- [Telecom IUC (Interconnect Usage Charges) Reconciliation for Indian Operators](https://www.terra-insight.com/insights/telecom-iuc-interconnect-reconciliation-india/)
- [Tower Infrastructure Revenue Reconciliation: Indus Towers, ATC, Brookfield Telco](https://www.terra-insight.com/insights/tower-infrastructure-revenue-reconciliation-india/)

## Insights: Automotive Component Reconciliation

- [ITC Clawback at Day 180 vs Day 181: Section 16(2) Second Proviso Boundary](https://www.terra-insight.com/insights/itc-clawback-180-day-boundary-auto-oem-section-16-second-proviso-india/)
- [ITC Clawback on Partial Payment: Proportional Reversal — Not Full](https://www.terra-insight.com/insights/itc-clawback-partial-payment-proportional-auto-oem-india/)
- [Rejection Debit After Invoice Already Paid: Section 34 Credit Note Cycle](https://www.terra-insight.com/insights/rejection-debit-after-invoice-paid-auto-section-34-credit-note-india/)
- [5% Retention Debit by OEM: Not a Short Payment, Not a Rejection](https://www.terra-insight.com/insights/retention-debit-5-percent-auto-oem-not-short-payment-india/)
- [Retroactive Price Increase from OEM: Credit-Note Aggregation Reconciliation](https://www.terra-insight.com/insights/retroactive-price-increase-auto-oem-credit-note-aggregation-india/)
- [Form 26AS (Form 168) vs Books Reconciliation for Auto-Component Manufacturers](https://www.terra-insight.com/insights/26as-vs-books-reconciliation-manufacturing-auto-india/)
- [Aftermarket Spares Distribution Reconciliation for Indian Auto-Component Manufacturers](https://www.terra-insight.com/insights/aftermarket-spares-distribution-reconciliation-auto-india/)
- [Aftermarket vs OEM Supply: How Reconciliation Discipline Differs for Auto-Component Manufacturers](https://www.terra-insight.com/insights/auto-aftermarket-vs-oem-supplier-reconciliation-differences-india/)
- [Auto-Component TDS/TCS Cross-Era Reconciliation: Bridging FY 2025-26 to FY 2026-27](https://www.terra-insight.com/insights/auto-component-tds-tcs-cross-era-reconciliation-india/)
- [Cost Audit under Section 148 for Auto-Component Manufacturers](https://www.terra-insight.com/insights/cost-audit-section-148-auto-component-manufacturer-india/)
- [Consignment Stock Withdrawal and ERS Invoicing under GST: Auto-Supplier Reconciliation](https://www.terra-insight.com/insights/gst-consignment-stock-withdrawal-ers-auto-india/)
- [GST on Warranty Replacements for Auto Components: Buyer-Seller-OEM Three-Party Treatment](https://www.terra-insight.com/insights/gst-on-warranty-replacements-auto-component-india/)
- [GST on Auto-Component Tooling under Rule 43: Capital-Goods ITC for Indian Suppliers](https://www.terra-insight.com/insights/gst-tooling-capital-goods-rule-43-auto-component-india/)
- [GST on Warranty Replacement Supplies for Auto Components: FOC Supply and Schedule I](https://www.terra-insight.com/insights/gst-warranty-replacement-foc-supply-auto-component-india/)
- [GSTR-9 Filing for Auto-Component Manufacturers: Key Reconciliations and Audit Trail](https://www.terra-insight.com/insights/gstr-9-auto-component-manufacturer-key-reconciliation-india/)
- [Input Tax Credit on Capital Goods for Auto-Component Manufacturers: Section 16, 17(5), Rule 43](https://www.terra-insight.com/insights/input-tax-credit-capital-goods-auto-manufacturing-india/)
- [Internal Audit of OEM Receivables for Auto-Component Suppliers](https://www.terra-insight.com/insights/internal-audit-oem-receivables-auto-component-india/)
- [Inventory Valuation for Auto-Component Manufacturers under Ind AS 2](https://www.terra-insight.com/insights/inventory-valuation-auto-component-ind-as-2-india/)
- [Multi-ASN Single Invoice Consolidation: GST Compliance for Auto-Component Suppliers](https://www.terra-insight.com/insights/multi-asn-single-invoice-consolidation-auto-india/)
- [New TDS and TCS Provisions FY 2026-27: What Indian Auto-Component Suppliers Must Reconfigure](https://www.terra-insight.com/insights/new-tds-tcs-provisions-fy-2026-27-auto-component-india/)
- [OEM Vendor Audit Preparation for Auto-Component Suppliers: Maruti, Tata, Mahindra, Bosch](https://www.terra-insight.com/insights/oem-vendor-audit-preparation-auto-supplier-india/)
- [Quality Cost Accounting for Auto-Component Manufacturers: PAF Model and Indian Tax Treatment](https://www.terra-insight.com/insights/quality-cost-accounting-auto-component-manufacturing-india/)
- [Revenue Recognition for Auto-Component Manufacturers under Ind AS 115](https://www.terra-insight.com/insights/revenue-recognition-auto-component-ind-as-115-india/)
- [Statutory Audit Checklist for Auto-Component Manufacturers: 47 Items for CAs](https://www.terra-insight.com/insights/statutory-audit-checklist-auto-component-manufacturer-india/)
- [TDS on Foreign Agent Commission for Auto-Component Exports: Section 393(2) + Payment Code 1057](https://www.terra-insight.com/insights/tds-foreign-agent-commission-auto-component-export-india/)
- [TDS on Freight and Transport for Auto-Component Suppliers: Section 393 + Payment Codes 1023/1024 (FY 2026-27)](https://www.terra-insight.com/insights/tds-on-freight-transport-auto-component-section-194c-india/)
- [TDS on Tooling Payments: Capital vs Revenue Classification for Auto-Component Suppliers](https://www.terra-insight.com/insights/tds-tooling-payment-capital-vs-revenue-auto-india/)
- [8D Corrective Action Reports: Financial Reconciliation for Indian Auto-Component Suppliers](https://www.terra-insight.com/insights/8d-corrective-action-quality-financial-impact-auto-india/)
- [ASN to GRN to Invoice: The Auto-Component Three-Way Match That Actually Works](https://www.terra-insight.com/insights/asn-grn-invoice-three-way-match-auto-india/)
- [Bajaj Auto and TVS Two-Wheeler Supplier Reconciliation: Operating Model for Indian Auto-Component Tier-1s](https://www.terra-insight.com/insights/bajaj-auto-tvs-two-wheeler-supplier-reconciliation/)
- [Casting Process Reconciliation: Melt Loss, Rejection and Auto-Component Material Accounting](https://www.terra-insight.com/insights/casting-melt-loss-rejection-reconciliation-auto-india/)
- [Consignment Stock and Vendor-Managed Inventory Reconciliation for Indian Auto-Component Suppliers](https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india/)
- [Microsoft Dynamics 365 India Localisation for Auto-Component Manufacturers: What's Missing](https://www.terra-insight.com/insights/dynamics-365-india-localisation-auto-component-gaps/)
- [ERP Data Extracts for Auto-Component Reconciliation: SAP IDocs, Oracle BIP, Tally CSV, D365 Data Entities](https://www.terra-insight.com/insights/erp-data-extract-reconciliation-auto-component-india/)
- [FOMP Warranty Back-Charge Accounting for Indian Auto Component Tier-1 Suppliers](https://www.terra-insight.com/insights/fomp-warranty-back-charge-accounting-auto-india/)
- [Forging Process Reconciliation: Die Wear, Flash Loss and Auto-Component Tax Treatment](https://www.terra-insight.com/insights/forging-die-wear-flash-loss-reconciliation-auto-india/)
- [Heat Treatment and Plating Job Work Reconciliation: Section 143 Compliance for Auto Suppliers](https://www.terra-insight.com/insights/heat-treatment-plating-job-work-reconciliation-auto-india/)
- [Hero MotoCorp Supplier Payment Reconciliation: Splendor and Passion Volume Suppliers](https://www.terra-insight.com/insights/hero-motocorp-supplier-payment-reconciliation/)
- [Hyundai Motor India Supplier Settlement: Reconciliation for Tier-1 and Tier-2 Auto Suppliers](https://www.terra-insight.com/insights/hyundai-motor-india-supplier-reconciliation/)
- [JLR and Tata Motors: Reconciliation for Suppliers Selling to Both Domestic PV and Export Programmes](https://www.terra-insight.com/insights/jlr-tata-motors-domestic-vs-export-supplier-reconciliation/)
- [JPC Steel Price Index for RMPV Claims: A Tier-1 Auto-Component Supplier Guide](https://www.terra-insight.com/insights/jpc-steel-price-index-rmpv-auto-india/)
- [Kanban vs MRP-Based Delivery: How the Supply Model Affects Auto-Component Reconciliation](https://www.terra-insight.com/insights/kanban-vs-mrp-delivery-reconciliation-auto-india/)
- [Line-Stop Charges and Liquidated Damages in Indian Auto Supply: Accounting Treatment](https://www.terra-insight.com/insights/line-stop-charge-liquidated-damages-auto-india/)
- [LME Aluminium and Copper Pricing for Indian Auto-Component RMPV Claims](https://www.terra-insight.com/insights/lme-aluminium-copper-pricing-rmpv-auto-india/)
- [Maruti e-Nagare for Delivery Schedule Reconciliation: A Finance Team Guide](https://www.terra-insight.com/insights/maruti-e-nagare-delivery-reconciliation-india/)
- [Multi-Hop Job Work in Auto Components: Challan Tracking Across 3-4 Vendors Without Section 143 Default](https://www.terra-insight.com/insights/multi-hop-job-work-challan-tracking-auto-india/)
- [OEM Debit Note Disputes: When to Accept, When to Contest (Indian Auto Components)](https://www.terra-insight.com/insights/oem-debit-note-dispute-accept-vs-contest-auto-india/)
- [Oracle ERP Cloud (Fusion) for Auto-Component Manufacturers: Reconciliation Gaps to Address](https://www.terra-insight.com/insights/oracle-erp-cloud-auto-component-reconciliation-gaps/)
- [Plastic Injection Moulding Reconciliation for Auto Components: Material, Tooling and OEM-Owned Moulds](https://www.terra-insight.com/insights/plastic-injection-moulding-reconciliation-auto-india/)
- [Rubber and Polymer Component Reconciliation for Indian Auto Suppliers: Hoses, Bushes, Seals](https://www.terra-insight.com/insights/rubber-polymer-component-reconciliation-auto-india/)
- [SAP ABAP Custom Reports Indian Auto-Component Tier-1s Actually Build](https://www.terra-insight.com/insights/sap-abap-custom-reports-auto-component-reconciliation/)
- [SAP Companion Products for Auto-Component Reconciliation: Why Native SAP Falls Short](https://www.terra-insight.com/insights/sap-companion-product-positioning-auto-india/)
- [Scheduling Agreement vs Purchase Order: Financial Implications for Indian Auto Component Suppliers](https://www.terra-insight.com/insights/scheduling-agreement-vs-purchase-order-auto-india/)
- [Sorting Back-Charges from OEMs: How Indian Auto Suppliers Account for Them](https://www.terra-insight.com/insights/sorting-back-charge-oem-accounting-auto-india/)
- [Stamping and Pressing Process Reconciliation for Indian Auto-Component Suppliers](https://www.terra-insight.com/insights/stamping-pressing-process-reconciliation-auto-india/)
- [Supplementary Invoices for RMPV Price Escalation: GST Section 34 Treatment for Auto Suppliers](https://www.terra-insight.com/insights/supplementary-invoice-price-escalation-gst-section-34-auto-india/)
- [Tally Prime Workarounds for Auto-Component Tier-2 and Tier-3 Suppliers](https://www.terra-insight.com/insights/tally-prime-auto-component-workarounds/)
- [Tata Motors Supplier Portal (TML SRM): Delivery Data Extraction for Finance Teams](https://www.terra-insight.com/insights/tata-supplier-portal-srm-delivery-reconciliation/)
- [Toyota Kirloskar Motor Supplier Reconciliation: TPS, Heijunka and Indian Tax Overlay](https://www.terra-insight.com/insights/toyota-kirloskar-supplier-reconciliation-india/)
- [Yield Reconciliation in Auto-Component Stamping: Skeleton Scrap, FI Steel and Section 394 TCS](https://www.terra-insight.com/insights/yield-reconciliation-stamping-skeleton-scrap-auto-india/)
- [ZF and Continental India Tier-1 Reconciliation: Global Captive Operating Model](https://www.terra-insight.com/insights/zf-continental-india-supplier-reconciliation/)
- [Bosch India SupplyOn Portal: Delivery Data and ASN Reconciliation for Tier-2 Suppliers](https://www.terra-insight.com/insights/bosch-supplyon-portal-asn-reconciliation-india/)
- [E-Invoice and E-Way Bill for Auto-Component JIT Delivery: High-Frequency Despatch Compliance](https://www.terra-insight.com/insights/e-invoice-e-way-bill-auto-component-jit-india/)
- [Form 26AS / Form 168 Reconciliation for Auto-Component Suppliers: OEM TDS Mismatch Resolution](https://www.terra-insight.com/insights/form-26as-reconciliation-auto-component-supplier-india/)
- [GST Credit Note on OEM Price Reduction: Section 34 Timeline and Compliance for Auto Suppliers](https://www.terra-insight.com/insights/gst-credit-note-oem-price-reduction-section-34-auto/)
- [GSTR-2B Reconciliation for Auto-Component Manufacturers with Job-Work Inputs](https://www.terra-insight.com/insights/gstr-2b-reconciliation-auto-component-job-work-india/)
- [Mahindra & Mahindra Supplier Payment and Debit-Note Handling for Auto-Component Suppliers](https://www.terra-insight.com/insights/mahindra-supplier-payment-debit-note-handling/)
- [PLI Auto Scheme Claim Process for FY 2026-27: How Auto-Component Suppliers File and Track Claims](https://www.terra-insight.com/insights/pli-auto-scheme-claim-process-fy-2026-27-india/)
- [PPM Quality Metric for Auto-Component Suppliers: What Finance Teams Need to Know](https://www.terra-insight.com/insights/ppm-quality-metric-auto-component-finance-india/)
- [Returnable Packaging GST: When Does a KLT Bin Become a Taxable Supply (Auto Components)?](https://www.terra-insight.com/insights/returnable-packaging-gst-klt-bin-auto-india/)
- [Rule 37 ITC Reversal Risk on OEM Unpaid Invoices: What Auto-Component CFOs Must Know](https://www.terra-insight.com/insights/rule-37-itc-reversal-oem-receivables-auto-india/)
- [Rule 55 Delivery Challan for Auto Components: FI Material, KLT Bins, Job Work Movement](https://www.terra-insight.com/insights/rule-55-delivery-challan-auto-component-fi-bins-job-work/)
- [Section 143 Deemed Supply: What Happens When Job-Work Goods Don't Return in Time (Auto Components)](https://www.terra-insight.com/insights/section-143-deemed-supply-auto-component-india/)
- [Tally Prime for Auto-Component Manufacturers: Reconciliation Limits and Workarounds](https://www.terra-insight.com/insights/tally-prime-auto-component-reconciliation-limits-india/)
- [Tata Motors Tier-1 Supplier Reconciliation: JLR vs Domestic OEM Settlement Differences](https://www.terra-insight.com/insights/tata-motors-tier1-supplier-reconciliation-india/)
- [Section 394 TCS on Scrap Sale by Auto Component Manufacturers: Payment Code 1071 (FY 2026-27)](https://www.terra-insight.com/insights/tcs-scrap-sale-section-394-auto-component-india/)
- [Tooling Cost Recovery and Amortisation for Auto-Component Programmes: Models Explained](https://www.terra-insight.com/insights/tooling-cost-recovery-amortisation-auto-component-india/)
- [Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ](https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india/)
- [Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers](https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india/)
- [CUM Quantity Drift: The Auto-Component Reconciliation Problem Nobody Talks About](https://www.terra-insight.com/insights/cum-quantity-drift-auto-component-india/)
- [EDI 830, 862, and 856 for Indian Auto-Component Suppliers: A Finance Team Primer](https://www.terra-insight.com/insights/edi-830-862-856-india-auto-component-finance-primer/)
- [Free-Issue Material Accounting for Indian Auto Stamping Suppliers](https://www.terra-insight.com/insights/free-issue-material-accounting-auto-stamping-india/)
- [Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers](https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india/)
- [GST Rate on Auto Components in India: 28% vs 18% vs 5% — Which Rate Applies?](https://www.terra-insight.com/insights/gst-rate-auto-component-india-28-vs-18-vs-5/)
- [ITC-04 Filing for Auto-Component Manufacturers: A Step-by-Step Guide](https://www.terra-insight.com/insights/itc-04-filing-auto-component-step-by-step-india/)
- [Maruti Suzuki Supplier Settlement Process: Payment Terms, Debit Notes, and Reconciliation](https://www.terra-insight.com/insights/maruti-suzuki-supplier-settlement-process-india/)
- [OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers](https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india/)
- [How Indian Auto Component Suppliers Handle OEM Short-Pays: A Finance Team Guide](https://www.terra-insight.com/insights/oem-short-pay-handling-auto-component-india/)
- [Raw Material Price Escalation Clause Reconciliation for Indian Auto Components](https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india/)
- [Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers](https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india/)
- [RMPV Calculation Formula for Auto-Component Suppliers: Step-by-Step Worked Examples](https://www.terra-insight.com/insights/rmpv-calculation-formula-auto-component-india/)
- [Raw Material Price Variation (RMPV) Clauses in Auto-Component Contracts: How They Actually Work](https://www.terra-insight.com/insights/rmpv-clause-auto-component-india-explained/)
- [SAP Scheduling Agreement Reconciliation for Auto Component Suppliers: What SAP Doesn't Do](https://www.terra-insight.com/insights/sap-scheduling-agreement-reconciliation-auto-india/)
- [Section 393(1) Sl. 6(i) TDS on Auto-Component Job Work: Rate, Threshold and FY 2026-27 Compliance](https://www.terra-insight.com/insights/section-194c-tds-auto-component-job-work-india/)
- [Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)](https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india/)
- [Why OEMs Pay 8-12% Less Than Invoice Value — And How Indian Auto Suppliers Reconcile the Gap](https://www.terra-insight.com/insights/why-oem-pays-less-than-invoice-auto-component-india/)
- [Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns](https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india/)
- [OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components](https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india/)
- [PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27](https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india/)
- [Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers](https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india/)

## Insights: EV Component Reconciliation (PLI-ACC, FAME-II)

- [E-Axle Supplier Reconciliation for Indian EV OEMs: Modular vs Integrated Supply](https://www.terra-insight.com/insights/e-axle-supplier-reconciliation-india/)
- [EV BMS Supplier Reconciliation under FAME-II: Indian Component Manufacturer Guide](https://www.terra-insight.com/insights/ev-bms-supplier-reconciliation-fame-ii-india/)
- [EV Battery Cell Supplier Reconciliation under PLI-ACC: Indian Manufacturer Guide](https://www.terra-insight.com/insights/ev-battery-cell-supplier-reconciliation-india-pli-acc/)
- [EV Charging Infrastructure Revenue Recognition and GST Treatment in India](https://www.terra-insight.com/insights/ev-charging-infrastructure-revenue-recognition-gst-india/)
- [EV Motor Controller Supplier Reconciliation under PLI-Auto Champion Scheme](https://www.terra-insight.com/insights/ev-motor-controller-pli-auto-supplier-india/)
- [Swappable Battery-as-a-Service (BaaS) Reconciliation for Indian EV OEMs](https://www.terra-insight.com/insights/swappable-battery-as-a-service-baas-reconciliation-india/)

## Insights: Healthcare Reconciliation

- [Diagnostic Lab Revenue Reconciliation: Test Aggregator and B2B Channel Recovery](https://www.terra-insight.com/insights/diagnostic-lab-revenue-reconciliation-india/)
- [Hospital Chain Multi-Location Revenue Reconciliation: A CFO Guide for Indian Healthcare](https://www.terra-insight.com/insights/hospital-chain-multi-location-reconciliation-india/)
- [IRDAI Insurance TPA Payout Reconciliation for Indian Hospitals](https://www.terra-insight.com/insights/irdai-insurance-tpa-payout-reconciliation-india/)
- [Medical Device Supplier Reconciliation for Indian Hospitals](https://www.terra-insight.com/insights/medical-device-supplier-reconciliation-india/)
- [Medical Tourism Foreign Patient Revenue Reconciliation for Indian Hospitals](https://www.terra-insight.com/insights/medical-tourism-foreign-patient-reconciliation-india/)
- [Pharmacy Stockist Reconciliation for Indian Pharma Distribution](https://www.terra-insight.com/insights/pharmacy-stockist-reconciliation-india/)
- [Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals](https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation/)
- [Cashless Claim Settlement Reconciliation for Hospitals and Insurers](https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation/)
- [CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims](https://www.terra-insight.com/insights/cghs-reconciliation-india/)
- [ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching](https://www.terra-insight.com/insights/echs-reconciliation-india/)
- [Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India](https://www.terra-insight.com/insights/hospital-billing-reconciliation-india/)
- [Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India](https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india/)
- [IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals](https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india/)
- [TPA Settlement Reconciliation for Indian Hospitals](https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india/)

## Insights: IT Services and SaaS Reconciliation

- [ESOP and RSU Accounting for IT Services Companies under Ind AS 102](https://www.terra-insight.com/insights/esop-rsu-accounting-it-services-ind-as-102/)
- [GST on SaaS Exports: Section 2(6) IGST Compliance and LUT Filing](https://www.terra-insight.com/insights/gst-export-services-saas-india-section-2-6-foreign-exchange/)
- [GST Input Tax Credit for SaaS and IT Services: Rule 42/43 and Mixed Use](https://www.terra-insight.com/insights/gst-input-tax-credit-reversal-saas-india/)
- [Multi-Currency Revenue Recognition for IT Services under Ind AS 115](https://www.terra-insight.com/insights/multi-currency-revenue-recognition-it-services-ind-as-115/)
- [Section 393(2) TDS on Foreign Software Licences: Royalty vs Service Distinction](https://www.terra-insight.com/insights/section-413-tds-foreign-software-license-india/)
- [Transfer Pricing for IT Services Captive: Section 92CA Compliance and APA](https://www.terra-insight.com/insights/transfer-pricing-it-services-section-92ca-india/)
- [Deferred Revenue Reconciliation for Indian SaaS Companies](https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india/)
- [Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies](https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india/)
- [Milestone Billing Reconciliation for IT Services Companies in India](https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services/)
- [Multi-Currency Reconciliation for Indian IT Services Companies](https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india/)
- [SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching](https://www.terra-insight.com/insights/saas-subscription-reconciliation-india/)
- [Time-and-Material Billing Reconciliation for Indian IT Companies](https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india/)

## Insights: Definitions and Glossary

- [What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams](https://www.terra-insight.com/insights/what-is-a-reconciliation-statement/)
- [What Is Bank Reconciliation? Definition and Process for Indian Finance Teams](https://www.terra-insight.com/insights/what-is-bank-reconciliation/)
- [What Is Automated Reconciliation? How It Differs from Manual Matching](https://www.terra-insight.com/insights/what-is-automated-reconciliation/)
- [What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses](https://www.terra-insight.com/insights/what-is-form-26as/)
- [What Is GSTR-2B? The Auto-Populated ITC Statement Explained](https://www.terra-insight.com/insights/what-is-gstr-2b/)
- [What Is ITC in GST? Input Tax Credit Explained for Indian Businesses](https://www.terra-insight.com/insights/what-is-itc-in-gst/)
- [What Is NACH in Banking? National Automated Clearing House Explained](https://www.terra-insight.com/insights/what-is-nach/)
- [What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account](https://www.terra-insight.com/insights/what-is-payment-gateway-settlement/)
- [What Is TDS Deduction? How Tax Deducted at Source Works in India](https://www.terra-insight.com/insights/what-is-tds-deduction/)
- [What Is a UTR Number? Unique Transaction Reference in Indian Banking](https://www.terra-insight.com/insights/what-is-utr-number/)

## Insights: Reconciliation Glossary

- [What is Cash Application (Cash App) in Receivables Reconciliation: Indian Finance Reference](https://www.terra-insight.com/insights/what-is-cash-app-cash-application-glossary/)
- [What is a Debit Note vs Credit Note under GST Section 34: Indian Reference](https://www.terra-insight.com/insights/what-is-debit-note-credit-note-section-34-glossary/)
- [What is Form 168 in Income Tax Act 2025: TDS Credit Statement Replacing Form 26AS for FY 2026-27 onwards](https://www.terra-insight.com/insights/what-is-form-168-tds-glossary/)
- [What is ITC-04: Job Work Quarterly Form Explained for Indian Manufacturers](https://www.terra-insight.com/insights/what-is-itc-04-job-work-glossary/)
- [What is RMPV (Raw Material Price Variation): Auto-Component Index-Linked Pricing](https://www.terra-insight.com/insights/what-is-rmpv-raw-material-price-variation-glossary/)
- [What is Three-Way Matching in Indian Accounts Payable: PO–GRN–Invoice Reconciliation](https://www.terra-insight.com/insights/what-is-three-way-match-india-glossary/)
- [What is a Virtual Account in Bank Reconciliation: Indian Treasury Reference](https://www.terra-insight.com/insights/what-is-virtual-account-bank-reconciliation-glossary/)
- [Financial Reconciliation Dictionary: Terms Used in Indian Finance Operations](https://www.terra-insight.com/insights/financial-reconciliation-dictionary-india/)
- [GST Reconciliation Glossary: Terms Every Finance Team Must Know](https://www.terra-insight.com/insights/gst-reconciliation-glossary-india/)
- [NACH and Payments Glossary: Key Terms for Reconciliation](https://www.terra-insight.com/insights/nach-payments-glossary-india/)
- [Platform Settlement Glossary: Terms for E-Commerce and Payment Gateway Finance Teams](https://www.terra-insight.com/insights/platform-settlement-glossary-india/)
- [TDS Glossary: Essential Terms for TDS Reconciliation in India](https://www.terra-insight.com/insights/tds-glossary-india/)

## Insights: Bank Statement Analysis — TransactIQ

- [Bank Statement Analysis India: What Lenders and NBFCs Actually Check](https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india/)
- [Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions](https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals/)
- [Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It](https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india/)
- [Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions](https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases/)
- [Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know](https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit/)
- [How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders](https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk/)
- [Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams](https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review/)

## Insights: Bank Statement Fraud and Forensics

- [PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity](https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india/)
- [Balance Chain Verification: Catching Altered Bank Statements Row by Row](https://www.terra-insight.com/insights/balance-chain-verification-bank-statement/)
- [Bank Statement PDF Metadata Inspection: What Credit Teams Should Check](https://www.terra-insight.com/insights/bank-statement-metadata-inspection/)
- [Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements](https://www.terra-insight.com/insights/counterparty-spread-analysis-statements/)
- [Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works](https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements/)
- [Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review](https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement/)
- [Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics](https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements/)
- [Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic](https://www.terra-insight.com/insights/round-number-clustering-fraud-detection/)

## Insights: Bank Statement OCR and Parsing

- [Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs](https://www.terra-insight.com/insights/bank-statement-ocr-india/)
- [Bank Statement Column Variants in India: Why 300+ Format Patterns Exist](https://www.terra-insight.com/insights/bank-statement-column-variant-parsing/)
- [PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs](https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india/)
- [Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge](https://www.terra-insight.com/insights/co-operative-bank-statement-ocr/)
- [Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work](https://www.terra-insight.com/insights/multi-statement-upload-reconciliation/)
- [Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them](https://www.terra-insight.com/insights/password-protected-bank-statement-india/)
- [PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers](https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges/)
- [Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs](https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india/)

## Insights: Bank Statement Risk Word Signals

- [Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained](https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements/)
- [Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders](https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements/)
- [Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why](https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements/)
- [Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders](https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements/)
- [Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators](https://www.terra-insight.com/insights/financial-distress-signals-bank-statements/)
- [Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams](https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements/)
- [Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals](https://www.terra-insight.com/insights/over-leverage-detection-bank-statements/)
- [Predatory Lending App Detection in Bank Statements: What Indian Lenders Check](https://www.terra-insight.com/insights/predatory-lending-app-detection-india/)
- [Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders](https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements/)
- [Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them](https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements/)

## Insights: MSME Synthetic Financial Statements

- [Synthetic Financial Statements for MSME Credit: What They Are and How They Work](https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india/)
- [Cash Flow Analysis for MSME Lending Using Bank Statement Data](https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india/)
- [MSME Credit Assessment Without Audited Financials: The Bank Statement Approach](https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india/)
- [Constructing a Synthetic P&L for MSMEs from Bank Transaction Data](https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india/)
- [MSME Working Capital Assessment from Bank Statement Analysis](https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement/)
- [Personal vs Business Transaction Separation in MSME Bank Statements](https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme/)
- [Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate](https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement/)

## Insights: product-principles

- [Accounting Identity Gates in Reconciliation: Money Conservation for Indian Finance Teams](https://www.terra-insight.com/insights/accounting-identity-gates-reconciliation-money-conservation-india/)
- [Deterministic Reconciliation and Audit Reproducibility Under Indian Statute](https://www.terra-insight.com/insights/deterministic-reconciliation-audit-reproducibility-india/)
- [Machine-Readable Evidence Trail: Reconciliation Audit Defensibility in India](https://www.terra-insight.com/insights/machine-readable-evidence-trail-reconciliation-audit-defensibility/)
- [One Engine, 24 Industry Presets: Multi-Tenant Reconciliation Architecture for Indian Businesses](https://www.terra-insight.com/insights/one-engine-24-industry-presets-reconciliation-architecture-india/)
- [Paise-Exact Decimal Half-Up Rounding — The India Reconciliation Convention](https://www.terra-insight.com/insights/paise-exact-decimal-round-half-up-india-reconciliation-convention/)

## Insights: agro-processing

- [Agro Processing Reconciliation India: Nine Sub-Verticals Master Cornerstone](https://www.terra-insight.com/insights/agro-processing-reconciliation-india-nine-sub-verticals-master/)
- [Agrochemical Manufacturer CIB&RC Registration + GST Reconciliation India](https://www.terra-insight.com/insights/agrochemical-manufacturer-cibrc-registration-reconciliation-india/)
- [Avanti Feeds Shrimp Feed Reconciliation — Thai Union JV](https://www.terra-insight.com/insights/avanti-feeds-shrimp-feed-reconciliation-thai-union-jv/)
- [Bajaj Hindusthan Sugar Farmer Payment Arrears Tracker Reconciliation](https://www.terra-insight.com/insights/bajaj-hindusthan-sugar-farmer-payment-arrears-tracker/)
- [Basmati Rice Export Reconciliation — MEP + RoDTEP India Cornerstone](https://www.terra-insight.com/insights/basmati-rice-export-reconciliation-mep-rodtep-india/)
- [Bayer CropScience India Reconciliation — Import + Formulate + Distribute](https://www.terra-insight.com/insights/bayer-cropscience-india-msil-reconciliation-import-formulate/)
- [Britannia Dairy Cheese and Curd Modern Trade Reconciliation](https://www.terra-insight.com/insights/britannia-dairy-cheese-curd-modern-trade-reconciliation/)
- [CCL Products Instant Coffee B2B Export Reconciliation India](https://www.terra-insight.com/insights/ccl-products-instant-coffee-b2b-export-reconciliation/)
- [Coastal Corporation Marine Export Reconciliation — Visakhapatnam](https://www.terra-insight.com/insights/coastal-corporation-marine-export-reconciliation-visakhapatnam/)
- [Coromandel International NPK Complex NBS Claim Reconciliation](https://www.terra-insight.com/insights/coromandel-international-npk-complex-nbs-claim-reconciliation/)
- [Dairy Inverted-Duty Refund under Rule 89(5) — Post-GST-2.0 (2026)](https://www.terra-insight.com/insights/dairy-inverted-duty-refund-rule-89-5-post-gst-2-0-2026/)
- [Dairy Reconciliation in India: Fat + SNF Milk Procurement Cornerstone](https://www.terra-insight.com/insights/dairy-reconciliation-fat-snf-milk-procurement-india/)
- [Devi Sea Foods Processing Plant Reconciliation — Andhra Pradesh](https://www.terra-insight.com/insights/devi-sea-foods-processing-plant-reconciliation-ap/)
- [Dhampur Sugar Distillery Molasses vs Cane-Juice Ethanol Reconciliation](https://www.terra-insight.com/insights/dhampur-sugar-distillery-molasses-cane-juice-ethanol/)
- [Dwarikesh Sugar EBP Ethanol Blending 2025-26 Reconciliation](https://www.terra-insight.com/insights/dwarikesh-sugar-ebp-ethanol-blending-2025-26-reconciliation/)
- [Edible Oil Chapter 15 IDS Refund Blocked — Notification 09/2022 India](https://www.terra-insight.com/insights/edible-oil-chapter-15-idr-refund-blocked-notification-09-2022-india/)
- [EID Parry Integrated Sugar Reconciliation — Cargill JV Refined Sugar](https://www.terra-insight.com/insights/eid-parry-integrated-sugar-recon-cargill-jv/)
- [FCI Custom Milling Rice (CMR) Outturn Reconciliation for Millers](https://www.terra-insight.com/insights/fci-custom-milling-rice-cmr-outturn-reconciliation/)
- [Fertilizer DBT: NBS vs Urea Cost-Plus Reconciliation India Cornerstone](https://www.terra-insight.com/insights/fertilizer-dbt-nbs-vs-urea-cost-plus-reconciliation-india/)
- [GNFC, Chambal, RCF Urea Cost-Plus Reconciliation India](https://www.terra-insight.com/insights/gnfc-chambal-rcf-urea-cost-plus-reconciliation-india/)
- [Godrej Tyson Real Good Chicken Modern Trade Reconciliation](https://www.terra-insight.com/insights/godrej-tyson-real-good-chicken-modern-trade-reconciliation/)
- [Hatsun Agro Arokya Milk Tamil Nadu Reconciliation](https://www.terra-insight.com/insights/hatsun-agro-arokya-milk-tamil-nadu-reconciliation/)
- [Heritage Foods Milk Procurement Reconciliation — AP + Telangana](https://www.terra-insight.com/insights/heritage-foods-milk-procurement-ap-telangana-reconciliation/)
- [HUL Bru Coffee Reconciliation — Plantation Purchase vs Instant Manufacture](https://www.terra-insight.com/insights/hul-bru-coffee-reconciliation-plantation-vs-instant/)
- [IB Group Poultry Feed Reconciliation — Input Tax Credit Discipline](https://www.terra-insight.com/insights/ib-group-poultry-feed-reconciliation-input-tax-credit/)
- [IFFCO Cooperative Fertilizer DBT Claim Reconciliation](https://www.terra-insight.com/insights/iffco-cooperative-fertilizer-dbt-claim-reconciliation/)
- [Kaveri Seed Bt Cotton Trait-Fee Reconciliation India](https://www.terra-insight.com/insights/kaveri-seed-bt-cotton-trait-fee-reconciliation-india/)
- [Kohinoor Foods Basmati Export FX Realisation Reconciliation](https://www.terra-insight.com/insights/kohinoor-foods-basmati-export-fx-realisation-reconciliation/)
- [KRBL India Gate Basmati Mandi Procurement Reconciliation](https://www.terra-insight.com/insights/krbl-india-gate-basmati-mandi-procurement-reconciliation/)
- [LT Foods Daawat Basmati Export Reconciliation — Royal + Devaaya](https://www.terra-insight.com/insights/lt-foods-daawat-basmati-export-recon-royal-devaaya/)
- [Mother Dairy Cooperative Settlement Reconciliation for Milk Producers](https://www.terra-insight.com/insights/mother-dairy-cooperative-settlement-reconciliation/)
- [Nestle India Dairy Whitener Supply Chain Reconciliation](https://www.terra-insight.com/insights/nestle-india-dairy-whitener-supply-chain-reconciliation/)
- [Parag Milk Foods Mozzarella PLISFPI Claim Reconciliation](https://www.terra-insight.com/insights/parag-milk-foods-mozzarella-plisfpi-claim-reconciliation/)
- [Poultry Contract Farming Reconciliation — Broiler India Cornerstone](https://www.terra-insight.com/insights/poultry-contract-farming-reconciliation-broiler-india/)
- [Rallis India + Sumitomo Chemical India Agrochemical Distributor Reconciliation](https://www.terra-insight.com/insights/rallis-india-sumitomo-chemical-agrochemical-distributor-recon/)
- [Rasi Seed Hybrid Cotton Farmer Buyback Reconciliation](https://www.terra-insight.com/insights/rasi-seed-hybrid-cotton-farmer-buyback-reconciliation/)
- [Shrimp Aquaculture MPEDA Export Reconciliation India Cornerstone](https://www.terra-insight.com/insights/shrimp-aquaculture-mpeda-export-reconciliation-india/)
- [Skylark Hatcheries Feed Formulation Reconciliation and FCR Metrics](https://www.terra-insight.com/insights/skylark-hatcheries-feed-formulation-reconciliation-fcr/)
- [Sugar Mill FRP Cane Payment Reconciliation India — 14-Day Rule + 15% Interest](https://www.terra-insight.com/insights/sugar-mill-frp-cane-payment-reconciliation-india/)
- [Sugarcane SAP vs FRP Reconciliation — Uttar Pradesh + Punjab](https://www.terra-insight.com/insights/sugarcane-sap-vs-frp-reconciliation-uttar-pradesh-punjab/)
- [Tata Consumer Tetley Global Tea Reconciliation — Brand + Export](https://www.terra-insight.com/insights/tata-consumer-tetley-global-tea-recon-brand-export/)
- [Tea Auction Settlement Reconciliation — Kolkata + Coonoor + Guwahati Cornerstone](https://www.terra-insight.com/insights/tea-auction-settlement-reconciliation-kolkata-coonoor-guwahati/)
- [Venky's Hatchery Broiler Breeding Reconciliation India](https://www.terra-insight.com/insights/venkys-hatchery-broiler-breeding-reconciliation-india/)
- [Wagh Bakri Tea Packet Modern Trade Reconciliation](https://www.terra-insight.com/insights/wagh-bakri-tea-packet-modern-trade-reconciliation/)
- [Waterbase and Nekkanti Shrimp Feed + Export Integrated Reconciliation](https://www.terra-insight.com/insights/waterbase-nekkanti-shrimp-feed-export-integrated-reconciliation/)

## Insights: textiles

- [BCD on Cotton Imports — Customs Duty Reconciliation for Textile India](https://www.terra-insight.com/insights/bcd-cotton-imports-customs-textile-india/)
- [Branded Apparel Reconciliation in India — Section 9(1) vs 9(5) Clarification](https://www.terra-insight.com/insights/branded-apparel-reconciliation-india-section-9-1-vs-9-5/)
- [CCI Cotton Corporation of India Procurement Reconciliation](https://www.terra-insight.com/insights/cci-cotton-corporation-india-procurement-reconciliation/)
- [CMP (Conversion Manufacturing Price) Garment Export Reconciliation](https://www.terra-insight.com/insights/cmp-conversion-manufacturing-price-garment-export-reconciliation/)
- [Cotton Bale Quality Testing and CCI Lab Recovery Reconciliation](https://www.terra-insight.com/insights/cotton-bale-quality-testing-cci-recovery-reconciliation/)
- [Cotton Supply Chain Reconciliation for Textile India](https://www.terra-insight.com/insights/cotton-supply-chain-reconciliation-textile-india/)
- [Customs BCD on Cotton + MMF Textile Import Reconciliation](https://www.terra-insight.com/insights/customs-bcd-cotton-mmf-textile-import-reconciliation/)
- [DPIIT Compliance for PLI Textile Claim — Annual Reporting Reconciliation](https://www.terra-insight.com/insights/dpiit-compliance-pli-textile-claim-reconciliation/)
- [Dyeing & Printing Job-Work TDS — Section 393(1) Code 1023 for Textile](https://www.terra-insight.com/insights/dyeing-printing-job-work-textile-tds-code-1023/)
- [e-BRC (Electronic Bank Realisation Certificate) Textile Export Reconciliation](https://www.terra-insight.com/insights/e-brc-electronic-bank-realisation-certificate-textile-export/)
- [E-Invoicing for Textile under ₹5 Crore Threshold — IRN Reconciliation](https://www.terra-insight.com/insights/e-invoicing-textile-5-crore-threshold-irn-reconciliation/)
- [EPCG Capital Goods Reconciliation for Textile Manufacturers](https://www.terra-insight.com/insights/epcg-export-promotion-capital-goods-textile-reconciliation/)
- [Fabric-to-Garment Inverted-Duty Refund Reconciliation for Textile](https://www.terra-insight.com/insights/fabric-garment-inverted-duty-refund-textile/)
- [Free-Issue Yarn/Fabric for Job-Work Reconciliation in Textile Industry](https://www.terra-insight.com/insights/free-issue-yarn-fabric-job-work-reconciliation-textile/)
- [GST Textile Rate Rationalisation — Sept 2025 Impact Reconciliation](https://www.terra-insight.com/insights/gst-textile-rate-rationalisation-sept-2025-impact/)
- [Hank Yarn vs Cone Yarn Duty Differential Reconciliation for Textile](https://www.terra-insight.com/insights/hank-yarn-cone-yarn-duty-differential-textile-reconciliation/)
- [ITC-04 Quarterly Return Reconciliation for Textile Job-Work](https://www.terra-insight.com/insights/itc-04-quarterly-return-textile-job-work-reconciliation/)
- [Ludhiana Hosiery and Woollen Cluster Reconciliation](https://www.terra-insight.com/insights/ludhiana-hosiery-woollen-cluster-reconciliation/)
- [MAT/AMT vs PLI Textile Claim — Tax Treatment Reconciliation](https://www.terra-insight.com/insights/mat-amt-pli-textile-claim-tax-treatment-reconciliation/)
- [MEIS Legacy Claim Reconciliation for Textile Exporters](https://www.terra-insight.com/insights/meis-legacy-claim-reconciliation-textile-export/)
- [Multi-Hop Job-Work Reconciliation for Textile Manufacturing in India](https://www.terra-insight.com/insights/multi-hop-job-work-reconciliation-textile-india/)
- [Myntra, Ajio, Flipkart Fashion Apparel Settlement Reconciliation](https://www.terra-insight.com/insights/myntra-ajio-flipkart-fashion-apparel-settlement-reconciliation/)
- [Net ITC Exclusion of Input Services and Capital Goods — Rule 89(5) Textile](https://www.terra-insight.com/insights/net-itc-input-services-capital-goods-exclusion-rule-89-5-textile/)
- [OEKO-TEX, GOTS Compliance Reconciliation for Textile India](https://www.terra-insight.com/insights/oeko-tex-gots-compliance-reconciliation-textile-india/)
- [Panipat Home Textile and Recycled Yarn Reconciliation](https://www.terra-insight.com/insights/panipat-home-textile-recycled-yarn-reconciliation/)
- [PLI MMF Apparel + Fabric Claim Reconciliation](https://www.terra-insight.com/insights/pli-mmf-apparel-fabric-claim-reconciliation/)
- [PLI MMF + Technical Textile Claim Reconciliation for India](https://www.terra-insight.com/insights/pli-mmf-technical-textile-claim-reconciliation-india/)
- [PLI Technical Textile (Medical, Agro, Packaging) Claim Reconciliation](https://www.terra-insight.com/insights/pli-technical-textile-medical-agro-claim/)
- [PLI Textile Machinery Capitalisation and Investment Tracking](https://www.terra-insight.com/insights/pli-textile-machinery-capitalisation-reconciliation/)
- [PLI Textile Minimum Investment Tiers (₹100 cr vs ₹300 cr) Reconciliation](https://www.terra-insight.com/insights/pli-textile-minimum-investment-100-cr-300-cr-tier/)
- [Returns and RTV at Branded Apparel Retail — Credit Note Section 34](https://www.terra-insight.com/insights/returns-rtv-branded-apparel-credit-note-section-34/)
- [GST RFD-01 Monthly Filing for Textile Inverted-Duty Refund](https://www.terra-insight.com/insights/rfd-01-monthly-filing-textile-inverted-duty-refund/)
- [RoDTEP Appendix 4RE — AA, EOU, SEZ Textile Claim Reconciliation](https://www.terra-insight.com/insights/rodtep-appendix-4re-aa-eou-sez-textile-claim/)
- [RoDTEP Appendix 4R DTA Textile Claim Reconciliation](https://www.terra-insight.com/insights/rodtep-appendix-4r-dta-textile-claim/)
- [RoDTEP Claim Reconciliation for Textile Exporters in India](https://www.terra-insight.com/insights/rodtep-claim-reconciliation-textile-india/)
- [RoSCTL Claim Reconciliation for Garment and Made-Ups Exporters](https://www.terra-insight.com/insights/rosctl-claim-reconciliation-garment-made-ups-india/)
- [Rule 55 Delivery Challan Reconciliation for Textile Job-Work](https://www.terra-insight.com/insights/rule-55-delivery-challan-textile-job-work/)
- [Rule 89(5) 2-Year Time Limit for Textile Refund Claim Reconciliation](https://www.terra-insight.com/insights/rule-89-5-2-year-time-limit-textile-refund-claim/)
- [Rule 89(5) Inverted-Duty Refund Reconciliation for Textile India](https://www.terra-insight.com/insights/rule-89-5-inverted-duty-refund-textile-india/)
- [Section 143 Deemed Supply — 1-Year Job-Work Return Rule for Textile](https://www.terra-insight.com/insights/section-143-deemed-supply-textile-job-work-1-year-rule/)
- [Section 43B(h) MSME 45-Day Powerloom Procurement Reconciliation for Textile](https://www.terra-insight.com/insights/section-43b-h-msme-45-day-powerloom-procurement-textile/)
- [SEIS Textile Services Export Reconciliation](https://www.terra-insight.com/insights/seis-textile-services-export-reconciliation/)
- [Surat Synthetic Saree Domestic + Export Reconciliation](https://www.terra-insight.com/insights/surat-synthetic-saree-domestic-export-reconciliation/)
- [TDS on Cotton/Yarn Freight under Section 194C Code 1001 for Textile](https://www.terra-insight.com/insights/tds-cotton-yarn-freight-section-194c-code-1001-textile/)
- [TDS Section 393(1) Codes 1023/1024 for Textile Job-Work](https://www.terra-insight.com/insights/tds-section-393-textile-job-work-codes-1023-1024/)
- [Tiruppur Knitwear Cluster Reconciliation — MSME and Section 43B(h)](https://www.terra-insight.com/insights/tiruppur-knitwear-cluster-reconciliation-msme-msme43bh/)
- [Tiruppur Knitwear Export Reconciliation](https://www.terra-insight.com/insights/tiruppur-knitwear-export-reconciliation/)
- [Trent Westside Apparel VMI Reconciliation](https://www.terra-insight.com/insights/trent-westside-fashion-vmi-reconciliation/)
- [VMI (Vendor Managed Inventory) at Tier-2 Garment Supplier Reconciliation](https://www.terra-insight.com/insights/vendor-managed-inventory-vmi-tier2-garment-supplier-reconciliation/)
- [Yarn-to-Fabric Inverted-Duty Refund — Rule 89(5) Application for Textile](https://www.terra-insight.com/insights/yarn-fabric-inverted-duty-refund-textile-rule-89-5/)

## Insights: jewellery

- [Bullion (B2B) vs Retail (B2C) Jewellery Supply Classification](https://www.terra-insight.com/insights/bullion-vs-retail-gst-supply-classification-jewellery-india/)
- [Damaged Jewellery Return and Section 34 Credit Note for Jewellers](https://www.terra-insight.com/insights/damaged-tampered-jewellery-return-section-34-credit-note-india/)
- [Gold Deposit / Savings Scheme Customer Liability Tracking for Jewellers](https://www.terra-insight.com/insights/deposit-gold-scheme-jewellery-customer-liability-tracking-india/)
- [EMI Scheme Revenue Recognition for Jewellery: Ind AS 115 Point-in-Time vs Over-Time](https://www.terra-insight.com/insights/emi-scheme-jewellery-instalment-plan-revenue-recognition-india/)
- [Jewellery Export Partial Realisation and EEFC Account Reconciliation](https://www.terra-insight.com/insights/export-jewellery-partial-70-percent-realisation-eefc-account-fema-india/)
- [Jewellery Franchise Royalty and Brand-Use Fee Reconciliation](https://www.terra-insight.com/insights/franchise-jewellery-store-royalty-reconciliation-section-194j-india/)
- [Gold Scrap Purchase from Unregistered Suppliers: Reverse Charge Section 9(4)](https://www.terra-insight.com/insights/gold-scrap-purchase-unregistered-supplier-rcm-section-9-4-india/)
- [Gold at 3% vs Making Charges at 5%: HSN Classification and Reconciliation](https://www.terra-insight.com/insights/gold-tax-3-percent-hsn-7113-vs-making-charges-5-percent-cbic-notification/)
- [BIS Hallmarking Charges and Cost Accounting for Jewellers](https://www.terra-insight.com/insights/hallmarking-bis-charges-cost-accounting-jewellery-india/)
- [Mixed-Rate Jewellery Invoice Reconciliation: 3% + 5% + 18% GST on One Bill](https://www.terra-insight.com/insights/jewellery-gst-tax-mixed-invoice-3-5-18-percent-reconciliation-india/)
- [Eighteen Jewellery Reconciliation Scenarios Indian Auditors Actually Ask About](https://www.terra-insight.com/insights/jewellery-reconciliation-scenarios-india-18-audit-defensible-cases/)
- [Jeweller Buying Goods and Giving Job-Work: Section 194C vs 194Q Trap](https://www.terra-insight.com/insights/job-work-gold-jewellery-section-194c-vs-194q-classification-india/)
- [Karigar / Workshop Labour TDS Reconciliation for Jewellers](https://www.terra-insight.com/insights/karigar-workshop-labour-tds-section-194c-code-1001-jewellery/)
- [Gold Metal Loan Reconciliation: Price Fixation on Delivery vs Invoice Day](https://www.terra-insight.com/insights/metal-loan-gold-price-fixation-delivery-day-vs-invoice-day-india/)
- [Old-Gold Exchange Against New Jewellery Purchase: Rule 32(5) Valuation](https://www.terra-insight.com/insights/old-gold-exchange-new-purchase-reconciliation-section-194ia-india/)
- [Diamond and Precious Stone Studding HSN 7102/7103 Reconciliation for Jewellers](https://www.terra-insight.com/insights/stone-diamond-studding-hsn-7102-7103-gst-jewellery-reconciliation/)
- [Gold Wastage and Melting Loss Inventory Reconciliation for Jewellers](https://www.terra-insight.com/insights/wastage-loss-gold-jewellery-manufacturing-inventory-reconciliation/)
- [High-Value Wedding Purchase Reconciliation: Section 269ST Cash Cap and PAN Mandate](https://www.terra-insight.com/insights/wedding-purchase-gst-invoice-vs-cash-jewellery-audit-defensibility-india/)

## Insights: reconciliation-process-design

- [GSTR-2B ITC Reconciliation Failure Modes: How to Prevent Section 16(4) Permanent Losses](https://www.terra-insight.com/insights/gstr-2b-itc-reconciliation-failure-modes-india/)
- [The Reconciliation Control Plan: A One-Page Template for Every Stream](https://www.terra-insight.com/insights/reconciliation-control-plan-template-india/)
- [Reconciliation Failure Analysis: A Process Design Method for Indian Finance Teams](https://www.terra-insight.com/insights/reconciliation-failure-mode-analysis-india/)
- [TDS Reconciliation Failure Modes Against Form 26AS and Form 168: Every Failure Mode That Turns Into a Section 200A Notice](https://www.terra-insight.com/insights/tds-form-26as-reconciliation-failure-modes-india/)

## Insights: reconciliation-playbook

- [GSTR-2B ITC Reconciliation Runbook: The Five-Day Cycle for Indian Finance Teams](https://www.terra-insight.com/insights/gstr-2b-itc-runbook-days-11-15-india/)
- [The Reconciliation Playbook: A Day-by-Day Monthly Close Guide for Indian Finance Teams](https://www.terra-insight.com/insights/reconciliation-playbook-monthly-close-india/)
- [TDS Reconciliation Runbook: Monthly Deposit and Quarterly Form 168 Match for Indian Finance Teams](https://www.terra-insight.com/insights/tds-reconciliation-runbook-monthly-quarterly-india/)
- [Three-Way ITC Reconciliation in Excel: Purchase Register, GSTR-2B, and IMS Actions in One Workbook](https://www.terra-insight.com/insights/three-way-itc-reconciliation-excel-india/)

## Insights: reconciliation-error-catalogue

- [The Carelessness Family: 16 Reconciliation Errors That Come From Working Late](https://www.terra-insight.com/insights/reconciliation-errors-carelessness-india/)
- [The Data Gaps Family: 9 Reconciliation Errors That Are Invisible Until the Arithmetic Forces Them Out](https://www.terra-insight.com/insights/reconciliation-errors-data-gaps-india/)
- [The Knowledge Gaps Family: 11 Reconciliation Errors Where a Wrong Belief Is Applied Consistently](https://www.terra-insight.com/insights/reconciliation-errors-knowledge-gaps-india/)
- [The Misconfigured Systems Family: 11 Reconciliation Errors Where the Software Was Set Up Wrong Years Ago](https://www.terra-insight.com/insights/reconciliation-errors-misconfigured-systems-india/)
- [The Missing and Mistimed Entries Family: 10 Reconciliation Errors That Are Why Reconciliation Exists](https://www.terra-insight.com/insights/reconciliation-errors-missing-mistimed-entries-india/)

## Knowledge cards (847 structured How-To entries)

Each article below emits a HowTo schema.org block with four structured steps — Problem, Logic (How It Is Resolved), Configuration, and Output. This is the machine-readable form of the reconciliation knowledge base.

### Section 194O → §393(1) Sl. 8(v) Code 1035 Cross-Era Mapping (FY 2025-26 / 2026-27 Transition)

Source: https://www.terra-insight.com/insights/194o-section-393-cross-era-mapping-india/

- **Problem:** For FY 2026-27, an e-commerce participant active across the FY 2025-26 / 2026-27 cutover receives TDS credits at 0.1% on two different forms under two different statutes for the same economic activity. Q4 FY 2025-26 sale settlements deducted under Section 194O credit in Form 26AS in May 2026. Q1 FY 2026-27 settlements deducted under §393(1) Sl. 8(v) code 1035 credit in Form 168 in August 2026. Without per-batch deduction-date tagging, the seller cannot tell which form a particular sale belongs on, and ITR filing under-claims or double-claims TDS.
- **Logic:** Reconciliation classifies each marketplace settlement batch by deduction date (the earlier of credit to participant or actual payment). Settlements with deduction date on or before March 31, 2026 are routed to the 194O / Form 26AS bucket. Settlements with deduction date on or after April 1, 2026 are routed to the 1035 / Form 168 bucket. Within each bucket the seller's sales register is reconciled against the respective form on a composite key of marketplace TAN, deduction date, and deductee PAN, with GST gross-up applied to taxable sales before the 0.1% rate is validated.
- **Config:** Marketplace master annotated with TAN per platform. Cross-era ruleset configured with the March 31, 2026 cutover date, mapping legacy Section 194O to new payment code 1035, with deduction-date routing rules that flag settlement batches spanning the boundary. Form 26AS and Form 168 ingestion separated into two collections with linked aggregate views for ITR preparation.
- **Output:** Two reconciled buckets per seller: a closed FY 2025-26 bucket showing every Section 194O deduction tied to a Form 26AS line, and an open FY 2026-27 bucket showing every code 1035 deduction tied to a Form 168 line. ITR schedule populated by summing each bucket; cross-form audit trail showing the deduction date for every batch.

### Form 26AS (Form 168) vs Books Reconciliation for Auto-Component Manufacturers

Source: https://www.terra-insight.com/insights/26as-vs-books-reconciliation-manufacturing-auto-india/

- **Problem:** An Indian Tier-1 auto-component manufacturer with ₹3.6 crore of annual TDS receivable across 6 to 8 OEM TANs — Maruti, Hyundai, Tata Motors, Mahindra, Ashok Leyland, Daimler India — must reconcile every monthly Form 168 download against the supplier's invoice ledger across seven mismatch classes (deductor-deposit gap, wrong section code, wrong PAN, amount difference, period difference, Section 393(1) Sl. 8(ii) versus Section 394(1) confusion, timing) on multiple payment codes (1024 contractor, 1031 purchase, 1057 foreign commission, 1071 scrap TCS), during the FY 2026-27 cross-era window where legacy 194x deductions and new 1001-1092 deductions coexist on the same deductee Form 168 view. Manual reconciliation at this scale leaks 8 to 15% of TDS receivable into never-claimed credit, with the cross-era complication doubling the risk through FY 2026-27.
- **Logic:** Run a monthly Form 168 download routine on the 12th to 15th of every month, segregate entries by deductor TAN and payment code, match each line against the supplier's books on invoice-number / gross-billing / deduction-rate / deduction-amount / period, classify mismatches into the seven recurring classes, route each mismatch into a deductor-correction-required dispute register with TRACES correction tracking, hold legacy 194x lineage and new 1001-1092 lineage on parallel tracks without netting, file a quarterly controller-level reconciliation summary, and close the cross-era overlap through FY 2026-27 with separate dispute columns for legacy and new lineages.
- **Config:** Deductor master with TAN and PAN, applicable payment-code matrix per OEM, supplier invoice ledger with gross-value / GST-split / pre-GST-value / section-code mapping, monthly Form 168 download calendar with TRACES login automation, monthly Form 26AS download for cross-era FY 2025-26 entries still in correction, mismatch classification taxonomy (seven classes), dispute register with deductor-correction-action flag and TRACES tracking, cross-era reconciliation rule routing pre-1-April-2026 deductions to legacy 194x / Form 26AS and post-1-April-2026 deductions to Form 168 / 131 / 141, and a controller-level dashboard of reconciliation health per OEM TAN.
- **Output:** A monthly Form 168 reconciliation dashboard segmented by OEM TAN and payment code, a TDS mismatch dispute register ranked by deductor-action-required status across the seven mismatch classes, a quarterly Form 168 / Form 26AS versus books variance summary for controller-level review, a cross-era register flagging any deduction with code-mismatch during the FY 2026-27 transition, and an audit-defensible trail linking every Form 168 entry to its source invoice, payment code, and TRACES correction history.

### 3PL Settlement Reconciliation for Indian Logistics and Supply-Chain Operators

Source: https://www.terra-insight.com/insights/3pl-settlement-reconciliation-india/

- **Problem:** Indian 3PL operators serving 50 to 500 clients across surface and air networks face five concurrent reconciliation rails — slab-and-zone-banded multi-client tariff settlement, volumetric vs actual weight disputes with 14-day contest windows, COD remittance lifecycle from rider-to-hub-to-client with 5-day average float, Section 34 credit-note flow for failed deliveries within the 30-September-following-FY-end deadline, and SAC 996819 GST plus Section 393(1) Sl. 6(i).D(b) code 1024 TDS on client-side payments.
- **Logic:** Reconcile every AWB against the client-specific tariff card and re-price from the booking record, close volumetric-weight disputes within the 14-day window with one of three outcomes (accepted upgrade, valid contest write-off, unresponded billed), age COD remittance per client per delivery date against the contracted T+X SLA with RTO hold-back release at month-end, file Section 34 credit notes on each failed-delivery AWB tied to the original invoice and reflect in GSTR-1 amendment, and tie SAC 996819 18% service GST output and Section 393(1) Sl. 6(i).D(b) code 1024 TDS deducted by client to the 3PL's quarterly 26AS.
- **Config:** Client master with negotiated tariff card per slab per zone per service tier and SLA-driven remittance offset, AWB master with origin pin, destination pin, declared weight, volumetric L*B*H, declared value, COD flag and service tier, hub re-weigh ingest with photograph and dimension capture per AWB, weight-dispute register with 14-day window and outcome flag, COD escrow ledger with rider-hub-HO-client float visibility, RTO hold-back release schedule per client per month, and credit-note register tied to GSTR-1 amendment date.
- **Output:** A monthly client-wise revenue reconciliation showing billed tariff vs re-priced expected vs accepted disputes with delta classification, AWB-wise weight-dispute status with hub re-weigh evidence and 14-day window flag, COD float position by client by delivery date with RTO hold-back accumulation and release timing, credit-note issuance log tied to original failed-delivery AWB with GSTR-1 amendment month, monthly service GST output reconciliation at 18% SAC 996819 with claimable ITC on inbound expenses, and a quarterly Section 393(1) Sl. 6(i).D(b) code 1024 TDS reconciliation against Form 26AS by client TAN.

### 8D Corrective Action Reports: Financial Reconciliation for Indian Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/8d-corrective-action-quality-financial-impact-auto-india/

- **Problem:** Auto-component finance teams must reconcile the financial impact of every 8D corrective action against quality reserves booked at problem identification, classify D5 tooling modifications as capitalisable under Ind AS 16 vs expensed, track OEM debit-note exposure with the Section 393(1) Sl. 6(i).D(b) code 1024 TDS split on the service portion of warranty back-charges, manage Section 34 credit notes on the goods portion within cutoff, and release unutilised reserves at D8 close-out. Manual tracking creates restatement risk on tooling treatment and lost recovery on debit-note offsets.
- **Logic:** Open a quality-reserve ledger at problem identification (typically D3) under Ind AS 37 with expected sort, rework, scrap, and OEM debit-note exposure. Walk each discipline (D1 through D8) and post actual costs against the reserve. Classify D5 tooling modifications: extends life or improves function → Ind AS 16 capitalisation; like-for-like restoration → expense. Track OEM debit-note exposure separately, splitting goods (Section 34 credit-note offset, 30 Nov cutoff) vs service (warranty back-charge with Section 393(1) Sl. 6(i).D(b) TDS at 2% under code 1024). At D8 close-out, release unutilised reserve to P&L. Map every 8D to its underlying defect-campaign cum-quantity exposure for downstream PPM reporting.
- **Config:** Defect-campaign master with linked 8D, opened reserve, classification rules. 8D event ledger per discipline (D0-D8) with cost feeds (sort, rework, scrap, ECN, tooling, PPAP, qualification). OEM debit-note feed with goods/service split. Ind AS 16 capitalisation classifier with audit-defence trail. Ind AS 37 reserve ledger with provision-actual-release accounting. Section 34 credit-note generator on the goods portion. Section 393(1) Sl. 6(i).D(b) TDS routing on the service portion at 2% under code 1024. PPM cross-link to the cum-quantity exposure of the defect campaign.
- **Output:** Per-8D close-out worksheet showing reserve opened at D3, actual costs charged D3-D8, D5 tooling treatment (capitalised vs expensed under Ind AS 16), OEM debit-note exposure split into goods (Section 34 credit-note offset with cutoff watch) and service (Section 393(1) Sl. 6(i).D(b) code 1024 TDS), unutilised reserve release at D8, and the linked PPM impact on the defect campaign for downstream quality reporting.

### Accounting Identity Gates in Reconciliation: Money Conservation for Indian Finance Teams

Source: https://www.terra-insight.com/insights/accounting-identity-gates-reconciliation-money-conservation-india/

- **Problem:** Reconciliation tools ship reports where the sum of matched, unmatched, and exception buckets does not equal the input total — a stray ₹5,000 lost to a rounding cascade, an orphan entry that fell out of the join because of a null key, or a currency-conversion off-by-one that no one notices until the statutory auditor foots the columns. The residual is small enough to escape casual review and large enough over a year to trigger a Section 128 books-of-account concern, a CARO 2020 statutory-dues disclosure exposure, or a qualified audit opinion on inability to substantiate. Most tools have no built-in check that refuses to publish when the numbers do not tie; they leave the discipline to the human reviewer and hope.
- **Logic:** Before a reconciliation cycle publishes, the engine computes four totals from the same input universe — input total, matched total, unmatched total, exception total — and tests whether matched + unmatched + exceptions equals input to the paisa. This is money conservation as a hard gate: value that enters the cycle must appear in exactly one of the three output buckets. If the identity fails, the run is refused. The engine surfaces the specific failure — the residual amount, the identity violated, and where possible the input rows implicated in the imbalance. The finance team resolves the underlying data quality issue and re-runs. If the identity holds, the report publishes and the identity outcome is recorded in the audit trail alongside the reconciliation result. The same discipline applies to sub-identities within the cycle — bank versus book column tallies, currency-by-currency conservation on multi-currency cycles, and inflow-equals-outflow tests on closed-loop settlement flows.
- **Config:** Reconciliation cycles carry an input universe (bank statement, GL extract, settlement file, or their combination) with a canonical input total. The engine emits matched, unmatched, and exception buckets and runs the identity test before publish. Currency-scoped identities run per currency on multi-currency cycles; bank-versus-book identities run per side on BRS cycles; closed-loop identities test that inflows equal outflows on settlement or intercompany flows. The identity outcome is recorded in the evidence trail with the input total, each bucket total, the residual (which must be zero for publish), and a timestamp. The gate never runs after the report has published — the check is a pre-publish precondition.
- **Output:** A reconciliation cycle either publishes with a machine-verifiable statement that money conservation held (input equals the sum of matched, unmatched, and exceptions, to the paisa), or it does not publish at all and the finance team receives a specific, actionable failure describing what did not tie. Downstream reports — the CARO 2020 statutory-dues disclosure, the Section 44AB tax audit reconciliation, the GSTR-9C reconciliation, the year-end BRS pack for the statutory auditor — inherit that guarantee. Match-rate figures cannot silently drift because the denominators and numerators are cross-footed by the same identity check on every cycle.

### API Imports: Customs Tariff Act 1975 Reconciliation for Formulators

Source: https://www.terra-insight.com/insights/active-pharmaceutical-ingredient-import-customs-tariff-1975/

- **Problem:** A Tier-1 integrated pharma formulator running a Halol formulation plant in Gujarat sources Amoxicillin trihydrate under HSN 2941.10 ex-Shanghai and other Chapter 29 antibiotic APIs from ex-Zhejiang, ex-Jiangsu, ex-Shandong and ex-Italy suppliers. Each shipment carries a Bill of Entry filed by the customs broker at ICEGATE, with Basic Customs Duty at 7.5 percent, Agriculture Infrastructure and Development Cess at 5 percent, and IGST at 5 percent (post 22 September 2025) computed on the assessable value under Section 14 of the Customs Act 1962. The reconciliation surface spans the supplier commercial invoice in USD, the Airway Bill or Bill of Lading, the freight forwarder invoice, the ICEGATE Bill of Entry, the ICEGATE e-payment duty challan, the warehouse receipt at the Halol plant, the Ind AS 21 foreign exchange translation between the invoice-date rate and the BoE-fortnight CBIC reference rate, and the monthly IGST-import ITC availment against Table 4(A)(1) of GSTR-3B and its GSTR-2B reflection. Section 194Q code 1031 does not apply — the customs mechanism substitutes — and mis-deducting 194Q on the overseas supplier remittance creates a downstream Form 26AS mismatch and refund cycle.
- **Logic:** Build a per-shipment Bill of Entry level landed cost workbook keyed on the BoE number and BoE date. Extract the supplier commercial invoice details in USD or EUR, translate to INR at the Ind AS 21 policy rate on the invoice date, and post to the accounts payable subledger. Attach the Airway Bill or Bill of Lading and the freight forwarder invoice. Reconcile the customs-broker BoE against the supplier invoice at HSN classification (2941.10 for penicillins, 2933 or 2934 for heterocyclic-nitrogen compounds, 2942 for other organic compounds), quantity, unit price, CIF value and the 1 percent landing charges load to arrive at the assessable value. Verify BCD at 7.5 percent, AIDC at 5 percent on assessable value, and IGST at 5 percent on the sum of assessable value plus BCD plus AIDC. Match the ICEGATE duty payment challan to the BoE duty computation. Record BCD and AIDC as cost elements in the landed cost (not creditable). Post IGST-import as input tax credit under Section 16 CGST Act to Table 4(A)(1) of GSTR-3B for the tax period of home-consumption clearance. Reconcile the BoE IGST amount against the GSTR-2B ICEGATE reflection for the tax period. Record the Ind AS 21 rate-timing difference between the invoice-date rate and the BoE-fortnight CBIC reference rate.
- **Config:** Import cell master with supplier code, supplier region (China Zhejiang, China Jiangsu, China Shandong, Italy, US, Israel, Spain), HSN classification per API (2941.10 for penicillin-family, 2933 for other heterocyclic nitrogen, 2934 for nucleic-acid derivatives, 2942 for other organic compounds), preferred customs broker and freight forwarder, port of import (Nhava Sheva JNPT, Chennai, Kolkata, ICD Tughlakabad); per-BoE reconciliation register with BoE number, BoE date, supplier invoice reference, USD or EUR value, FOB terms, freight-and-insurance, CIF value, 1 percent landing charges load, assessable value, BCD amount, AIDC amount, IGST amount, ICEGATE duty payment challan reference, out-of-charge date, warehouse receipt date; Ind AS 21 FX ledger with invoice-date rate, BoE-fortnight CBIC reference rate, settlement-date rate, rate-timing differences per shipment; GSTR-3B Table 4(A)(1) IGST-import ITC availment feed and the GSTR-2B ICEGATE-reflected IGST reconciliation; Section 194Q suppression flag on the AP subledger for import supplier codes so the domestic 194Q code 1031 mechanism does NOT fire on non-resident remittances.
- **Output:** A per-tax-period Bill of Entry landed cost pack: shipment-by-shipment BoE-level reconciliation of supplier invoice, freight forwarder invoice, BoE assessable value with BCD, AIDC and IGST computation, ICEGATE duty payment challan, warehouse receipt at the Halol formulation plant, and the Ind AS 21 rate-timing reconciliation. A monthly IGST-import ITC register feeding Table 4(A)(1) of GSTR-3B with the BoE-to-GSTR-2B ICEGATE-reflection tie-out. A per-supplier annual purchase register that surfaces the Rs 50 lakh Section 194Q threshold breach but flags each line as an import (194Q non-applicable, customs mechanism substitutes) so no 194Q TDS is mis-deducted on outbound remittance. The BCD and AIDC per shipment flow into the plant's per-API landed cost per kilogram, which feeds the standard cost setting for the Chapter 30 formulation output and closes back to the plant P&L.

### Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained

Source: https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements/

- **Problem:** Recurring or high-value adult entertainment spending in a bank statement may indicate a discretionary spend allocation that reduces effective repayment capacity, or financial behaviour inconsistent with the applicant's declared income profile.
- **Logic:** Match transaction descriptions against platform names and associated payment entity names in the adult entertainment category. Record transaction count, total debit, total credit, and top five matched terms. Assess frequency and value relative to average monthly income to contextualise the signal within the full discretionary spend profile.
- **Config:** Enable for NBFC and HFC credit underwriting workflows. The category operates as part of the 10-category risk word scan and is presented alongside gambling, alcohol, luxury, and BNPL signals in the discretionary spend section of the credit report.
- **Output:** Adult entertainment risk section in the credit report showing transaction count, total debit, total credit, and top five matched terms, flagged for human review when activity exceeds the lender-defined threshold.

### Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS

Source: https://www.terra-insight.com/insights/advance-tax-reconciliation-india/

- **Problem:** Advance tax follows a 15%, 45%, 75%, 100% cumulative schedule across 15 June, 15 September, 15 December, and 15 March. Shortfalls trigger Section 234C interest at 1% per month; Challan 280 paid under the wrong PAN or wrong AY lands in the wrong Form 26AS and compounds Section 234B interest.
- **Logic:** Match each Challan 280 payment to its CIN (BSR code + date + serial) in Form 26AS Part F after a 3–7 day lag. Validate cumulative payment against the scheduled 15/45/75/100 percentages, and reconcile any shortfall before the next instalment to stop Section 234C interest growing. Catch wrong PAN or wrong AY entries in the same cycle and raise a correction request.
- **Config:** CIN-keyed matching to Form 26AS Part F, cumulative instalment schedule, Section 234B/234C interest calculator, and challan-correction workflow for wrong PAN/AY entries.
- **Output:** Fully credited advance tax in Form 26AS, zero avoidable 234B/234C interest, clean Challan 280 audit trail, and reconciled tax expense in the ledger for the ITR filing.

### Advertising TDS: Why Creative Services Fall Under 194J, Not 194H

Source: https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india/

- **Problem:** Advertising creative and production services are classified under Section 194J at 10%, not Section 194H at 2% commission. Only pure media-buying commission remains under 194H. Incorrect 194H deduction on creative invoices triggers shortfall interest and disallowance risk.
- **Logic:** Split agency invoices into creative/production lines and separately stated commission lines with different SAC codes. Apply 194J at 10% on the creative and production component; apply 194H at 2% only on a separately stated commission line. Update vendor master to tag the agency under 194J, removing any legacy 194H default.
- **Config:** Invoice line classification by SAC code. Vendor-master default 194J for advertising agencies. 194H reserved for separately stated commission lines only.
- **Output:** Invoice-level correct deduction, Form 26AS or Form 168 matching on expected rates, and corrected agency ledger with any remaining 194H rows flagged for commission-only entries.

### Aerated and Sweetened Beverage GST and Cess Reconciliation (40% NSAB slab)

Source: https://www.terra-insight.com/insights/aerated-sweetened-beverage-gst-cess-40-percent/

- **Problem:** Aerated and sweetened beverage bottlers running franchise volume for global cola brands must reconcile a 22 September 2025 GST rate transition that moved HSN 2202 lines from 28% GST plus 12% compensation cess to a consolidated 40% NSAB slab. Pre-transition stock cleared before 22 September carries the old rate on its originating invoice, sits in distributor and retail channels for weeks after the transition, and returns via Section 34 credit notes at the old rate. Post-transition dispatches at 40% NSAB and their scheme reimbursements settle at the new rate. The reconciliation must resolve which rate governs each invoice, credit note, and scheme cycle, split the GSTR-1 HSN table by sub-heading and rate-effective-date with a compensation cess column, and align to the tax GL by month without under- or over-declaring cess on straddle transactions.
- **Logic:** Build a per-invoice register keyed by dispatch date, HSN sub-heading (2202 10 / 2202 91 / 2202 99), warehouse, distributor GSTIN, SKU, MRP, and rate at time of supply. Classify each invoice as pre-22-September or post-22-September. Maintain a scheme master with published rate and effective-date range; when a scheme cycle straddles the transition, hold both the pre-transition and post-transition treatment lines separately. Match each credit note to its originating invoice by number and enforce that the credit-note rate equals the invoice rate. Generate GSTR-1 Table 12 with two rows per HSN sub-heading during the transition FY — a pre-transition row and a post-transition row — with taxable value, GST amount, and compensation cess amount populated per rate. Cross-foot to the tax GL by HSN sub-heading and by month, and to the trade-spend GL for scheme reimbursements by rate cohort.
- **Config:** Rate master with HSN sub-heading (2202 10 / 2202 91 / 2202 99), pre-transition GST rate (28%), pre-transition compensation cess rate (12%), post-transition NSAB rate (40%), post-transition cess rate (0%), and effective-date fields (before 22 September 2025 / on or after 22 September 2025); scheme master with rate, geography, category, effective-date range, and Section 15(2) treatment flag; per-warehouse dispatch register with clearance timestamp; distributor master with GSTIN, PAN, claim-portal ID; PLISFPI base-year (FY 2019-20) SKU register at the underlying rate; credit-note linkage table pointing to originating invoices; GSTR-1 amendment table structure by rate cohort; MRP register per SKU per pack size per rate cohort for the September 2025 straddle.
- **Output:** A month-end GST reconciliation pack: GSTR-1 Table 12 populated by HSN sub-heading with pre-transition and post-transition rows, compensation cess correctly declared on pre-transition volume, credit notes tagged to their originating invoice's rate, and the trade-spend GL cross-footed by scheme cohort. A straddle exposure report — pre-22-September stock still held at distributor/retail and unsold as of month-end, with the exposure to further credit-note flow at the old rate. A Section 34 30-November deadline dashboard by rate cohort, flagging claims where the credit-note window is nearing expiry. A PLISFPI incremental-sales report holding parallel base-year and claim-year lines at underlying rate for audit trail integrity.

### Aftermarket Spares Distribution Reconciliation for Indian Auto-Component Manufacturers

Source: https://www.terra-insight.com/insights/aftermarket-spares-distribution-reconciliation-auto-india/

- **Problem:** The aftermarket spares channel runs on a different commercial logic from OEM-fitment supply: MRP-driven pricing, longer payment terms upstream, shorter terms downstream, two-tier distribution through 200-500 distributors, e-commerce platform sales under Section 9(5)/Section 52 GST, warranty pass-through from consumer to distributor to manufacturer, and a much slower-moving inventory profile. Tier-1 manufacturers that try to run aftermarket on the same ledger discipline as OEM-fitment break reconciliation: channel discounts get netted incorrectly, e-commerce TCS credits go unclaimed, warranty Section 34 credit notes miss the 30 November cutoff, and slow-moving stock provisions drift below NRV.
- **Logic:** Run aftermarket as a separately segmented revenue stream. Maintain MSL inventory ledger with FIFO costing and age buckets; per-distributor sub-ledger with credit terms, channel-discount accrual and reverse-logistics queue; e-commerce platform ledger with TCS-credit reconciliation against GSTR-2X; warranty pass-through workflow with Section 34 credit-note window watch; age-based slow-moving inventory provision. Inter-state stock transfer (MSL to MSL, or MSL to distributor across state) under GST Schedule I requires tax invoice with full GST charged and ITC available at receiving end.
- **Config:** Aftermarket-segment chart of accounts; MSL master with location, GSTIN, opening inventory; distributor master with credit terms, channel-discount percentage and warranty claim history; e-commerce platform master with TCS rate and reconciliation period; warranty pass-through workflow with Section 34 cutoff calendar; slow-moving inventory ageing report with provision policy; inter-state stock transfer routine with e-way bill generation.
- **Output:** A separately segmented aftermarket P&L with channel margin analysis per distributor, e-commerce TCS credit reconciliation, warranty pass-through liability with Section 34 cutoff watch, slow-moving inventory provision aligned to NRV under Ind AS 2, and segment reporting that satisfies Ind AS 108 where aftermarket exceeds 10 percent of group revenue.

### Agro Processing Reconciliation India: Nine Sub-Verticals Master Cornerstone

Source: https://www.terra-insight.com/insights/agro-processing-reconciliation-india-nine-sub-verticals-master/

- **Problem:** An agro processing group operating across two or more of the nine sub-verticals — for example, a dairy plus edible-oil plus fertilizer trading group, or a rice plus sugar plus contract poultry group — cannot run a single reconciliation preset because each sub-vertical has its own statutory pricing overlay (Fat + SNF for dairy, FCR for poultry, FRP for sugarcane, NBS or Cost-Plus for fertilizer), its own subsidy or claim mechanic (PLISFPI for dairy processing, MPEDA RCMC for aquaculture, DBT for fertilizer, RoDTEP for rice exports), and its own GST rate architecture (5 percent output on dairy versus 0 percent output on seeds versus Chapter 15 block on edible oil). Manual reconciliation across the group loses cross-vertical visibility of ITC, mis-attributes shared overhead to blocked-refund streams, and typically files Section 54(3) applications with formula errors under the Rule 89(5) amended computation — leaving substantial refund entitlements unclaimed on the non-blocked streams and refund rejections on the blocked ones.
- **Logic:** Build a per-sub-vertical reconciliation preset that maps procurement contract, statutory pricing overlay, TDS payment code, and GST rate architecture to the movement documents and settlement counterparty for each. Ingest procurement and settlement data at the granularity each sub-vertical demands — Fat kg and SNF kg for dairy, live-bird weighments and FCR for poultry, RCMC-certified shipping bill and EIC lab test for aquaculture, cane weighment and FRP calendar for sugar, auction settlement note for tea and coffee, custom-milling recovery ratio for rice, e-Urvarak PoS logs for fertilizer, CIB and RC filings for agrochemicals, trait-fee remittance for seeds. Cross-foot per-vertical ITC against per-vertical output turnover under the Rule 89(5) amended formula, gate refundable ITC against the Chapter 15 block for edible oil, and produce the Section 54(3) draft only for streams with a computable refund entitlement post 22 September 2025.
- **Config:** Nine sub-vertical presets, each carrying: procurement contract template (cooperative pooling / contract farming / auction / DBT retailer network / trait-fee remittance); TDS payment code map (Sl. 4 code 1023 for job-work with material supplied, 1024 without; Sl. 8 code 1031 for Section 194Q high-value purchase; Sl. 15 code 1005 for Section 194J professional; Sl. 18 code 1015 for Section 194H commission); statutory pricing overlay (Fat + SNF rate card, FCR schedule, FRP calendar, NBS Rs per kg nutrient, Urea Cost-Plus MRP Rs 242 per 45-kg bag); subsidy or claim clock (PLISFPI incremental sales test, MPEDA RCMC validity, e-Urvarak weekly claim cycle, RoDTEP Appendix 4R rate); output GST rate and refund posture (Chapter 15 blocked under Notification 09/2022; seeds 0 percent output with no offset; zero-rated exports refundable under Section 54(3) clause (a)); Rule 89(5) amended formula flag effective 5 July 2022; 56th GST Council rate table effective 22 September 2025 with FAQ Q10/Q25/Q51 flags for expedited refund processing on inversion-deepened streams.
- **Output:** Per-sub-vertical month-end reconciliation packs feeding a group-level control tower. Dairy pack: Fat + SNF procurement register, cooperative settlement reconciliation, cold-chain movement audit, PLISFPI eligibility log. Poultry pack: Section 143 free-issue register, contract-farmer FCR reconciliation, mortality and medication adjustments. Aquaculture pack: MPEDA RCMC shipment register, EIC lab test log, Section 54(3) zero-rated refund draft. Sugar pack: cane weighment register, 14-day FRP payment log, arrears-interest exposure at 15 percent per annum. Tea and coffee pack: auction settlement reconciliation, HSN 0902 versus 2101 inversion posture. Rice pack: FCI Custom Milling recovery reconciliation, DGFT MEP compliance log, RoDTEP Appendix 4R claim draft. Fertilizer pack: e-Urvarak PoS log, weekly subsidy claim reconciliation, Urea Cost-Plus audit trail. Agrochemicals pack: CIB and RC filing register, contract manufacturing TDS payment code 1023 reconciliation. Seeds pack: trait-fee remittance register, 0 percent output GST posture with no ITC offset. Group control tower cross-foots ITC across all nine and gates Section 54(3) refund draft against the Chapter 15 block and the 22 September 2025 rate table.

### Agrochemical Manufacturer CIB&RC Registration + GST Reconciliation India

Source: https://www.terra-insight.com/insights/agrochemical-manufacturer-cibrc-registration-reconciliation-india/

- **Problem:** An Indian agrochemical manufacturer running a portfolio of 350 active ingredient formulations at Rs 12,000 crore India turnover must reconcile the CIB&RC registration validity register across three registration classes (Section 9(3) full data, 9(3B) provisional, 9(4) me-too), the Ind AS 38 intangible asset amortisation schedule for each capitalised AI registration cost, Section 194Q code 1031 on aggregate AI purchase above Rs 50 lakh per resident supplier, Section 194H code 1015 on kharif and rabi distributor commission, Section 195 with Form 15CA and 15CB on imported technical remittance to the foreign parent, Section 15(2) CGST post-supply trade discount treatment on seasonal distributor incentives, and Section 43B(h) 45-day MSME payment aging on small formulator and packaging suppliers. Manual reconciliation across the registration, tax, and channel layers loses AI-wise validity expiry dates, mis-classifies distributor incentive between 194H commission and 15(2) trade discount, over-states input tax credit on imported technicals where the Section 195 remittance record does not tie back to the customs bill of entry, and triggers a Section 43B(h) add-back at year-end that leaves the P&L with a material tax hit that could have been avoided by a controlled 45-day payment cycle.
- **Logic:** Build an AI-wise registration register keyed to CIB&RC certificate number, Section 9 class (9(3) / 9(3B) / 9(4)), grant date, validity expiry, and the renewal filing window (typically 6 months before expiry). Capitalise the registration cost as an Ind AS 38 intangible asset by component (statutory fee, bio-efficacy trial cost, toxicity study cost, residue data cost, chemistry data cost, product-development cost), assign a useful-life estimate per AI (Section 9(3) new molecule 10-15 years; Section 9(4) me-too 5-8 years), and generate a monthly amortisation schedule that flows into the intangible asset schedule of the balance sheet and the amortisation line of the P&L. Extract every AI purchase invoice with supplier PAN and cumulate to the running annual aggregate; trigger Section 194Q code 1031 at 0.1 percent on the invoice value crossing the Rs 50 lakh threshold per supplier, and cross-reference with Section 206AB non-filer flag for the higher rate. Extract every distributor incentive accrual, classify between Section 194H commission (code 1015 at 5 percent TDS) and Section 15(2) post-supply trade discount (credit note with pre-agreement, invoice linkage, and recipient ITC reversal), and split the payout process accordingly. Extract imported technical purchase from customs bill of entry, generate Form 15CA and 15CB workflow for the Section 195 remittance to the foreign parent, and reconcile the CIF value against GSTR-2B IGST payable on import. Flag every supplier with an Udyam Registration Number as MSE, compute the payables aging from acceptance date, alert on approaching 45-day breach, and prepare the Section 43B(h) add-back schedule at year-end close for balances beyond the window.
- **Config:** AI master with active ingredient name, IUPAC identity, CIB&RC certificate number, Section 9 class, grant date, validity expiry, renewal window flag, and manufacturing site code; state licensing master with State Department of Agriculture licence number per state where the AI is marketed; intangible asset register with capitalised cost by component, useful-life estimate, and amortisation schedule; supplier master with PAN, GSTIN, Section 206AB non-filer flag (refreshed quarterly), Udyam Registration Number, MSE classification (micro / small / medium), and written-agreement flag; distributor master with distributor code, PAN, GSTIN, kharif/rabi target slab schedule, incentive classification default (194H commission versus 15(2) trade discount); customs master with bill of entry reference, imported AI CIF value, foreign parent supplier PAN of the parent Indian subsidiary or non-resident PAN if applicable; GSTR-1 and GSTR-2B feed for input credit and output supply reconciliation; Form 15CA and 15CB submission log for Section 195 remittance.
- **Output:** A month-end and year-end agrochemical reconciliation pack: AI-wise registration validity dashboard with expiring-within-6-months alert, intangible asset amortisation schedule with per-AI capitalised cost and monthly amortisation charge, Section 194Q code 1031 running aggregate by supplier with threshold-crossing invoice flag and Section 206AB overlay, Section 194H code 1015 distributor commission remittance schedule with kharif and rabi season split, Section 15(2) trade discount credit note register with pre-agreement and ITC reversal audit trail, Section 195 foreign remittance log with Form 15CA and 15CB submission reference, GSTR-2B IGST-on-import reconciliation against customs bill of entry, Section 43B(h) MSME aging report with 45-day breach schedule and year-end add-back working, and the CIB&RC renewal filing tracker for AIs entering the 6-month pre-expiry window.

### AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR

Source: https://www.terra-insight.com/insights/ais-tis-reconciliation-india/

- **Problem:** The Annual Information Statement replaced Form 26AS as the primary reconciliation reference for Section 143(1) processing in November 2021. AIS aggregates 46 categories — SFT reports, dividends, mutual fund redemptions, foreign remittances, GST turnover — far beyond 26AS. ITRs that conflict with AIS trigger automatic Section 143(1)(a) intimations even when the ITR figures are correct.
- **Logic:** Reconcile AIS against the books first, then cross-check 26AS TDS entries against AIS Part B. For AIS entries that disagree with the books, submit Feedback (Income is not mine, already included, partially correct, or duplicate) through the e-filing portal. Wait 15 days for source response and file ITR using TIS processed values rather than raw AIS values.
- **Config:** Category-wise AIS import with 46 buckets. Feedback submission workflow with response ageing. Cross-check routine matching 26AS TDS entries to AIS Part B.
- **Output:** ITR filed against TIS processed values, documented feedback trail for any disputed AIS entry, and no Section 143(1)(a) intimations for categories the taxpayer can defend with the books and feedback log.

### Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O

Source: https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india/

- **Problem:** Fashion brands selling on Ajio and Myntra operate across four parallel fulfilment models — Ajio Own Inventory, Ajio Sell On, Myntra Flex, Myntra FBF — each with a different commission tier, fulfilment fee structure, return treatment, Section 52 TCS posture, and Section 194O TDS applicability, and consolidating them into a single receivable line hides 25–40% return-rate leakage and model-level margin drift.
- **Logic:** Separate orders by fulfilment model before matching. Apply commission tier per model (Ajio Sell On 12–25%, Myntra Flex 15–28%, Ajio Own Inventory wholesale 35–50% off MRP, Myntra FBF with FC storage). Net returns within the platform's return window (7–15 days) and reverse TCS Section 52 via the revised GSTR-8. Apply TDS 194O at 1% on gross sale value past the ₹5 lakh annual threshold for individuals (first rupee for entities).
- **Config:** Fulfilment-model classifier per order, commission-tier master per platform per category per brand tier, fulfilment fee schedule (platform-ship vs vendor-ship vs FBF), return-window rules (7–15 days), TDS 194O threshold tracker per seller PAN, and TCS Section 52 reversal logic tied to return confirmation.
- **Output:** A reconciled seller receivable per fulfilment model, per-SKU net realisation across Ajio and Myntra, clean TDS 194O and TCS Section 52 posture in GSTR-3B and Form 26AS, and receivable aging that correctly distinguishes B2C settlement from B2B wholesale trade receivables.

### Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders

Source: https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements/

- **Problem:** High alcohol spending relative to income in a bank statement indicates a discretionary expense allocation that may reduce effective repayment capacity, particularly when combined with other high-discretionary categories such as gambling, luxury, or entertainment spending.
- **Logic:** Match every transaction description against 100+ alcohol brand names, state beverage corporation outlet names, bar and restaurant names, and home delivery platform references where alcohol is a primary category. Record transaction count, total debit, total credit, and top five matched terms. Compute alcohol debits as a share of average monthly income.
- **Config:** Enable for NBFC and HFC credit underwriting. Include state corporation names for accurate South and West India coverage. Set income-share threshold based on lender policy. Review alongside luxury and gambling signals for full discretionary spend picture.
- **Output:** Alcohol risk section in the credit report showing transaction count, total debit, total credit, and top five matched terms. Flagged if alcohol debits exceed the lender-defined income-share threshold.

### Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts

Source: https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation/

- **Problem:** Amazon Pay has two distinct settlement modes: marketplace sellers face weekly payouts net of referral fee, FBA fulfilment, returns, and 1% Section 52 TCS, while external-website merchants receive T+2 payment-gateway payouts with only MDR and 18% GST on MDR. Mixing the two causes misposted TCS credits and GSTR-8 versus GSTR-2B mismatches.
- **Logic:** Mode classification routes every Amazon credit to the correct pipeline. Marketplace reconciliation joins Amazon MTR settlement report against bank credit and matches TCS line items against GSTR-8 plus GSTR-2B Part II plus Form 26AS Part F. External-merchant Amazon Pay reconciliation runs the standard payment-gateway pattern on settlement_id plus UTR plus net amount.
- **Config:** Pipeline router on merchant type, TCS matcher keyed on GSTIN plus tax period plus order ID, referral-fee category rate table, and FBA fulfilment-fee decomposer.
- **Output:** Marketplace sellers get a reconciled TCS credit aligned to GSTR-2B, disaggregated revenue per order net of referral and FBA fees, return-adjustment trail. External merchants get order-level revenue and MDR ITC claim.

### Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1

Source: https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india/

- **Problem:** SPN consultants and Amazon sellers running hybrid Easy Ship plus FBA operations across 5–10 state-level GSTINs must file GSTR-1 per GSTIN mapping each invoice to the correct Table (4A, 5A, 7A, 7B) and place-of-supply, reconcile returns straddling two GSTR-1 periods, and track Section 52 TCS reversals across Amazon's revised GSTR-8 filings — all from the MTR template.
- **Logic:** Ingest Amazon MTR monthly per GSTIN. Classify each invoice by B2B/B2C and intra-state vs inter-state for GSTR-1 table mapping. For Easy Ship, credit notes reverse output tax in the issue period (GSTR-1 Table 9B). For FBA, credit notes align to Amazon's return confirmation period — not the original sale period. Claim TCS Section 52 in GSTR-3B against GSTR-2B entries from Amazon's operator GSTIN and reverse any TCS that Amazon subsequently reverses via revised GSTR-8.
- **Config:** Amazon MTR connector, multi-GSTIN registry per FBA fulfilment state, place-of-supply logic per IGST Act Section 10, GSTR-1 table router (4A / 5A / 7A / 7B / 9B), return-period tracker for Easy Ship vs FBA, and TCS Section 52 reversal reconciliation against operator GSTR-8.
- **Output:** A filing-ready GSTR-1 per GSTIN with every invoice in the correct table, clean GSTR-3B output tax plus TCS Section 52 credit adjustment, return timing aligned to credit-note period rules, and an audit trail linking every MTR line to its GSTR-1 entry and GSTR-2B TCS credit.

### American Express MDR: 3% Across Indian Gateways

Source: https://www.terra-insight.com/insights/american-express-mdr-3-percent-across-gateways-india/

- **Problem:** American Express is billed at the 2.95% to 3.5% premium slab across every Indian payment gateway studied — Razorpay 3%, PayU 3%, Cashfree 2.95% domestic, PhonePe through its premium-tier custom quote — while Visa and Mastercard consumer credit run closer to 2% and UPI bank account runs 0%. Where Amex is absorbed into a flat blended quote rather than appearing as a separate settlement line, the gateway under-recovers on the premium tail at the contracted moment and then reclaims the differential later through retrospective reclassification adjustments, notice-period rate-revision letters, or opaque renewal true-ups. The merchant sees the recovery as an unexplained settlement adjustment or a sudden rate change at a moment the CFO has not budgeted for it, and the per-transaction evidence required to dispute it is already settled and aged out.
- **Logic:** Per-network effective-rate reconciliation isolates American Express as a dedicated bucket in the settlement-file audit. Transactions are grouped by network using the BIN prefix (Amex BINs start with 34 or 37) and split by issuer country to separate Amex-India volume from Amex-issued-abroad volume. For each bucket the audit sums gross transacted value and total fee deducted, computes fee divided by volume as the effective rate in percentage terms, and compares the effective rate against the contracted slab in the rate card. A NETWORK_EFFECTIVE_RATE_GAP variance is raised whenever the Amex effective rate falls more than 10 basis points below the contracted premium slab (under-recovery flag, gateway claw-back exposure) or exceeds the contracted slab by more than 10 basis points (over-charge flag, dispute candidate).
- **Config:** Amex BIN range identifier (BINs beginning with 34 or 37); issuer-country lookup against the BIN table to split Amex-India and Amex-issued-abroad; per-network rate-card rule keyed on contracted domestic Amex slab and contracted international Amex slab; blended-quote rule recording the headline blended rate the merchant believes is in force; NETWORK_EFFECTIVE_RATE_GAP variance class with 10-basis-point slab tolerance; GST-invoice matcher for the 18% line on the Amex fee; Cashfree promo-eligibility rule recording the 18 September 2025 to 30 April 2026 window and the 40% UPI-share covenant where applicable.
- **Output:** A per-cycle Amex effective-rate table with fee, volume, effective rate, contracted slab, variance in basis points, and recoverable or exposed amount; an issuer-country split table separating Amex-India volume at the domestic slab from Amex-issued-abroad volume at the international slab plus forex; a CFO dashboard showing Amex share of card GMV, blended-vs-effective spread, and rolling under-recovery exposure month-on-month; a dispute-pack export per gateway with per-transaction Amex evidence and expected-vs-actual fee calculation against the contracted rate card; a GST-invoice reconciliation schedule against the gateway's monthly tax-invoice line.

### Amex and Diners Hidden Inside a Blended MDR Rate: Detection Technique

Source: https://www.terra-insight.com/insights/amex-diners-hidden-in-blended-mdr-india/

- **Problem:** A single blended MDR quote — Razorpay 2%, PayU 2%, Cashfree 1.95%, PhonePe 1.95% — conceals the per-network spread between zero-MDR UPI, ~1.5% Visa/Mastercard credit, and 2.95-3.5% Amex and Diners. The merchant sees one deducted percentage on the settlement file and cannot tell whether Amex and Diners were separately and correctly priced. Either the merchant is cross-subsidising premium-network volume through low-cost UPI, or the gateway is under-recovering on the premium share and reclaiming silently in a later cycle via reclassification, a rate revision, or a renewal true-up.
- **Logic:** Per-network effective-rate reconciliation groups every settlement-file transaction by network (Visa debit, Mastercard debit, Visa credit, Mastercard credit, Amex, Diners, UPI bank account, RuPay debit, international), sums the fee deducted and the gross transacted value for each group, and computes fee divided by volume. The effective rate per group is then compared against the gateway's published per-network rate card and against the blended quote the merchant believes is in force. A NETWORK_EFFECTIVE_RATE_GAP variance is raised whenever the per-network effective rate exceeds the contracted blended rate plus a tolerance, with Amex and Diners isolated as a dedicated bucket for separate slab verification.
- **Config:** Per-network MDR rule set keyed on network (Visa, Mastercard, Amex, Diners, RuPay, UPI bank, international) and product tier (consumer, premium, commercial); blended-quote rule recording the contracted blended rate; NETWORK_EFFECTIVE_RATE_GAP variance class with 10-bps slab-delta tolerance; Amex and Diners flagged as a separate audit bucket regardless of share; GST-invoice matcher for the 18% line; refund-MDR retention flag and 90-day rolling recovery window.
- **Output:** A per-network effective-rate table per settlement cycle with fee, volume, effective rate, expected rate, variance basis points, and recoverable amount; a CFO-facing dashboard showing network mix, blended vs effective spread, and Amex/Diners isolated share month-on-month; a dispute-pack export per gateway with per-transaction Amex and Diners evidence and expected-vs-actual fee calculation; a GST-invoice reconciliation schedule against the gateway's tax-invoice line.

### Tentative Approval to Launch: When ANDA Revenue Actually Books

Source: https://www.terra-insight.com/insights/anda-milestone-payment-usfda-tentative-approval-revenue-timing/

- **Problem:** A Tier-1 India-listed generic exporter holding a tentative-approval ANDA for a Paragraph IV first-to-file molecule must reconcile three parallel timelines that agents and auditors regularly conflate. Timeline one is the USFDA regulatory timeline under Section 505(j) FDCA — ANDA acceptance, tentative approval, final approval on Orange Book patent expiry or Paragraph IV court resolution, and the 180-day exclusivity window under Section 505(j)(5)(B)(iv). Timeline two is the Ind AS 115 revenue timeline — no recognition at tentative approval, no recognition at final approval, recognition on shipment to the US wholesaler customer at transaction price net of variable consideration. Timeline three is the working-capital timeline — chargeback reserve build, Medicaid rebate reserve build, wholesaler management fee accrual, expected returns reserve, and the settlement cycle for each. A misalignment between these three timelines produces either premature revenue recognition (auditor flag), understated reserves (subsequent revenue reversal), or overstated launch-quarter revenue against a post-exclusivity price step-down.
- **Logic:** Build a Section 505(j) milestone register keyed to the molecule and its reference-listed drug, capturing ANDA acceptance date, tentative approval date, Orange Book patent expiry schedule, Paragraph IV certification status and any settlement or court decision date, projected final approval date, and projected 180-day exclusivity window start and end. Separately build an Ind AS 115 revenue register keyed to shipment purchase orders — shipment date, INCOTERM control-transfer point, invoice value at WAC, and the variable-consideration reserve estimate at shipment date decomposed by component (chargeback, Medicaid rebate, wholesaler management fee, returns). Build a two-regime pricing model — the exclusivity-window regime with sole-generic assumptions, and the post-exclusivity regime with competitive-entry step-down assumptions — and use the appropriate regime for the reserve estimate on each shipment. Reconcile the reserve estimates quarterly against actual chargeback invoices received, actual Medicaid rebate invoices received, actual wholesaler fee deductions and actual returns processed. Flow reserve-versus-actual gaps to the following-quarter true-up per Ind AS 115 paragraph 88 (change in estimate) rather than restating the prior period.
- **Config:** ANDA molecule master with reference-listed drug, therapeutic category, Orange Book patent listing, exclusivity code, Paragraph IV certification status, projected final approval window; USFDA milestone register per ANDA capturing acceptance date, tentative approval date, final approval date, exclusivity start/end; US wholesaler customer master with negotiated WAC, chargeback contract terms, wholesaler management fee percentage, returns policy; Medicaid rebate register with National Drug Code mapping, quarterly shipment volume feed to CMS, quarterly state rebate invoice reconciliation; two-regime price and volume model — exclusivity-window and post-exclusivity — with parameter overrides at reset events (competitive entry, price-list revision); Ind AS 115 variable-consideration reserve register per shipment with decomposition by component; quarterly reserve-versus-actual reconciliation with true-up entries flagged to the following-quarter close; FCA-INCOTERM (or FOB or CIF as applicable) mapping to control transfer date; forex translation register under Ind AS 21 (invoice-date spot rate, quarter-end closing rate, realisation-date rate) for the USD invoice conversion to INR reporting currency; e-BRC integration for the Indian shipping bill and bank realisation certificate reconciliation feeding the [DGFT export incentive claim](/insights/pharma-export-drawback-rodtep-reconciliation-formulations/).
- **Output:** A quarterly ANDA milestone-to-revenue pack that maps every regulatory event in the Section 505(j) timeline to its Ind AS 115 accounting consequence (or lack thereof), a shipment-by-shipment transaction-price register with the variable-consideration reserve estimate at shipment date and the actual experience against each reserve line, a two-regime pricing model that separates sole-generic exclusivity-window arithmetic from post-exclusivity competitive-entry arithmetic, a reserve movement schedule showing opening reserve, current-quarter accrual, actual invoices received and payments settled, closing reserve and the true-up entry flowing to the following quarter, a forex translation reconciliation converting the USD invoice to INR at the correct rates per Ind AS 21, and a treasury projection mapping expected chargeback settlement, Medicaid rebate settlement and wholesaler fee settlement to the working-capital cycle.

### ANDA and US Generic Revenue: Milestone-Based Ind AS 115 Reconciliation

Source: https://www.terra-insight.com/insights/anda-us-generic-export-revenue-recognition-milestone-reconciliation/

- **Problem:** An Indian pharma US-generic exporter running an ANDA pipeline of approximately 185 approved plus 145 pending applications must reconcile a five-stage milestone lifecycle — Paragraph IV Certification filing under Section 505(j)(2)(A)(vii), notice-of-suit and 30-month litigation stay, tentative approval, final approval, and 180-day first-to-file exclusivity under Section 505(j)(5)(B)(iv) — against Ind AS 115 revenue recognition. Development-phase milestones are variable consideration constrained under Ind AS 115 paragraphs 56 to 58 until the milestone is highly probable; typical practice is no revenue recognition until final approval. The 180-day exclusivity is a revenue-density event recognised at point of sale for each shipment (not front-loaded on Day 1) with gross-to-net variable-consideration estimation for chargebacks, Medicaid rebates, Medicare Part D coverage-gap discounts, commercial rebates, wholesaler stocking allowances, and returns. Post-launch commercial supply is standard Ind AS 115 point-of-sale recognition at transaction price. Cross-linkages: India-US DTAA Article 7 business-income treatment for no-PE direct-to-wholesaler sales; Section 54(3)(i) IGST export refund on accumulated ITC via GST RFD-01; Ind AS 21 forex translation on USD-denominated receivables and milestone rights at each reporting date; Ind AS 21 realisation on the AD Category-I bank credit against FIRC / BRC. Missing any hop breaks the quarterly earnings walk and exposes a Section 271 addition or a statutory audit qualification on the exclusivity-window release.
- **Logic:** Build an ANDA-wise pipeline register keyed to the reference listed drug (RLD) with the ANDA number, submission date, patent certification category (I, II, III, or IV), notice-of-suit date, 30-month stay expiry date, tentative approval date, final approval date, first-commercial-marketing date, 180-day exclusivity start date, and 180-day exclusivity end date. For each ANDA milestone that carries a contingent milestone-fee entitlement under a US-side licensing or profit-share arrangement, apply the Ind AS 115 paragraph 56-58 constraint test — is the milestone highly probable such that a significant reversal in cumulative revenue would not occur? If yes, include the milestone amount in transaction price; if no, constrain (do not recognise). On achievement of a previously-constrained milestone, release the constrained amount to the profit and loss of the period of achievement. For direct-to-wholesaler generic sales (the applicant is the ANDA-holder), recognise revenue at each shipment invoiced to the US wholesaler at the transaction price, with gross-to-net variable-consideration reduction for the standard US-generic gross-to-net stack (Medicare Part D coverage-gap discount, Medicaid rebates, Federal Supply Schedule pricing, commercial payer rebates, chargebacks, wholesaler stocking allowances, returns provision). Translate USD-denominated receivables to INR at each reporting date under Ind AS 21 at the closing spot rate; recognise forex gain or loss on translation and on realisation. Reconcile the GST RFD-01 export refund pack quarterly against the DGFT shipping-bill register, the FIRC / BRC realisation register, and Rule 89(4) formula-driven ITC refund. On the India-side tax return, treat the US-generic business income as Article 7 DTAA business profits taxable in India only for the no-PE case; apply Section 195 only to the reverse leg (payments the Indian applicant makes to US non-resident service providers such as patent counsel or CGMP remediation consultants) at India-USA DTAA Article 12 or Article 15 rates.
- **Config:** ANDA pipeline master keyed to ANDA number with reference listed drug (RLD) name, active pharmaceutical ingredient, dosage form, strength, indication, patent certification category, notice-of-suit date, 30-month stay expiry, tentative approval date, final approval date, first-commercial-marketing date, 180-day exclusivity window; US-side commercial arrangement flag (direct-to-wholesaler / licensed-out / profit-share / royalty); Ind AS 115 revenue-recognition method flag (point-in-time at shipment / over-time by input method / milestone-based); gross-to-net reduction stack template (Medicare Part D coverage-gap discount, Medicaid rebates, chargebacks, commercial rebates, wholesaler stocking allowances, returns provision) with historical percentages by product and by channel; ERP customer master with US-wholesaler and US-distributor identifiers (McKesson, Cardinal Health, AmerisourceBergen, Morris Dickson, HD Smith); AD Category-I bank realisation register with FIRC / BRC reference; DGFT shipping-bill register keyed by BE number and shipping-bill number; Rule 89(4) CGST Rules formula inputs for the quarterly RFD-01 refund pack; GST portal filing calendar for GSTR-1 (invoice-level export sales), GSTR-3B (aggregate zero-rated turnover), and RFD-01 (quarterly refund); Ind AS 21 reporting-date closing spot rate feed from RBI reference rate or the bank pool rate; Section 195 withholding register for reverse-leg payments to US non-resident service providers with India-USA DTAA Article 12 / 15 rate lookup; Ind AS 20 flag for any US-side federal or state grant income (unusual — but a University-sponsored research collaboration or an FDA orphan-drug voucher sale would carry an Ind AS 20 recognition question); Section 92CA transfer-pricing register for any US subsidiary intra-group transfer where the ANDA-holder in India transfers to a US-marketing-arm subsidiary at a distributor margin.
- **Output:** A quarterly ANDA revenue pack: the pipeline register with milestone-status column and revenue-recognition-status column for each ANDA (constrained / released this quarter / recognised at point of sale for commercial supply); the milestone-release schedule showing previously-constrained variable consideration released this quarter with the Ind AS 115 paragraph 56-58 justification memo; the exclusivity-window revenue register for any ANDA in its 180-day exclusivity showing shipment-by-shipment recognition with gross-to-net reduction to net revenue; the commercial-supply revenue register for post-exclusivity ANDA-covered products with the standard Ind AS 115 point-of-sale recognition; the Ind AS 21 forex translation walk showing USD-denominated receivables translated at reporting-date closing spot rate with the exchange difference to profit and loss; the AD Category-I bank realisation reconciliation showing FIRC / BRC-matched inflows against invoiced amounts; the GST RFD-01 quarterly export-refund pack with the Rule 89(4) formula-driven ITC refund and the DGFT shipping-bill and FIRC / BRC cross-references; the Section 195 reverse-leg withholding register for US-side service provider payments; the India-side tax provisioning schedule showing US-generic business income taxed in India only under India-USA DTAA Article 7 for the no-PE direct-sale case; and the statutory-audit-ready walk from ANDA pipeline milestone event to Ind AS 115 recognition to Ind AS 21 translation to bank realisation, with the audit trail from FDA milestone announcement press release or FDA Orange Book listing to internal accounting entry.

### APEDA Export Incentive Reconciliation for Indian Food Processing

Source: https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india/

- **Problem:** Food product exporters in India operate under multiple APEDA-administered export schemes (TMA, Market Development Assistance, Quality and Infrastructure Development) plus the cross-cutting RoDTEP electronic scrip mechanism that replaced MEIS in 2021, with reconciliation against FIRC, shipping bills, IGST refund on zero-rated supplies under Section 16 IGST Act, LUT or EDLI bond tracking, and Section 393(2) Sl. 17 code 1057 TDS on foreign-agent commission — each scheme with separate claim cycles.
- **Logic:** Tag every shipping bill to its eligible scheme(s) at lodgement; reconcile RoDTEP scrip issuance against shipping bill value and rate notification; tie each export to its FIRC realisation within the 9-month RBI window; operate under LUT for IGST-free zero-rated supply and reconcile input ITC refund under Section 54 CGST Act; deduct Section 393(2) Sl. 17 code 1057 TDS on foreign-agent commission with Form 15CA/15CB.
- **Config:** Export configuration with APEDA scheme tags per shipping bill, RoDTEP rate notification by HSN, FIRC ingestion against shipping bill register, LUT registration tracker, IGST refund file builder, Section 393(2) vendor master for foreign agents with DTAA country tag, Form 15CA/15CB workflow.
- **Output:** A monthly export close where APEDA scheme claims tie to shipping bill register, RoDTEP scrips reconcile against eligible export value, FIRC realisation is matched within the RBI 9-month window, accumulated input ITC refund file builds against zero-rated supply under LUT, and Section 393(2) challans tie to each foreign-agent commission remittance.

### APEDA Exports, RCMC and EIC Lab-Test Recovery Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/apeda-exports-rcmc-fmcg-reconciliation/

- **Problem:** Indian FMCG dairy and processed-food exporters — GCMMF (Amul), Britannia, ITC Foods, Marico, Dabur, Adani Wilmar — ship scheduled products through the APEDA-notified channel where three parallel cost and evidence flows must be reconciled every period. APEDA RCMC is an annual fee booked as prepaid expense and amortised across eligible exports. EIC lab-test invoices are per-consignment and either recoverable from the importer via contract clause or absorbed as export overhead. FEMA-side FIRC realisation must match export invoice value within nine months. The three ledgers live in different systems (SAP FI for the fee amortisation, an EIC-facing invoice tracker for lab-test recovery, an AD-Bank statement feed for FIRC realisation) and rarely reconcile without controller intervention — leaving PLISFPI incremental-sales certification, transfer-pricing benchmarks, and the FEMA reportable position all exposed at year-end.
- **Logic:** Build a scheduled-HSN master with RCMC coverage flag per product line and per validity period. Amortise the annual RCMC fee over the certificate validity and allocate the period charge across eligible-export invoice lines by scheduled HSN and dispatch volume. Parse the EIC/EIA lab-test invoice register — each row referencing the shipping bill number, port, consignment value, and inspection fee — and match one-to-one with the export shipping bills carrying the corresponding certificate references. Classify each EIC line as recoverable (contract clause), CIF-loaded (buried in price), or absorbed (export overhead). Parse the FIRC feed from the AD Bank — invoice number reference, realised currency amount, INR credited, and realisation date — and match to the export invoice register on invoice number and dispatch date. Age unrealised invoices in FEMA-window buckets (0-90 / 91-180 / 181-270 days). Cross-foot the three ledgers to the export sales general ledger and the prepaid expense movement before month-end close.
- **Config:** Scheduled-HSN master with RCMC coverage flag, validity from-to, and RCMC certificate number; RCMC fee amortisation schedule with prepaid expense GL account and period-charge allocation rule; EIC/EIA invoice register with shipping bill reference, port, consignment value, and recovery classification (recoverable / CIF-loaded / absorbed); export shipping bill feed with EIC certificate reference and scheduled-HSN flag; export invoice register with customer, currency, invoice value, dispatch date, and PLISFPI-eligibility flag; FIRC feed from the authorised dealer bank with invoice number, realised amount, INR credit, and realisation date; FEMA nine-month window ageing configuration (0-90 / 91-180 / 181-270 days); PLISFPI base year FY 2019-20 export sales reference for the incremental-sales calculation.
- **Output:** A month-end APEDA reconciliation pack: RCMC prepaid expense movement (opening, amortisation, closing), EIC invoice register with recovery status, export shipping bills with EIC and RCMC coverage confirmation, FIRC realisation register with matched and unmatched invoices, FEMA-window ageing on unrealised invoices, and the export sales cross-foot to the general ledger. Per-invoice FIRC ageing surfaces the overdue population for AD Bank extension requests or RBI reporting. The pack feeds three downstream registers — PLISFPI incremental-sales certification with base year FY 2019-20, transfer-pricing benchmark for the export cost base, and the year-end statutory audit disclosure on FEMA position.

### API CDMO Margin Reconciliation: Cost-Plus, Fixed-Price, Milestone

Source: https://www.terra-insight.com/insights/api-contract-manufacturing-margin-reconciliation-cdmo/

- **Problem:** A Tier-2 CRAMS operator running a diversified CDMO contract book — illustratively of the order of Rs 650 crore per year split roughly 40 percent cost-plus at an average 18 percent margin, roughly 35 percent fixed-price at an average 32 percent margin, and roughly 25 percent milestone at an average 28 percent margin — must apply Ind AS 115 revenue recognition differently to each of the three contract types (cost-plus over time via input method, fixed-price over time via cost-to-cost input method, milestone at point-in-time on customer acceptance), must flag every intra-group contract at inception under Section 92BA of the Income-tax Act 2025 for Rule 10D transfer-pricing documentation and Form 3CEB annual filing, must track Section 194Q payment code 1031 TDS credit per principal against Form 26AS, and must refresh the estimate-at-completion cost forecast on every fixed-price contract monthly to catch a completed-contract loss provision under Ind AS 37 before year-end audit.
- **Logic:** Build the contract master with contract type, intra-group flag, Section 92BA marker, principal-entity identification, contract-life value, and budgeted margin populated at inception. Feed the per-contract cost ledger and billing register into a per-contract revenue-recognition tracker that applies the Ind AS 115 method appropriate to each contract type — an input method for cost-plus with margin overlay, a cost-to-cost input method for fixed-price against the contract price, and a point-in-time trigger for each milestone against customer acceptance sign-off. Extract a per-contract-type margin variance table at monthly close with a root-cause flag. Compile a Section 194Q TDS credit register per principal reconciling the CDMO's invoice-level 194Q-expected calculation to the Form 26AS credit and the principal's Form 26Q return line. Refresh the estimate-at-completion cost forecast on every fixed-price contract monthly and raise a completed-contract loss provision alert under Ind AS 37 when the forecast crosses the fixed contract price. Compile the intra-group contract population into the Form 3CEB annual filing feed.
- **Config:** Contract master with per-contract type field (cost-plus, fixed-price, milestone), intra-group flag, Section 92BA marker, principal-entity identification (PAN and GSTIN), contract-life value, budgeted margin, and revenue-recognition method assignment; per-contract cost ledger and billing register with month-end refresh; Ind AS 115 method-specific revenue-recognition calculators (cost-plus input method with margin overlay, fixed-price cost-to-cost input method, milestone point-in-time trigger register keyed to customer acceptance sign-off); per-contract-type margin variance table with root-cause tagging library covering yield loss, solvent cost, FX movement, milestone timing; Section 194Q TDS credit register per principal reconciling invoice-level expected against Form 26AS and principal Form 26Q; estimate-at-completion cost-forecast refresh loop with completed-contract loss provision alert under Ind AS 37; Form 3CEB annual compilation feed from the intra-group contract population; Rule 10D documentation library link per contract.
- **Output:** A month-end CDMO margin reconciliation pack per plant per contract type: aggregate revenue recognition decomposed by Ind AS 115 method, per-contract-type margin variance table with root-cause flags, per-principal Section 194Q TDS credit reconciliation against Form 26AS, estimate-at-completion refresh with completed-contract loss provision alerts on any fixed-price contract whose forecast has crossed the contract price, and a Section 92BA intra-group contract register with the Rule 10D documentation link per contract. At year-end, the pack feeds the Form 3CEB filing for the intra-group contract population and reconciles the aggregate reported margin against the aggregate budgeted margin at contract inception, decomposed by contract type. The reconciliation surface serves as the audit reference for both the Ind AS 115 revenue-recognition disclosures in the annual report and the transfer-pricing scrutiny defence for the intra-group contracts.

### API vs Formulation: HSN 2941 / 3003 / 3004 Reconciliation Guide

Source: https://www.terra-insight.com/insights/api-vs-formulation-hsn-2941-3003-3004-reconciliation-guide/

- **Problem:** A backward-integrated Indian pharma group running an API manufacturing unit under HSN 2941 that dispatches bulk antibiotic (Amoxicillin trihydrate, Cefixime) to a sister formulation plant that converts the same molecule to HSN 3004 finished dosage form must reconcile the material-flow register across two GSTINs, an inter-unit invoice at arm's length under Section 92BA specified domestic transaction discipline with Rule 10D documentation, two separate Rule 89(5) inverted-duty refund cycles filed at each GSTIN with the Chapter-27 solvent exclusion applied only at the API side per Notification 09/2022-Central Tax (Rate), and Section 194Q buyer-side TDS on the cross-plant procurement where the two units are held under separate legal entities. Manual reconciliation loses per-batch HSN tagging on the material-flow register, mixes solvent ITC into the API unit's refund workbook, and under-documents the inter-unit transfer against the arm's-length benchmark — exposing the group to Section 74 GST penalty at either GSTIN and to a Section 92BA transfer-pricing adjustment at the assessment stage.
- **Logic:** Build a material-flow register keyed on the API batch number that carries the HSN tag from Chapter 29 (2941) at the API dispatch stage, through Chapter 30 (3003) at the formulation feedstock stage, to Chapter 30 (3004) at the finished-dosage-form dispatch stage. Reconcile the API dispatch invoice against the formulation plant's inward register on a two-way match keyed on batch number, quantity, and HSN tag, and route the differential through an inter-unit variance register. Extract the API unit's input ITC into three sub-pools — Chapter 27 solvent ITC (refund-blocked under Notification 09/2022), other Chapter 29 to 38 chemical ITC (refund-eligible under Rule 89(5)), and services and capital-goods ITC (excluded from Net ITC under the amended formula) — and file GST RFD-01 monthly on the refund-eligible base only. Extract the formulation plant's input ITC on the same three-pool basis (though Chapter 27 exposure at the formulation stage is typically lower — solvents are largely spent at the API stage). Compute Section 92BA arm's-length benchmark on Cost Plus or Comparable Uncontrolled Price basis and generate Form 3CEB certification base at year-end. Compute Section 194Q liability on cross-plant procurement only where the two units are separate legal entities.
- **Config:** API unit GSTIN master with plant address, HSN 2941 output SKU catalogue (Amoxicillin trihydrate, Cefixime, Azithromycin, Ciprofloxacin), Chapter 27 solvent input catalogue (hexane, isopropyl alcohol, methanol, toluene, ethyl acetate) tagged refund-blocked, other Chapter 29 to 38 input catalogue tagged refund-eligible; formulation plant GSTIN master with plant address, HSN 3003 feedstock catalogue, HSN 3004 finished dosage form catalogue by product code and pack size; inter-unit invoice header schema with batch number, HSN tag, IGST computation, arm's-length benchmark source, Form 3CEB tag; Section 92BA related-party flag on the group counterparty (Section 40A(2)(b) test); Section 194Q buyer flag on the formulation plant's cross-plant procurement register with the Rs 50 lakh threshold tracker per counterparty; monthly GST RFD-01 refund workbook per GSTIN with the amended Rule 89(5) formula pre-loaded and the Notification 09/2022 Chapter-27 exclusion pre-applied; material-flow register with three-stage HSN transition tracker (2941 to 3003 to 3004) per batch.
- **Output:** A month-end backward-integrated pharma reconciliation pack: material-flow register per batch with three-stage HSN transition (API 2941, feedstock 3003, finished 3004) reconciled, cross-plant dispatch to receipt two-way match with variance register, API unit GST RFD-01 refund workbook with Chapter-27 solvent ITC segregated and refund-eligible base cleanly derived, formulation plant GST RFD-01 refund workbook on the same basis, inter-unit invoice register at arm's length with Section 92BA compliance flag and Form 3CEB feed, Section 194Q liability computation on cross-plant procurement above Rs 50 lakh per counterparty where the two units are separate legal entities, and Section 206C(1H) TCS reconciliation where the seller-side is the covered person. At year-end the pack feeds the Form 3CEB Accountant's report for Rule 10D certification and the group's transfer-pricing documentation file.

### API Yield Loss and Solvent Recovery: Reconciling the Weight-Loss Gap

Source: https://www.terra-insight.com/insights/api-yield-loss-solvent-recovery-reconciliation-pharma-manufacturing/

- **Problem:** A Chapter 29 API custom-synthesis unit runs a 4-step organic synthesis on a starting material to produce a bulk API classified under HSN Chapter 29 (heading 2941 for antibiotics or another Chapter 29 heading for the broader spectrum of API molecules). The theoretical mole-balance yield from starting material through 4 reaction steps to the isolated product molecule is 72 percent illustratively; the actual isolated yield after crystallisation, mother-liquor loss, wash-cycle loss and filtration-and-drying loss is 65 percent — a 7 percentage-point yield gap that must be reconciled batch by batch. The synthesis consumes 12 tonne of hexane at HSN 2710 per batch as reaction solvent; the distillation column recovers 10.4 tonne (87 percent recovery) for re-use in the next batch cycle; the make-up solvent requirement is 1.6 tonne (13 percent of the hexane charge). The recovered hexane and the fresh hexane both sit at HSN 2710 with the Notification 09/2022-Central Tax (Rate) dated 13 July 2022 Chapter 27 refund block in force. Spent solvent and mother liquor sent to the Common Hazardous Waste Treatment, Storage and Disposal Facility under the Hazardous and Other Wastes Rules 2016 must be reconciled from the Form 3 batch manifest to the state pollution control board monthly return.
- **Logic:** Build a batch-level material balance workbook that reconciles input weight (starting material + reagents + fresh solvent + make-up solvent) against output weight (isolated API + recovered solvent + quantified spent solvent to waste manifest + quantified unrecovered loss). Compute the yield-loss variance as (actual yield percent minus standard yield percent) applied to the starting-material charge and translated to a rupee variance against the standard cost. Maintain a solvent recovery cycle register keyed to the solvent HSN (2710 hexane, 2905 isopropyl alcohol, 2914 methyl ethyl ketone) that reconciles fresh solvent purchase (from the vendor invoice register with GST at 18 percent), solvent recovered from the distillation column (from the plant DCS batch record), and make-up solvent required (arithmetic residual). Track the Chapter 27 solvent input ITC in the Net ITC pool as a distinct line — eligible ITC in the electronic credit ledger but subject to the Notification 09/2022 field-scrutiny carve-out at Rule 89(5) refund claim time. Reconcile the batch-level Form 3 waste-manifest entries (Category B10 spent solvent, Category B27 mother liquor) to the state pollution control board monthly return quantity.
- **Config:** Batch master with route ID, starting material grade, standard yield assumption per step and cumulative, standard solvent charge per solvent HSN, and standard recovery percent per solvent HSN; batch-record ingestion from the plant DCS or LIMS or manual batch card; material balance workbook per batch with input register and output register keyed to HSN chapter; yield-loss variance calculation module against the standard yield assumption; solvent recovery cycle register per solvent HSN with fresh purchase, recovered quantity and make-up requirement; hazardous waste manifest register with Category B10 spent solvent, Category B27 mother liquor, and other applicable categories per Hazardous and Other Wastes Rules 2016; state pollution control board monthly return builder (MPCB, GPCB, APPCB, TSPCB per plant location); ERP inventory movement reconciliation to the batch-record material balance; standard cost variance journal to post to the general ledger at tax-period close; tax-period Chapter 27 solvent ITC composition line in the Rule 89(5) refund workbook.
- **Output:** A month-end batch-level material balance pack: per-batch input-output reconciliation showing the yield-loss gap against standard, the solvent recovery cycle showing fresh purchase and recovered quantity and make-up requirement per solvent HSN, and the hazardous waste manifest showing spent solvent and mother liquor quantities disposed to the Common Hazardous Waste Treatment, Storage and Disposal Facility. A tax-period roll-up: aggregate yield-loss variance against standard translated to a rupee cost variance, aggregate Chapter 27 solvent make-up ITC feeding into the plant's Net ITC composition register, and the state pollution control board monthly return reconciled against the plant-level Form 3 manifest aggregate. A standing yield-improvement dashboard: batch-family yield trend, mother-liquor-loss trend, wash-cycle-efficiency trend, and the standard yield assumption re-baseline recommendation feeding the next-quarter standard cost update.

### APMC and Mandi Cess Reconciliation Across Indian States

Source: https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india/

- **Problem:** APMC mandi cess reconciliation requires handling state-specific market fee, mandi cess, rural development cess, auction fee and weighment charges that vary from approximately 1% (Maharashtra) to 6.5% (Punjab) — alongside Section 393(1) Sl. 6(i) TDS on labour and handling contractors and the GST exclusion of these state levies from the buyer's credit chain.
- **Logic:** Configure a state-by-state cess matrix at vendor-master setup; split every mandi invoice into commodity value, arhatiya commission, market fee, mandi cess, rural development cess, auction fee and weighment charge; treat all state cess as non-creditable cost-of-goods; deduct Section 393(1) Sl. 6(i) codes 1023 / 1024 TDS on labour and handling contractors; reconcile per-mandi receipt slip against the configured cess matrix.
- **Config:** Procurement configuration with state-cess matrix per APMC, vendor-master tag for mandi handling contractors with Section 393(1) Sl. 6(i) flag, mandi receipt slip ingestion, weighbridge slip cross-reference, GST-exempt classification on state cess lines, monthly cess-variance dashboard per state.
- **Output:** A monthly procurement close where each mandi invoice reconciles to its state cess matrix, mandi-handling contractor TDS rolls up under Section 393(1) Sl. 6(i) codes 1023 / 1024 challan, state-level procurement cost variances surface against configured rates, and the cess load per MT is reported as a non-GST-creditable cost-of-goods component for inventory valuation.

### APS-04 NACH Pre-Booking and Reconciliation for Indian Corporates

Source: https://www.terra-insight.com/insights/aps-aps04-prebooking-nach-india/

- **Problem:** A corporate running 22,000 monthly APS-04 NACH instructions for subscription billing reconciles only at settlement, missing the pre-booking stage entirely. Instructions that fail at pre-booking sit in limbo, customers are billed for services they did not pay for, and the operations team discovers the gap days later from customer complaints.
- **Logic:** Treat each APS-04 instruction as a state machine with three explicit states — pre-booked, presented, settled or returned — keyed on the instruction reference. Reconcile at every state transition: pre-booking confirmation against original request, presentment confirmation against pre-booking, and settlement or return against presentment. Timeouts on state transitions raise their own exceptions.
- **Config:** Instruction reference master, three-state reconciliation engine, NPCI return-code library at the presentment stage plus pre-booking rejection codes, timeout rules per state, and an exception MIS to the subscription billing team.
- **Output:** Same-day visibility of failures at every stage of the APS-04 cycle, a clean join between billing instructions and actual cash receipt, and a defensible audit trail showing every instruction's lifecycle from pre-booking to terminal state.

### ASN to GRN to Invoice: The Auto-Component Three-Way Match That Actually Works

Source: https://www.terra-insight.com/insights/asn-grn-invoice-three-way-match-auto-india/

- **Problem:** Tier-1 auto-component suppliers shipping against rolling schedule agreements run an ASN-GRN-invoice three-way match across four clocks (dispatch, transit, GRN, e-invoice IRN) with cum-quantity drift, lost-in-transit ASNs, ad-hoc PI receipts, and partial rejections. Generic PO-anchored AP three-way matching cannot model this — exception rates above 10% per cycle, recovery losses on lost ASNs, and analyst hours lost to manual cum-quantity reconciliation are the consequences.
- **Logic:** Anchor the match on the ASN (EDI 856), not the PO. Walk forward to the OEM dock-receipt timestamp to form the GRN match. Reconcile the supplier's tax invoice (with IRN from the GST e-Invoice portal) against the matched ASN-GRN pair. Maintain a cum-quantity ledger per schedule agreement reconciling running totals on both sides; flag drift events for joint sign-off. Classify exceptions into four buckets (no-GRN, no-ASN, cum-drift, partial-rejection) and route each to its own resolution path. Split the matched invoice into goods value and conversion value at payment release for Section 393(1) Sl. 8(ii) TDS routing under code 1031.
- **Config:** Schedule-agreement master with cum-quantity counter per OEM per part. ASN feed (EDI 856) by dispatch event. GRN feed by OEM dock-receipt timestamp. Tax invoice feed with IRN reference. Cum-quantity reconciliation ledger with reset-event support. Exception classifier with four-bucket taxonomy. TDS split routing for Section 393(1) Sl. 8(ii) code 1031. OEM-portal handshake (Bosch SupplyOn, Maruti e-Nagare, Tata iFM, M&M Source One) for ASN acknowledgement and GRN pull.
- **Output:** Per-cycle three-way match worksheet showing matched ASN-GRN-invoice triplets, exception lines classified into the four buckets with rupee exposure and aging, the cum-quantity ledger with drift events flagged, the TDS split per matched invoice (goods portion, conversion portion, 1031 code TDS payable), and a recovery-action queue (chase missing GRNs, lift ad-hoc PI receipts into the schedule, negotiate cum-quantity resets, process partial-rejection debit notes within Section 34 cutoff).

### Aftermarket vs OEM Supply: How Reconciliation Discipline Differs for Auto-Component Manufacturers

Source: https://www.terra-insight.com/insights/auto-aftermarket-vs-oem-supplier-reconciliation-differences-india/

- **Problem:** An Indian Tier-1 manufacturer selling into both OEM-fitment and aftermarket channels runs two businesses sharing manufacturing and overhead. The reconciliation discipline differs across at least twelve axes — payment terms, price discovery, warranty mechanics, GST treatment, debit-note classes, returns workflow, Section 34 credit-note basis, Ind AS 115 application, inventory provisioning, channel-discount accrual, segment reporting under Ind AS 108, TDS treatment under Section 393(1) Sl. 8(ii). Tier-1s that try to run aftermarket on the same ledger discipline as OEM-fitment break reconciliation; tier-1s that try to run OEM-fitment on aftermarket discipline lose recovery on debits.
- **Logic:** Run the two channels as separately segmented revenue streams from finished-goods inwards. OEM-fitment: scheduling-agreement master, EDI 830/862/856 flow, OEM GRN-based receivable trigger, consolidated weekly tax invoice, debit-note matching workflow with six debit classes, Section 34 credit notes against consolidated invoice IRN, 60-90 day terms, variable consideration adjustment at period end. Aftermarket: MSL master with FIFO inventory, distributor sub-ledger with credit terms and channel-discount accrual, MRP-driven dispatch invoice, two-tier returns workflow, Section 34 credit notes against dispatch invoice, 30-45 day terms, slow-moving provision and segment reporting at year-end.
- **Config:** Channel-segmented chart of accounts; OEM-fitment scheduling-agreement master plus EDI register; OEM debit-note classification taxonomy with six classes; aftermarket MSL master with distributor sub-ledger; channel-discount accrual policy with volume-tier matrix; Section 34 credit-note workflow split by channel; Section 393(1) Sl. 8(ii) reconciliation split by buyer-type; Ind AS 108 segment-reporting roll-up; warranty workflow split by back-charge vs over-counter.
- **Output:** Two clean P&L segments — OEM-fitment and aftermarket — with channel-specific recoverability analysis, debit-note recovery rate for OEM, channel-margin analysis for aftermarket, segment reporting under Ind AS 108 where each exceeds 10 percent of group revenue, and a defensible split of shared cost basis between the two channels.

### Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ

Source: https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india/

- **Problem:** Auto component exporters run a multi-scheme incentive stack — RoDTEP e-scrips on FOB value by HS code, EPCG duty-free capital imports against a 6x export obligation over six years with block-wise milestones, Advance Authorization duty-free inputs governed by SION input-output norms, and SEZ/deemed-export zero-rating with IGST or ITC refund under Section 16 of the IGST Act — each with its own realisation, fulfilment and refund reconciliation, layered over FIRC/BRC export-proceeds realisation and Section 393(2) Sl. 17 code 1057 TDS on foreign agent commission, which no generic ERP reconciles together.
- **Logic:** Tag every shipping bill to its scheme (RoDTEP / EPCG / Advance Authorization / SEZ-LUT); reconcile RoDTEP entitlement claimed to e-scrip credited to scrip realised; track EPCG export obligation as fulfilled-versus-required at total, block-wise and average-EO levels per authorisation; prove Advance Authorization input consumption within SION ratio per authorisation; tie zero-rated SEZ/EOU supplies to the IGST/ITC refund claimed and sanctioned under Section 16 IGST Act; reconcile export proceeds to FIRC/BRC; withhold Section 393(2) Sl. 17 code 1057 on chargeable foreign agent commission with Form 15CA/15CB.
- **Config:** Shipping-bill-to-scheme tagging; RoDTEP rate table by HS code with per-unit cap; EPCG authorisation register with duty saved, 6x EO, six-year tenure, block milestones and average-EO base; Advance Authorization register with SION norm per product; SEZ/EOU customer master with LUT/bond reference; IGST refund tracker under Section 16 IGST Act; FIRC/BRC realisation calendar; Section 393(2) Sl. 17 code 1057 non-resident withholding with DTAA / TRC / Form 15CA-CB.
- **Output:** A reconciled export-incentive dashboard showing RoDTEP claimed-credited-realised per shipping bill, EPCG EO fulfilled-versus-required at total/block/average levels with shortfall alerts, Advance Authorization SION consumption per authorisation, SEZ/deemed-export IGST-ITC refund claimed-versus-sanctioned, FIRC/BRC realisation status per export, and Section 393(2) Sl. 17 code 1057 withholding on foreign agent commission tied to the remittance and the export realisation.

### Auto-Component TDS/TCS Cross-Era Reconciliation: Bridging FY 2025-26 to FY 2026-27

Source: https://www.terra-insight.com/insights/auto-component-tds-tcs-cross-era-reconciliation-india/

- **Problem:** An Indian Tier-1 auto-component supplier transitioning across 1 April 2026 must reconcile two parallel TDS / TCS lineages through an 8 to 12-month cross-era window — legacy 194x deductions on FY 2025-26 invoices flowing through Form 26Q (deductor) and Form 26AS (deductee), and new Section 393 / 394 / 413 deductions on FY 2026-27 invoices flowing through Form 131 / 141 (deductor) and Form 168 (deductee). Straddling invoices (raised pre-1-April-2026 but paid post-1-April-2026) need the date-of-credit-or-payment-whichever-is-earlier test applied invoice by invoice; ITR cross-era credit claims need legacy and new lineages mapped to the correct assessment year; missing-deduction discoveries from Q4 FY 2025-26 stay under legacy lineage; and the supplier's reconciliation register must hold both lineages without netting through to roughly Q3 FY 2026-27 close.
- **Logic:** Maintain dual-lineage reconciliation registers — one for legacy 194x entries on FY 2025-26 invoices (matched to Form 26Q deductor filings and Form 26AS deductee credits, with TRACES corrections raised under legacy identifiers), one for new section entries on FY 2026-27 invoices (matched to Form 131 / 141 deductor filings and Form 168 deductee credits, with TRACES corrections under new identifiers). For every straddling invoice, apply the time-of-deduction test — earlier of date of credit or date of payment — to assign to the correct lineage. Run monthly Form 168 download (and Form 26AS download for any open legacy lineage), reconcile against the supplier's books, route mismatches into the appropriate dispute register. Prepare the FY 2025-26 and FY 2026-27 ITRs separately, claiming legacy 194x credits against FY 2025-26 income and new 1001-1092 credits against FY 2026-27 income, with explicit cross-era schedules where the income year and deduction year diverge.
- **Config:** Cross-era register with date-of-credit-or-payment discriminator field, legacy-lineage register tagged with 194x section codes and Form 26AS / Form 26Q references, new-lineage register tagged with Section 393 / 394 / 413 codes and Form 168 / 131 / 141 references, straddling-invoice flag (1 January 2026 to 30 April 2026 invoices), ITR cross-era schedule preparation pack, deductor-correction tracking on both lineages, and a controller-level dashboard of cross-era reconciliation health through FY 2026-27.
- **Output:** A cross-era dashboard showing legacy and new lineage entries side-by-side without netting, straddling-invoice resolution log with the date-of-payment-governs determination on each, monthly Form 168 and Form 26AS reconciliation summary, ITR Schedule TDS / TCS preparation pack mapping legacy entries to FY 2025-26 and new entries to FY 2026-27, the deductor-correction dispute register on both lineages, and an audit-defensible trail of every cross-era decision.

### Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers

Source: https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india/

- **Problem:** Indian OEMs raise quality debit notes on supplied parts rejected at the assembly line, apply contractual PPM (parts-per-million) penalties when the defect rate breaches the agreed threshold, demand 8D corrective actions, and back-charge sorting/rework cost when a resident engineer or third-party agency inspects suspect stock — four distinct charges that hit the supplier's settlement together, each needing a different reconciliation and GST treatment, on top of any field-failure/warranty recovery overlap.
- **Logic:** Match each quality debit to its rejection-slip and 8D quality-notification ID and to the supplier's own rejection/return record; compute the supplier's PPM from its records and validate the OEM PPM penalty against the contractual band; tie sorting/rework back-charges to the sorting authorisation, agency invoice and quantity sorted; treat returned goods as a supplier Section 34 credit note (within the 30-November window, OEM ITC reversed) and the replacement dispatch as a fresh tax invoice; keep PPM penalties and sorting charges separate from the goods credit note; flag any line-rejection that also appears as a field/warranty claim to avoid double recovery.
- **Config:** Part master with contractual PPM threshold and penalty band per part/programme; quality-debit taxonomy keyed by rejection-slip ID, quality-notification/8D ID, and charge type (per-part value, PPM penalty, sorting/rework, line-stop); internal rejection/return register; sorting-authorisation and agency-invoice register; GST mapping splitting goods returns (Section 34 credit note, 30-November cutoff) from penalty/sorting recoveries; field-failure/warranty link to detect overlap.
- **Output:** A per-OEM quality reconciliation showing each debit matched to rejection-slip and 8D ID with charge-type split, supplier-computed PPM vs OEM-asserted PPM with penalty-band validation, sorting back-charge tied to authorisation and quantity, a Section 34 credit-note action queue for returned goods with cutoff watch, replacement-dispatch tracking, and an exception queue for contested rejections, PPM-calculation disputes, unauthorised sorting charges, and line-rejection/field-failure double-recovery.

### How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)

Source: https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india/

- **Problem:** Mid-market and enterprise finance teams cannot manually clear 800-plus inward invoices through the IMS accept/reject/pending workflow within the six-day window between GSTR-2B generation on the 14th and GSTR-3B filing on the 20th. Manual processing risks ITC mismatches, Rule 36(4) compliance gaps, and DRC-01C notices.
- **Logic:** An automated workflow pulls IMS data daily, joins it to the purchase register on supplier GSTIN plus invoice number plus tax period, recommends Accept for matched lines, Reject for orphans or amount mismatches, and Pending for review-needed exceptions. The exception queue routes to GSTIN owners with vendor follow-up tasks. Post-decision GSTR-2B is re-pulled and reconciled against accepted-set ITC for GSTR-3B preparation.
- **Config:** Daily IMS pull schedule, purchase-register-to-IMS field mapping, decision-recommendation thresholds (amount tolerance, date tolerance), vendor-follow-up SLA per Pending bucket, multi-GSTIN consolidation rules, and Rule 36(4) audit-trail capture per Accept timestamp.
- **Output:** Daily IMS decision queue with auto-recommended actions, exception report per GSTIN, GSTR-3B-ready ITC value reconciled against post-decision GSTR-2B, vendor follow-up workbook for Pending items, and Rule 36(4)-compliant audit pack for the period.

### Automating TDS Reconciliation: What the Process Looks Like End-to-End

Source: https://www.terra-insight.com/insights/automating-tds-reconciliation-india/

- **Problem:** Manual TDS reconciliation for a company with 60 to 80 deductors across multiple sections takes 3 to 5 staff days per quarter and 2 to 3 weeks at year-end, and still leaves systematic gaps — cross-quarter credits, wrong-section filings, multi-TAN deductors, and Section 197 lower-deduction mismatches that spreadsheets cannot reliably classify.
- **Logic:** Ingest Form 26AS from TRACES, the TDS receivable ledger from the ERP, and bank receipt data in structured form. Perform three-way matching: invoice to bank credit (net of TDS), bank credit to Form 26AS entry, and Form 26AS to deductor TAN via a TAN-to-client master. Classify each mismatch into a typed variance — short deduction, wrong section, cross-quarter, PAN error, Section 197, or challan delay — and route each type to its resolution queue.
- **Config:** TAN-to-client master aggregating multiple TANs per economic entity. Variance taxonomy with typed exception codes. Net-of-TDS receipt matching rule linking bank credit, Form 26AS, and invoice in a single match.
- **Output:** A pre-classified exception list cleared in 2 to 4 hours versus 3 to 5 staff days manually, structured follow-up with deductors for short-deduction and wrong-section corrections, and a reconciled TDS receivable ledger at every quarter close.

### Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns

Source: https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india/

- **Problem:** Indian auto-component manufacturers serve OEMs through a Tier 2-Tier 1-OEM chain on JIT/kanban delivery with short-pays, FOMP warranty back-charges of 1-3% of monthly billing, one-time tooling cost recovered over committed volume, PLI Auto incentive disbursements per ₹26,058 crore scheme, and Section 393(1) Sl. 6(i).D(b) contractor TDS on job-work — five overlapping reconciliation rails that no generic ERP module handles together.
- **Logic:** Reconcile OEM customer at part number and programme level with kanban deliveries matched to short-pay debit notes, FOMP back-charges traced through Tier 1 debit notes to original Tier 2 invoices, tooling amortisation tracked against contractual volume cap per programme, PLI claim filed against value-add-audited incremental sales and reconciled to MoHI bank credit per quarter, Section 393(1) Sl. 6(i).D(b) code 1024 deduction on every job-work invoice with the related Section 143 dispatch challan tracked on its one-year return window.
- **Config:** Customer master keyed by OEM plant code and vehicle programme, kanban delivery schedule by part number, FOMP back-charge taxonomy with claim ID and Tier link, tooling-recovery ledger with cumulative-against-cap tracking per die, PLI eligible-sales calculation table by value-add tier, Section 393(1) Sl. 6(i).D(b) vendor rate matrix with code 1024 default, scrap TCS Section 394 code 1071 ledger for ferrous and non-ferrous waste.
- **Output:** A daily reconciled view per OEM customer showing dispatched kanban quantity to invoiced quantity to paid amount with short-pay variance coded by reason, FOMP exposure aged by claim ID against the Tier 1 running account, tooling recovery progress per programme against contractual cap, PLI claim status per quarter (filed, under-audit, sanctioned, credited), and the monthly Section 393 TDS challan tied to job-work payments by code 1024.

### Avanti Feeds Shrimp Feed Reconciliation — Thai Union JV

Source: https://www.terra-insight.com/insights/avanti-feeds-shrimp-feed-reconciliation-thai-union-jv/

- **Problem:** A vertically integrated Indian shrimp feed and frozen-food group — feed unit selling roughly 500,000 MT of protein-graded feed a year to MPEDA-registered aquaculture farmers across Andhra Pradesh, Tamil Nadu, and Odisha; and a frozen-food subsidiary exporting head-on shell-on and value-added shrimp to the United States, the European Union, Japan, and China — must reconcile a farmer feed sales register keyed to protein grade and pond cycle, a Section 34 CGST credit note run for disease and weather crop-loss adjustments within the Section 34 tax-period reporting window, a Section 92 to 92F inter-company transfer-pricing audit trail against an offshore JV counterparty holding 25 percent or more equity in the Indian shrimp-processing subsidiary (with Section 94A specified-persons documentation where the counterparty is in a notified jurisdictional area, and Rule 10D documentation retained for eight years), and the frozen-food subsidiary's Section 54(3) zero-rated export refund under LUT with Net ITC accumulating across 5 percent feed input, 18 percent packaging, 18 percent cold-chain, and 18 percent power. Manual reconciliation across these four surfaces slips credit-note reporting windows at GSTR-9, breaks farmer MPEDA-reference capture at the sales-invoice level, leaves Form 3CEB benchmarking documentation exposed at the Section 92E filing, and stalls Section 54(3) refund claims at the shipping-bill to e-BRC to GSTR-1 chain match.
- **Logic:** Build a farmer master keyed to MPEDA registration reference, pond cycle identifier, protein grade preference, and cumulative cycle sales; extend every feed sales invoice with protein grade, pond cycle reference, and FCR benchmark; expose crop-loss events (disease, cyclone, salinity, dissolved oxygen) as a first-class object with agronomist certification or PMFBY aquaculture claim attachment; auto-generate the Section 34 CGST credit note with the source invoice reference, the crop-loss event reference, and the tax-period reporting-window guard against the 30 November following the end of the financial year in which the supply was made, or the annual return date, whichever is earlier. For the Thai Union style JV counterparty, run the inter-company invoice register through a Section 92A associated-enterprise classifier, tag every transaction by international transaction type under Section 92B, maintain the Rule 10D contemporaneous documentation set (ownership structure, business description, FAR, industry analysis, method selection, benchmarking study, ALP computation) as a linked artefact per transaction line, and generate the Form 3CEB feed for the Section 92E filing timeline. Where the counterparty is in a Section 94A NJA, run the specified-persons documentation supplement. For the frozen-food subsidiary export refund, reconcile the shipping bill register against the e-BRC bank realisation certificate on the DGFT portal against the GSTR-1 export invoice register against the Net ITC ledger — Rule 89(4) refund formula applied per tax period against the accumulated Net ITC, with input services and capital goods correctly classified for the pure zero-rated variant.
- **Config:** Farmer master with farmer code, MPEDA registration reference, PAN (where filed), pond location (delta, mandal, village), pond area in hectares, cycle stocking date, cycle expected harvest date, protein grade preference; feed SKU master keyed to protein grade (starter 42 percent, grower 38 percent, finisher 35 percent) with HSN 2309 and 5 percent GST; JV counterparty master with equity holding percentage, associated enterprise classification under Section 92A, jurisdiction (with Section 94A NJA flag), inter-company transaction types (feed premix, broodstock, technology, royalty, management fee, financing); Rule 10D documentation register with FAR, benchmarking method (CUP, RPM, CPM, PSM, TNMM), and comparables set; Form 3CEB feed generator keyed to Section 92E filing timeline; frozen-food subsidiary export register with shipping bill number, port of loading, HSN 0306, destination country (USFDA import alert flag, EU RASFF flag, Japan or China variant), FOB value in USD, freight and insurance, and LUT reference; e-BRC feed from AD bank ledger keyed to shipping bill; GSTR-1 export invoice register cross-matched by invoice date and shipping bill date; GST RFD-01 Section 54(3) refund workbook applying Rule 89(4) formula per tax period.
- **Output:** A month-end integrated shrimp feed and frozen-food reconciliation pack: opening balance of farmer feed sales sub-ledger by MPEDA reference, invoice accruals by farmer by pond cycle by protein grade, crop-loss event ledger with agronomist certification and PMFBY claim attachments, Section 34 CGST credit note run with tax-period reporting-window guard, closing farmer sales balance and cycle-close realisation summary; inter-company invoice register with Section 92A associated-enterprise tag, Rule 10D documentation link per transaction line, Section 92E Form 3CEB filing draft, and Section 94A specified-persons supplement where applicable; frozen-food subsidiary export register with shipping bill to e-BRC to GSTR-1 chain match, Section 54(3) refund draft under Rule 89(4) per tax period, and per-shipment traceability from feed batch to pond cycle to shipping bill for downstream RASFF or USFDA import alert response. Per-cycle FCR realisation supports the feed integrator's product formulation feedback loop and the JV counterparty's operations dashboard.

### Axis Bank Corporate Statement Reconciliation: CIB, NEFT/RTGS, MT940 for Indian Treasury

Source: https://www.terra-insight.com/insights/axis-bank-corporate-statement-reconciliation-india/

- **Problem:** Axis Bank's CIB platform exports the same transactions across CSV, PDF, and MT940 with different narration shapes — and the CSV truncates NEFT/RTGS UTRs at the 120-character column boundary. Without channel-aware parsing, '/RFB/' prefix stripping, and holiday-aware date bucketing, weekend and holiday postings collapse into wrong value dates and auto-match falls below 60 percent.
- **Logic:** Channel-aware ingestion routes Axis CSV, MT940, and MT942 to separate parser profiles. NEFT and RTGS narrations are tokenised on hyphen delimiters with '/RFB/' prefix stripping in :86:. Holiday calendar logic maps RBI-notified non-banking days to the next available statement date. Intra-day MT942 postings are tracked for cash visibility but reconciliation closes only against the MT940 :62F: end-of-day balance. Service-charge debits route to the bank charges GL with GST split for ITC.
- **Config:** Axis CIB '/RFB/' parser profile, MT940 end-of-day SFTP ingestion, MT942 intra-day visibility stream, NEFT/RTGS hyphen tokeniser, RBI holiday calendar, Section 194A TDS auto-recon for interest credits above ₹40,000.
- **Output:** Clean Axis transaction ledger reconciled against MT940 :62F:, intra-day cash position from MT942, NACH batch credits exploded against sponsor-bank settlement files, GST-eligible bank charges in the input tax credit register, and Section 194A TDS aligned with Form 26AS.

### Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals

Source: https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation/

- **Problem:** PM-JAY claims for 1,929 treatment packages are settled at state-determined rates with 30-90 day cycles, and package rate variances between hospital charges and approved amounts go untracked.
- **Logic:** Match TMS portal claim submissions to hospital billing records by beneficiary ID and package code. Flag rate variances between hospital charge and PM-JAY approved amount.
- **Config:** 1,929 treatment packages, state-level rate tables, TMS portal as source, preauth validity 60 days, settlement window 30-90 days.
- **Output:** Package-wise claim status report, rate variance analysis, pending preauth tracker, and state-wise settlement reconciliation.

### Backward Integration: API Transfer Pricing to Formulation Plants

Source: https://www.terra-insight.com/insights/backward-integration-api-manufacturing-transfer-pricing-pharma/

- **Problem:** A Tier-1 integrated pharma group operating a backward-integrated manufacturing footprint — a Chapter 29 API plant at Kurkumbh in Maharashtra manufacturing antibiotic APIs, and a Chapter 30 formulation plant at Verna in Goa converting those APIs into finished dosage forms — transfers approximately Rs 350 crore of intra-group Chapter 29 APIs from the API plant to the formulation plant every FY. Where either unit enjoys a tax holiday under Section 80-IE, Section 80-IC, Section 10AA or Section 115BAB, the aggregate crosses the Rs 20 crore Section 92BA previous-year threshold and the transaction is a specified domestic transaction requiring Rule 10D contemporaneous documentation, Section 92C arm's length price determination under one of the six prescribed methods (typically CUP for commodity APIs and TNMM for specialty APIs), and Form 3CEB filing with the annual return by 31 October of the assessment year. In parallel, every intra-group inter-state API dispatch is a paragraph 2 Schedule I supply under the CGST Act 2017 attracting IGST at 5 percent under HSN Chapter 29 heading 2941, valued under Section 15(4) read with Rule 28 (with the full-ITC safe harbour in the second proviso), and generating an ITC availment at the formulation plant that must reconcile to the API plant's outward supply register invoice-by-invoice.
- **Logic:** Build a per-molecule per-tax-period intra-group transfer workbook keyed on the API plant GSTIN and the formulation plant GSTIN. Extract the API plant's outward supply register from GSTR-1 into the dispatch register — captured by HSN sub-heading (2941 antibiotics, 2933 heterocyclic compounds, 2934 nucleic acids), quantity in kilograms, and invoice value at the intra-group transfer price. Extract the formulation plant's ITC register from GSTR-2B into the receipt-side register — matched invoice-by-invoice on GSTIN plus invoice number plus date plus value plus tax. Reconcile the two sides for the tax period so that every dispatch from the API plant has a matching receipt at the formulation plant within the ITC-availment window. On the income-tax side, extract the annual intra-group transfer volume by HSN sub-heading and by molecule from the dispatch register. For each molecule, apply the transfer pricing methodology selected in the Rule 10D documentation — CUP where external market price is verifiable, TNMM where specialty. Compute the arm's length range under Rule 10CA. Compare the intra-group transfer price against the arm's length range. Prepare the Rule 10D contemporaneous documentation with the FAR analysis, the benchmarking study and the arm's length range test. Feed the SDT particulars into Form 3CEB Part C. File Form 3CEB with the return by 31 October of the assessment year. On the GST side, verify that the recipient formulation plant is eligible for full ITC (the standard case post the 22 September 2025 rate reset where downstream Chapter 30 output attracts 5 percent GST), which triggers the second-proviso-to-Rule-28 safe harbour and accepts the invoice value as the open market value.
- **Config:** API plant master and formulation plant master with GSTINs, states, tax-holiday status (Section 80-IE, Section 80-IC, Section 10AA, Section 115BAB flag), and HSN Chapter 29 or Chapter 30 assignment; molecule master keyed by name and HSN sub-heading (2941, 2933, 2934, 2939) with production cost benchmark and industry external market price reference where CUP applies; intra-group invoice register per FY with molecule-wise volume in kilograms and rupees; Section 92BA SDT threshold monitor cumulating aggregate SDT value against the Rs 20 crore previous-year threshold; Rule 10D documentation register per molecule per FY holding the FAR analysis, transfer pricing methodology, benchmarking study, arm's length range under Rule 10CA and comparability adjustments; Form 3CEB Part C feed with per-SDT particulars ready for accountant certification; GSTR-1 outward supply extract from the API plant GSTIN and GSTR-2B inward ITC extract from the formulation plant GSTIN with dispatch-to-receipt matching for the tax period; ITC continuity register from the API plant dispatch to the formulation plant availment; Section 15(4) read with Rule 28 valuation register with full-ITC safe harbour flag per invoice; year-end group-consolidation elimination worksheet for the intra-group profit-in-inventory at the formulation plant balance sheet date.
- **Output:** A year-end backward-integration transfer pricing pack: per-molecule per-FY intra-group transfer volume and value, the Section 92BA SDT threshold cumulation showing whether the Rs 20 crore aggregate is crossed, the Rule 10D contemporaneous documentation set (ownership structure, FAR analysis, transfer pricing methodology, benchmarking study, arm's length range under Rule 10CA), the Form 3CEB Part C draft ready for chartered-accountant certification, the accountant-certified Form 3CEB filed with the return by 31 October of the assessment year, and the parallel GST-side reconciliation showing the intra-group inter-state IGST 5 percent dispatch register from the API plant GSTIN matched invoice-by-invoice to the ITC availment register at the formulation plant GSTIN with the full-ITC safe-harbour flag confirming the invoice value is deemed the open market value under the second proviso to Rule 28. A rolling monthly view surfaces the SDT threshold cumulation early so the Rule 10D documentation build starts before the year-end scramble. A year-end reconciliation between the Section 92C arm's length price and the GST Rule 28 invoice value confirms the two regimes carry the same number, closing the two-track exposure.

### Bajaj Auto and TVS Two-Wheeler Supplier Reconciliation: Operating Model for Indian Auto-Component Tier-1s

Source: https://www.terra-insight.com/insights/bajaj-auto-tvs-two-wheeler-supplier-reconciliation/

- **Problem:** Tier-1 suppliers to Bajaj Auto and TVS Motor operate inside a two-wheeler commercial regime that is structurally different from passenger-vehicle supply — smaller absolute part values, much higher per-part volumes (millions of pieces per month per SKU), faster delivery cycles into a pull-system in-line stores, per-100-piece quality penalties as the dominant debit type, and a Tier-2 chain dominated by heat-treatment / plating / stamping job-work under Section 393(1) Sl. 6(i).D(b) code 1024. A Tier-1 with ₹45 crore annual billing across Bajaj (Chakan, Waluj, Pantnagar) and TVS (Hosur, Mysuru, Nalagarh) faces a higher debit-line count per month than a passenger-vehicle peer at the same revenue.
- **Logic:** Decompose each Bajaj and TVS settlement at the plant-code level, tie each invoice and debit memo to the source two-wheeler programme (Pulsar / Dominar / Avenger / CT / Platina / Chetak EV for Bajaj; Apache / Jupiter / Raider / iQube / Ronin for TVS), classify per-100-piece quality penalties against the supplier's QC record, validate JIT shortage debits against ASN-GRN timing, calendar Section 34 GST credit notes per accepted debit, reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i).D(b) code 1024 against the Tier-1's books, and maintain a Tier-2 job-work payment register for the heat-treatment / plating / stamping outsource chain.
- **Config:** Bajaj Auto and TVS Motor customer masters with sub-records per plant code (Chakan / Waluj / Pantnagar; Hosur / Mysuru / Nalagarh), portal export-mapping for daily release / ASN / GRN / settlement-statement parsing, debit-note reason taxonomy with per-100-piece quality penalty sub-codes, FOMP / warranty back-charge register, JIT shortage register tied to ASN-GRN timing, Form 168 TDS register with Section 393(1) Sl. 6(i).D(b) code 1024 reconciliation, Tier-2 job-work payment register, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-plant, per-programme Bajaj and TVS settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with per-100-piece quality penalty attribution, portal-sourced delivery-schedule reconciliation, rolling-PPM dashboard per part against threshold, Tier-2 job-work TDS register reconciled under Section 393(1) Sl. 6(i).D(b) code 1024, and a Section 34 GST credit-note action queue keyed to approaching cutoff.

### Bajaj Hindusthan Sugar Farmer Payment Arrears Tracker Reconciliation

Source: https://www.terra-insight.com/insights/bajaj-hindusthan-sugar-farmer-payment-arrears-tracker/

- **Problem:** A 14-plant Uttar Pradesh sugar portfolio operating an aggregate 2024-25 crushing season cane payment liability of the order of Rs 4,200 crore must simultaneously (a) run a per-plant ryot-wise arrears aging bucket under Sugarcane Control Order 1966 Clause 3(3A) with a 14-day payment window, (b) accrue interest at 15 percent per annum on every ryot's outstanding balance beyond day 14, (c) segregate the cane development GL between Section 37 revenue expenditure and Ind AS 16 capital expenditure, and (d) key every cane development contractor invoice to TDS code 1001 or 1002 by contractor legal form. Manual reconciliation across 14 plants and hundreds of thousands of ryots loses per-ryot arrears aging, over-provisions or under-provisions the statutory 15 percent interest accrual, mis-classifies drip irrigation head-works as revenue expenditure (or ratoon management as capex), and mis-keys corporate contractor invoices to the individual TDS code — exposing the mill to statutory arrears complaint by the Cane Commissioner, to a Section 37 disallowance at assessment, to an Ind AS 16 audit qualification, and to a Section 201 short-deduction demand from the TDS wing.
- **Logic:** Ingest each plant's cane delivery slip file with ryot code, delivery date, delivery quantity in tonnes, and applicable price per tonne (FRP or SAP by state); build a per-ryot arrears register with a days-outstanding counter running from the delivery date to the payment date; on each day past day 14, accrue interest at 15 percent per annum on the outstanding principal to a statutory arrears interest liability account keyed to the ryot code and the delivery slip number; discharge payment against the oldest arrears first (FIFO) so the interest clock stops on the oldest outstandings; ingest the cane development contractor invoice file, key each invoice to the contractor PAN and to TDS code 1001 or 1002 by legal form, deduct TDS on payment or credit whichever is earlier, and remit against the contractor PAN on Form 26Q; classify each contractor invoice at source as revenue (routed through the Section 37 wholly-and-exclusively test) or capex (routed to the fixed asset register with a useful life and depreciation schedule under Ind AS 16); aggregate the per-plant arrears aging pack, the accrued-interest provision, and the cane development GL split into a monthly close reconciliation for the mill's audit committee.
- **Config:** Plant master with plant code, purchasing centre network, and state (for FRP-versus-SAP application); ryot master with ryot code, PAN (where filed), village, bank account for direct settlement, and delivery-slip series; cane price schedule versioned by crushing season and state (FRP as base, SAP as top-up for Uttar Pradesh, Punjab, Haryana, Uttarakhand); interest accrual configuration set at 15 percent per annum with a 14-day payment window (both statutory anchors, not tunable per plant); cane development GL chart of accounts with activity-type sub-ledgers (ratoon management, drip irrigation, variety trials, pest management, seed cane multiplication) each pre-classified at source as revenue or capex per Ind AS 16; cane development contractor master with contractor code, PAN, legal form (Individual/HUF versus other), TDS code (1001 or 1002), and 26AS reconciliation flag; fixed asset register integration for capex-classified cane development spend with useful life and depreciation schedule; Section 43B(h) MSME flag on cane development contractors registered as MSMEs (drip irrigation vendors and pesticide applicators often qualify).
- **Output:** A month-end multi-plant sugar mill cane payment and cane development reconciliation pack: opening arrears balance by plant and by ryot, cane delivery accrual by plant and by ryot, payment discharge FIFO against the oldest arrears first, closing arrears balance with a days-outstanding aging (0-14, 15-30, 31-60, 61-90, over 90), accrued statutory arrears interest at 15 percent per annum keyed to each ryot beyond day 14, cane development GL split between revenue and capex per Ind AS 16 with a fixed asset register update for the capex tranche, cane development contractor TDS run keyed to code 1001 or 1002 with 26AS reconciliation on file, and Section 43B(h) MSME payment schedule for MSME-registered cane development contractors — packaged for the mill's audit committee and the Cane Commissioner's compliance return.

### Balance Chain Verification: Catching Altered Bank Statements Row by Row

Source: https://www.terra-insight.com/insights/balance-chain-verification-bank-statement/

- **Problem:** A manipulated bank statement with altered transaction amounts, deleted transactions, or an inflated opening balance can appear visually plausible. The running balance column printed on the statement is itself part of the fabricated output and cannot be trusted. Independent recomputation is the only reliable check.
- **Logic:** For every transaction row: take the prior row's balance, add any credit amount, subtract any debit amount, and compare the result to the balance printed in that row. Any row where the computed balance differs from the printed balance — beyond a small rounding tolerance — is flagged. A special check compares the opening balance against what the observed cash flows would imply for an account with no prior history.
- **Config:** Apply a ±1 rupee rounding tolerance per row to account for legitimate decimal truncation in bank printing. Flag the first row where the chain breaks and continue checking all subsequent rows to count total break count. Surface opening balance anomalies as a separate signal from mid-statement chain breaks.
- **Output:** Row-level exception list showing each balance mismatch — the row number, the printed balance, the computed balance, and the discrepancy amount. A count of total chain breaks and an opening balance anomaly flag where applicable, all surfaced in the fraud signals section of the analysis report.

### Bank Statutory Branch Audit (LFAR) in India: Empanelment, Engagement, Execution

Source: https://www.terra-insight.com/insights/bank-audit-statutory-branch-audit-india/

- **Problem:** Bank statutory branch audit is appointment-driven by ICAI MEF empanelment and RBI allocation, executed against the LFAR questionnaire format, and judged primarily on advances ledger reconciliation, NPA classification under IRAC norms, and inter-branch suspense clearance. Year-end fieldwork must complete between April 1 and April 12 to 15 so the Statutory Central Auditor can consolidate by the first-week-of-May Board date.
- **Logic:** Each LFAR section is mapped to a verification programme — advances to drawing power and IRAC, inter-branch to suspense aging, deposits to dormancy and KYC, contingent liabilities to BG and LC registers. NPA sampling covers all four asset classifications proportionally; reconciliation between the General Ledger control account and the loan-wise sub-ledger is performed on the full branch advances book before sample selection.
- **Config:** LFAR section to verification matrix, IRAC sampling plan keyed to standard/sub-standard/doubtful/loss with size bands, inter-branch suspense aging schedule, drawing power recomputation worksheet, and the engagement timetable mapping each procedure to a fieldwork day.
- **Output:** Signed branch audit report, completed LFAR, tax audit report, Ghosh and Jilani Committee certificates, capital adequacy data, and a documented reconciliation file that the Statutory Central Auditor can rely on for bank-level consolidation.

### Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching

Source: https://www.terra-insight.com/insights/bank-charges-reconciliation-india/

- **Problem:** Bank service charges (NEFT, RTGS, IMPS, account maintenance, cheque book, DD, locker) arrive as auto-debits under SAC code 997119 with 18% GST embedded — no prior invoice, variable amounts by transaction volume, and batched debits that obscure the split between base charge and GST. Unreconciled charges leave ITC unclaimed each month.
- **Logic:** Narration-pattern matcher parses auto-debit lines like 'NEFT CHG [date] [count] TXN [amount] GST [gst]' to extract base fee and 18% GST separately. Each debit is routed to the bank charges GL with GST flagged for ITC. Monthly bank tax invoice is cross-matched against GSTR-2B and the accumulated debits for the period.
- **Config:** Bank-specific charge narration patterns, ±₹5 or ±1% tolerance bands for FEE_VARIANCE, SAC 997119 mapping, and monthly tax-invoice matcher to GSTR-2B.
- **Output:** Reconciled bank charges expense ledger with GST split, monthly ITC claim aligned to GSTR-2B, FEE_VARIANCE exception queue for fee-schedule disputes, and audit trail from auto-debit to ITC claim.

### Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies

Source: https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india/

- **Problem:** A Bank Reconciliation Statement must explain the gap between cash book balance and bank statement balance at every period end. Unexplained BRS items (expired cheques, stale deposits in transit, unrecorded bank charges) produce audit observations, delayed sign-offs, and suggest internal-control weakness.
- **Logic:** Prepare a standard-format BRS per bank account at period end: start from cash book balance, add unpresented cheques, deduct deposits in transit, adjust for bank errors and unrecorded bank charges, arriving at the bank statement balance. Age each reconciling item; reverse cheques stale-dated beyond 3 months and post unrecorded bank charges immediately.
- **Config:** Standard BRS template per account, 3-month stale-cheque rule, 1–3 business day NEFT/RTGS clearance tolerance, and period-end sign-off by preparer and reviewer.
- **Output:** A signed BRS for every bank account for the last day of the financial year and each quarter-end, with no unexplained items above 30 days and full documentation for statutory audit.

### Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions

Source: https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals/

- **Problem:** NBFC credit decisions degrade when all bank statement signals are weighted equally — overweighting low-priority metrics like average balance while underweighting NACH bounce history produces both false approvals and false declines.
- **Logic:** Signal families are ranked by predictive value for Indian NBFC portfolios, with NACH/EMI continuity, income regularity, and balance distribution on mandate dates treated as primary signals, and risk word hits or single-month anomalies treated as supporting context.
- **Config:** The analysis framework requires 3 to 12 months of statements depending on loan product, with bank-specific NACH return code mappings to normalise abbreviated codes across PSU and co-operative banks.
- **Output:** A prioritised credit signal report covering 40+ indicators across income, obligation, balance, and risk categories, with each signal labelled by confidence level based on the statement format quality.

### Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It

Source: https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india/

- **Problem:** NBFC credit officers reviewing MSME loan applications cannot reliably separate income from transfers in co-mingled bank accounts, compute defensible FOIR, or identify NACH delinquency signals through manual statement review at volume.
- **Logic:** Bank statement analysis classifies every credit entry into income or exclusion categories, computes FOIR from identified recurring NACH/ECS debits, checks NACH continuity over the prior 6 months, and flags round-trip transactions and balance anomalies that signal misrepresentation.
- **Config:** The statement period required is 3 months for small-ticket loans, 6 months for mid-range personal and business loans, and 12 months for MSME working capital — aligned to RBI's cash-flow-based underwriting guidance.
- **Output:** A credit appraisal-ready report with classified monthly income, current FOIR, post-proposed-EMI FOIR, NACH continuity status, and risk flags, documented for RBI inspection purposes.

### Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions

Source: https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases/

- **Problem:** NBFCs applying uniform bank statement analysis across all loan products miss product-specific signals — a microfinance mandate check and an MSME working capital assessment require different data extractions from the same document.
- **Logic:** Analysis is configured per loan product: MSME underwriting separates business from personal cash flows and checks 12 months for seasonality; microfinance checks balance on specific mandate debit dates; digital lending scores thin-file borrowers using NACH and balance patterns rather than bureau history.
- **Config:** Each NBFC loan product requires a defined statement period (3, 6, or 12 months) and signal threshold set aligned to its credit policy and RBI product-level guidelines.
- **Output:** A product-appropriate credit signal report that covers the 40+ indicators relevant to each loan type, with FOIR, NACH continuity status, and loan-stacking flags ready for the credit appraisal note.

### Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know

Source: https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit/

- **Problem:** Indian lenders conflate bank statement analysis with bank statement audit, leading to either over-engineering routine credit decisions or under-documenting compliance requirements that actually need a CA opinion.
- **Logic:** Bank statement analysis extracts income, FOIR, bounce history, and risk signals for credit decisions in minutes with no statutory requirement; a bank statement audit is a CA engagement under ICAI standards that produces a formal opinion for statutory or regulatory purposes and takes days to weeks.
- **Config:** NBFCs should use automated analysis for all credit underwriting decisions and commission CA audits only when required by the Companies Act, RBI inspection, or income tax proceedings — not for routine loan files.
- **Output:** Clear documentation of which process applies to each scenario: an internal credit report for underwriting or a signed CA opinion letter for statutory and regulatory purposes, avoiding both unnecessary audit cost and compliance gaps.

### Bank Statement Column Variants in India: Why 300+ Format Patterns Exist

Source: https://www.terra-insight.com/insights/bank-statement-column-variant-parsing/

- **Problem:** Indian bank statement PDFs use 300+ distinct column name variants for date, debit, credit, and balance fields across banks and channels, causing column misidentification that produces catastrophically incorrect income and expense figures.
- **Logic:** A header-matching engine compares extracted column labels against a comprehensive variant library, falling back to positional inference for unlisted headers, and validates all assignments using balance-chain verification to catch swapped debit/credit columns.
- **Config:** The variant library must be maintained with new column names discovered from bank software updates and merger-era legacy layouts; confidence flags on positionally-inferred columns alert credit teams to statements needing manual verification.
- **Output:** A correctly mapped transaction table where each column is labelled with its semantic role and confidence level, ready for income classification and FOIR computation.

### Bank Statement PDF Metadata Inspection: What Credit Teams Should Check

Source: https://www.terra-insight.com/insights/bank-statement-metadata-inspection/

- **Problem:** Credit teams cannot reliably detect edited bank statement PDFs by visual inspection alone. A document with modified transaction amounts or a boosted opening balance can look identical to a genuine statement unless the PDF's internal metadata is examined.
- **Logic:** Inspect four metadata fields on every uploaded PDF: Creator (the application that originally created the document), Producer (the PDF rendering engine), CreationDate (when the file was first generated), and ModDate (when the file was last modified). Bank-generated PDFs from known core banking software show consistent Creator/Producer values and matching creation and modification dates. Consumer editing tools update these fields automatically, exposing the edit.
- **Config:** Match Creator and Producer values against a reference list of known banking software (Finacle, Flexcube, iText, Crystal Reports, Temenos T24) and known editing tools (iLovePDF, Smallpdf, Foxit PDF Editor, Adobe Acrobat DC, LibreOffice Draw, FPDF, ReportLab). Flag when CreationDate differs from ModDate by more than a de minimis threshold.
- **Output:** Per-PDF metadata verdict — Clean, Flagged for Review, or Unknown — with the specific field values that triggered the classification, surfaced in the fraud signals section of the bank statement analysis report.

### Bank Statement Narration Pattern Classification: A Library for Indian Treasury Teams

Source: https://www.terra-insight.com/insights/bank-statement-narration-pattern-classification-india/

- **Problem:** Indian bank statement narrations are not standardised. The same NEFT credit can appear as 'NEFT CR:[UTR]/...' in one bank, 'NEFT-[UTR]-...' in another, and 'TRANSFER FROM ... UTR [UTR]' in a third. Without a classification library, reconciliation engines either miss the UTR or assign the transaction to the wrong family, breaking downstream auto-match.
- **Logic:** An 18-family classification model anchored on short tokens (NEFT, RTGS, IMPS, UPI/, NACH, ECS, CHQ, CHRG, INT, TDS, CASH) routes each narration to one family before secondary extraction runs. Direction (debit or credit) splits same-anchor families like NEFT-In versus NEFT-Out. Ambiguous prefixes are resolved by a priority-ordered rule list that evaluates the most specific token first. Bank-specific delimiters (forward slash, pipe, dash) are normalised to a single canonical separator before UTR and counterparty extraction.
- **Config:** Anchor token library with 20 to 25 entries, bank-specific delimiter normalisation profile (HDFC, ICICI, SBI, Axis, Kotak, Yes, IndusInd, PSU banks), direction-based disambiguation, aggregator counterparty allowlist for PG-Settlement routing, quarterly unmatched-narration review process.
- **Output:** Each statement row tagged with one of 18 transaction families, a clean extracted match key (UTR, UPI ref, NACH batch ID, or cheque number), and a canonical counterparty string ready for fuzzy matching against the sub-ledger.

### Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them

Source: https://www.terra-insight.com/insights/bank-statement-narration-patterns-india/

- **Problem:** RBI mandates UTR format (22 characters: 4-char bank code plus 2-digit year plus 3-digit day plus 7-digit sequence) but not the surrounding narration template. HDFC uses forward slashes, ICICI hyphens, Axis spaces — so a single reconciliation setup must parse bank-specific formats across NEFT, RTGS, IMPS, UPI, and NACH without truncation breaking the UTR.
- **Logic:** Per-bank parser configurations extract UTR, counterparty name, and reference from each narration using bank-specific delimiters and prefixes. NACH batch credits are exploded against the sponsor-bank batch file to individual mandate references. Truncated or UTR-less narrations fall back to amount plus date plus counterparty-pattern matching with dedup guardrails.
- **Config:** Bank-by-bank narration parser library (HDFC /INF/ prefix, ICICI /TXT/, Axis plain), UTR regex, NACH batch file ingestion, and truncation-fallback rules.
- **Output:** Consistent match keys across multi-bank inflows, NACH batch explosion into mandate-level ledger, exception queue for UTR-truncated and reference-less transactions, and reconciled statement-to-book trail.

### Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs

Source: https://www.terra-insight.com/insights/bank-statement-ocr-india/

- **Problem:** Indian NBFC underwriting desks receive bank statements in three structurally different formats — digital PDFs, scanned photocopies, and password-protected files — each requiring a different processing path. PSU and co-operative bank statements add further complexity through format heterogeneity, faded scans, and non-standard column layouts.
- **Logic:** Route each statement to the correct processing path: digital PDFs via native text extraction; scanned PDFs via an OCR pipeline with premium cloud fallback for degraded quality; password-protected PDFs via supplied or systematically derived password candidates. Multi-statement batches are deduplicated and merged before credit signal extraction.
- **Config:** 34+ dedicated bank parsers; 300+ column-name variant generic fallback engine; 150+ RBI bank holiday calendar; lakh-crore number format handling; Indian date convention (DD/MM/YYYY) and UPI/NEFT/NACH narration parsing
- **Output:** Structured transaction rows (date, narration, debit, credit, running balance) from all statement types, delivered as a structured Excel workbook and JSON, ready for credit signal extraction

### Bank Statement OCR vs Machine-Readable Formats: When to Use Which for Indian Reconciliation

Source: https://www.terra-insight.com/insights/bank-statement-ocr-pdf-vs-machine-readable-india/

- **Problem:** A finance team ingesting statements from 8-12 Indian banks gets a mix of machine-readable CSV and MT940 from the top private banks, and PDF or scanned PDF from PSU branches, cooperative banks, and archived periods. Mis-routing a scanned dot-matrix statement to a CSV parser produces silent failures; relying on OCR for statements where a CSV exists wastes accuracy and review time.
- **Logic:** Source classification routes each incoming statement to the right ingestion mode based on file type, generation method (digital vs scanned), and the bank's known capabilities. Typed PDFs and CSVs go to direct parsing; scanned PDFs and dot-matrix prints go to OCR with a confidence threshold; password-protected PDFs are unlocked before classification. A hybrid pull strategy fetches both PDF and CSV for any bank that exposes both, using the CSV for transaction posting and the PDF for balance certification and narration backfill.
- **Config:** Per-bank ingestion profile (CSV first, MT940 first, PDF OCR fallback), OCR confidence threshold per amount and narration field, password store for protected PDF exports, hybrid pull schedule per bank, and human review queue for low-confidence lines.
- **Output:** Clean transaction ledger from every source regardless of format, certified opening and closing balances reconciled to the signed PDF, narration backfilled from PDF where CSV truncates, and a per-bank accuracy report tracking OCR confidence drift over time.

### PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs

Source: https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india/

- **Problem:** Indian bank statement PDFs span three distinct document types — native digital, scanned image, and hybrid — each requiring different extraction methods, while lakh-crore number formats and UPI narration patterns break generic international parsers.
- **Logic:** The parser detects document type per page, applies direct text extraction for native pages and the OCR pipeline for scanned pages, then applies India-specific number formatting and NPCI payment rail narration patterns to produce structured transaction data.
- **Config:** No configuration is required from lenders — format detection, number parsing convention, and narration classification are handled by the India-specific parser library covering 300+ column name variants.
- **Output:** A clean, merged transaction table with standardised date, amount, and narration fields regardless of whether the source PDF was native, scanned, or hybrid.

### Banquet Event Advance Reconciliation: Contract to Final Folio in India

Source: https://www.terra-insight.com/insights/banquet-event-advance-reconciliation/

- **Problem:** A banquet booking creates a contract liability months before the event, an advance receipt that triggers GST under Section 13 of the CGST Act, and a final folio split across hall, menu, decor, and bar sub-billing — leaving hotel finance teams unable to prove that every advance is either consumed against a final invoice, refunded, or forfeited with the right tax treatment.
- **Logic:** Build a three-tier reconciliation: contract (hall, menu rate, expected covers, decor, bar quote) vs PMS advance-deposit ledger (advance receipt voucher, GST, bank credit) vs final folio (actual covers, hall hire posted, decor pass-through, bar consumption). Apply time-of-supply GST on advance receipt with adjustment at final invoice. Handle cancellation flows with forfeit-vs-refund branching and corresponding GST treatment.
- **Config:** PMS adapter pulling advance-deposit ledger and event folio; contract repository linking event ID to BEO; F&B POS feed for banquet covers and bar; vendor pass-through accruals for decor and AV; GST advance-adjustment logic per Section 13 CGST; cancellation rules per contract template.
- **Output:** A reconciled event close showing contract value matched to advance plus balance plus consumption, a clean GSTR-1 advance-and-adjustment line, a forfeit handler emitting either a tax invoice or a refund voucher, and a zero-balance advance-deposit ledger after every closed event.

### Basmati Rice Export Reconciliation — MEP + RoDTEP India Cornerstone

Source: https://www.terra-insight.com/insights/basmati-rice-export-reconciliation-mep-rodtep-india/

- **Problem:** A basmati rice exporter shipping 8,500 metric tonnes per month across US, EU, and Middle East destinations must reconcile every shipping bill against the commercial invoice, verify FOB compliance against the DGFT Minimum Export Price floor for shipments falling in the 25 August 2023 to 13 September 2024 notification window (USD 1,200/MT and then USD 950/MT), claim RoDTEP scrip on HSN 1006 30 20 (raw basmati) and 1006 30 90 (parboiled) under Appendix 4R, and match e-BRC bank realisation against the shipping bill by BL cycle for FEMA nine-month realisation compliance. Manual reconciliation across shipping bill filing, APEDA RCAC registration, commercial invoice negotiation, RoDTEP scrip crediting on the DGFT portal, and e-BRC issuance loses period-specific MEP flags, misses RoDTEP scrip disbursement follow-ups, and lets unrealised shipping bills drift past the FEMA nine-month window into caution-listed exposure.
- **Logic:** Build a shipping bill master keyed on the shipping bill number with attached RCAC number, port code, HSN classification (1006 30 20 raw or 1006 30 90 parboiled), destination country, FOB value per MT, and BL date. Attach a period-specific MEP compliance flag against the shipping bill date — USD 1,200/MT if the bill falls between 25 August 2023 and 25 October 2023, USD 950/MT if between 25 October 2023 and 13 September 2024, and no floor otherwise — and surface any FOB shortfall as a reconciliation exception. Ingest the APEDA contract register and reconcile every shipping bill RCAC number back to an active contract. Ingest the RoDTEP e-scrip ledger from the DGFT portal and reconcile every EGM-closed shipping bill against the corresponding scrip credit with the notified Appendix 4R rate applied to the FOB value. Ingest the e-BRC feed from the DGFT portal and match every shipping bill to its FIRC-linked e-BRC issuance; surface unrealised bills approaching the FEMA nine-month timeline. Ingest the arhtiya purchase register and apply Section 8 Sl. 8 code 1031 TDS at 0.1 percent on aggregate annual purchases above Rs 50 lakh per PAN.
- **Config:** Shipping bill master with shipping bill number, RCAC number, port code, HSN (1006 30 20 or 1006 30 90), destination country ISO code, FOB per MT in USD or EUR, BL date, and MEP-period stamp; APEDA contract register with RCAC number, contract date, buyer name, quantity, and FOB; RoDTEP e-scrip ledger extract from DGFT portal with scrip number, shipping bill link, notified Appendix 4R rate, scrip value, and credit date; e-BRC feed from DGFT portal with shipping bill number, FIRC number, foreign currency amount, INR realisation, exchange rate applied, and issuance date; AD bank EDPMS extract for FEMA realisation timeline tracking; arhtiya master with PAN, GSTIN, mandi, and Section 194Q flag (code 1031 at 0.1 percent above Rs 50 lakh annual); commercial invoice register with invoice number, buyer name, currency, amount, and shipping bill link; MEP notification history table (USD 1,200/MT effective 25 August 2023 to 25 October 2023, USD 950/MT effective 25 October 2023 to 13 September 2024, no floor from 13 September 2024).
- **Output:** A month-end multi-document basmati export reconciliation pack: shipping bill by shipping bill register with period-stamped MEP compliance flag and exception on any FOB shortfall against the applicable floor, APEDA RCAC-to-shipping-bill match tally, RoDTEP e-scrip credit reconciliation against EGM-closed shipping bills with an ageing bucket for scrip disbursement delay, e-BRC issuance status against every unrealised bill with an ageing bucket against the FEMA nine-month timeline, EDPMS variance report against the AD bank's own EDPMS extract, code 1031 TDS remittance schedule against arhtiya purchases above the Rs 50 lakh threshold, and — for the reconciliation exception window — a MEP-period audit trail extract that can be produced on demand for RoDTEP scrutiny or FEMA audit.

### BCD on Cotton Imports — Customs Duty Reconciliation for Textile India

Source: https://www.terra-insight.com/insights/bcd-cotton-imports-customs-textile-india/

- **Problem:** An Indian premium shirting or fabric mill importing extra-long-staple (ELS) cotton — Giza from Egypt, Pima from Peru or the United States, Australian ELS from Queensland — must reconcile every Bill of Entry against the customs tariff notification in force on the BoE filing date, split the duty payment into BCD, Social Welfare Surcharge, AIDC (non-creditable costs) and IGST (credit-eligible), and post each component to the correct GL. The exposure is that the CBIC customs tariff notification regime on cotton BCD changes with almost every Union Budget cycle and every shortage year — a mid-shipment notification change can swing landed cost by 15 percent or more, and a wrong notification reference on the BoE surfaces at post-clearance audit as a short-paid or excess-paid duty. Missing or mis-claiming IGST input credit on the BoE-linked IGST — through wrong classification, wrong return period, or wrong split between IGST and CGST/SGST — triggers a Section 73/74 GST notice and interest exposure at the mill's PAN level.
- **Logic:** Build a customs import register keyed by BoE number, BoE date, purchase order, bill of lading, container number, and country of origin. Ingest the ICEGATE BoE data feed and the customs broker's duty computation. Cross-reference every BoE filing date against the CBIC customs tariff notification calendar — for HS 5201 cotton, the operative BCD rate (base 10 percent or exempted), SWS (10 percent on BCD), AIDC (5 percent or exempted), and IGST (5 percent domestic supply rate). Compute the expected duty at each component level; match against the ICEGATE payment challan for that BoE. Post BCD, SWS, and AIDC to landed cost (allocated per bale per lot); post IGST to the input IGST at customs ledger and reconcile against GSTR-3B Table 4A(1) auto-population. Track the 30 November following FY as the outer time-limit for input credit under Section 16(4) CGST for every BoE.
- **Config:** Import-register master with BoE number, BoE date, PO reference, bill of lading, container, port of import, and country of origin; CBIC customs tariff notification calendar (BCD, SWS, AIDC, IGST rate periods) for HS 5201; landed cost GL mapping — BCD to duty-cost, SWS to cess-cost, AIDC to AIDC-cost, IGST to input-IGST-credit; ICEGATE BoE feed and challan feed for duty payment; GSTR-3B Table 4A(1) IGST-at-customs auto-population for credit claim reconciliation; Section 16(4) outer-time-limit alert at 30 November following FY of import; per-bale-per-lot landed cost allocation for standard-cost inventory posting.
- **Output:** A per-BoE landed cost pack: customs assessable value, BCD (with applied notification reference), SWS on BCD, AIDC (with notification reference), IGST base (assessable value plus BCD plus SWS plus AIDC), IGST credit-eligible, total landed cost, and per-bale allocation. Notification-calendar cross-check flags any BoE where the applied notification version does not match the operative notification on BoE filing date. IGST input credit register reconciles against GSTR-3B Table 4A(1) auto-population from ICEGATE. Section 16(4) outer-time-limit exposure by BoE, with alerts at 60, 30, and 15 days from 30 November following FY of import. Post-clearance audit-ready pack — every BoE with notification reference, duty payment challan, GL posting, and credit claim, all keyed to the same BoE number.

### Bayer CropScience India Reconciliation — Import + Formulate + Distribute

Source: https://www.terra-insight.com/insights/bayer-cropscience-india-msil-reconciliation-import-formulate/

- **Problem:** A listed Indian agrochemical formulator subsidiary of a European multinational running an illustrative Rs 4,800 crore of FY 2026-27 turnover with Rs 2,200 crore of Active Ingredient imported from the German parent plus subsidiaries, formulated at a Halol Gujarat plant, and pushed through a four-tier distributor pyramid (national to state to district to retailer) must reconcile the customs BCD plus IGST plus AIDC on the AI landed cost, the Rule 10D transfer pricing documentation on the related-party AI transfer plus separate royalty accrual, the Section 195 TDS on the royalty remittance to the German parent under the India-Germany DTAA Article 12, the Section 194H code 1015 commission on the four-tier distributor pyramid, the Section 15(2) CGST trade discount treatment for kharif and rabi BOGO scheme incentives, and the Ind AS 21 forex translation on the AI import ledger plus royalty accrual — all without falsely applying Section 194Q on the import leg (which the Customs mechanism already covers) and without confusing the top-tier Section 194H obligation with downstream tier obligations that reset at each payer.
- **Logic:** Ingest the customs Bill of Entry (BOE) ledger with the assessable value, BCD, IGST, and AIDC broken out per consignment; key each BOE to the underlying purchase order from the German parent under the licence agreement and to the Rule 10D arm's-length benchmarking file. Separate the AI transfer price component (recovered via customs) from the royalty accrual component (a distinct chargeable-under-the-Act sum for Section 195 purposes), and apply the India-Germany DTAA Article 12 rate of 10 percent on the royalty leg subject to a valid TRC and Form 10F on file. Track the customs IGST paid at import as an eligible ITC claim in the GSTR-3B feed, and reconcile against the CBIC-issued Bill of Entry ledger for consignment-by-consignment ITC assertion. Aggregate the four-tier distributor commission cycle at the top tier only for the manufacturer's Section 194H code 1015 obligation; expose downstream tier commission for audit visibility but do not include those in the manufacturer's Form 26Q filing base. Extract every kharif or rabi scheme document and match against the underlying invoice or credit note ledger for Section 15(3) qualification; where scheme documentation is missing or post-facto, flag the scheme value as staying in the transaction value with GST liability retained. Feed the AI import ledger into an Ind AS 21 forex translation worksheet with spot rates on transaction date and closing rates at each reporting period end, and recognise exchange differences in P&L unless hedge-accounted under Ind AS 109.
- **Config:** Foreign parent master with associated-enterprise identifier under Section 92A, country of residence, DTAA article reference, TRC validity window, and Form 10F on file; Rule 10D documentation set with FAR analysis, transfer pricing method, comparable set, and Form 3CEB linkage per assessment year; customs BOE master keyed to consignment ID, HSN, tariff line, BCD rate, IGST rate, and AIDC applicability; royalty accrual master keyed to formulation output volume or turnover as per the licence agreement, with Section 195 TDS rate under the DTAA and Form 27Q reporting schedule; distributor master with tier identifier (national/state/district/retailer), PAN, GSTIN, TDS code 1015, and commission slab; kharif/rabi scheme master with scheme document date, invoice linkage, and Section 15(3) qualification flag; Ind AS 21 exchange rate feed for the reporting entity's functional currency (INR); CIB&RC registration register with Section 9(3), 9(3B), or 9(4) registration reference per AI plus per formulation.
- **Output:** A month-end and year-end reconciliation pack covering: consignment-by-consignment AI import ledger with BCD, IGST, and AIDC broken out and reconciled against the CBIC BOE ledger; Section 195 TDS remittance schedule on royalty accrual reconciled against Form 27Q and the receiving parent's Form 15CB certification; Rule 10D related-party transaction register cross-referenced against the Form 3CEB filing base; distributor commission cycle top-tier accrual with code 1015 TDS reconciled against the manufacturer's own Form 26Q filing; downstream tier commission visibility register (audit-only) that clearly delineates the payer at each tier; kharif/rabi scheme register with Section 15(3) qualification flag per scheme and cross-referenced against the credit-note ledger in GSTR-1; Ind AS 21 forex translation workbook with the AI import ledger and royalty accrual translated at spot rates on transaction date and closing rates at each reporting period, with exchange differences to P&L reconciled against the annual audit adjusting entries; and a CIB&RC registration register mapping each imported AI plus formulated product to its active Section 9 registration.

### Best Reconciliation Software for Indian Businesses in 2026: A CFO Buyer Guide

Source: https://www.terra-insight.com/insights/best-reconciliation-software-india-2025/

- **Problem:** Indian CFOs evaluating reconciliation software are steered by global product directories that rank platforms on generic feature sets and miss the India compliance stack — TDS net-of-gross receipt matching, GSTR-2B locking, NACH return codes, and UPI netting — where a feature gap becomes a compliance liability after go-live.
- **Logic:** Apply a binary India-compliance filter first: does the platform handle TDS section codes with Form 26AS matching, GSTR-2B JSON ingestion with Rule 36(4) cap enforcement, NACH NPCI XML return classification, and multi-entity GSTIN separation natively. Then test matching depth on the buyer's own data using multi-pass matching with configurable tolerance bands and variance taxonomy. Reject vendors quoting custom development over 8 weeks.
- **Config:** Vendor evaluation scorecard with seven dimensions — India tax stack, payment rails, deployment model, matching engine, audit trail, security certifications, pricing — weighted by the buyer's transaction mix. Industry presets (manufacturing, NBFC, e-commerce, healthcare) pre-load the matching rules so config-only deployment goes live in 2–4 weeks.
- **Output:** A signed vendor selection defensible to the board and audit committee, with a 2–4 week go-live path, 70–85% first-pass match rate contracted, ISO 27001:2022 and AWS Mumbai residency confirmed, and TDS/GSTR-2B exception queues classified by variance code from day one.

### Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation

Source: https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation/

- **Problem:** Indian manufacturers running standard costing see month-end variances between standard cost of finished goods (rolled up from BOM) and actual cost (sum of materials issued plus labour and overhead) drift into COGS as a single unexplained gap of 3-8% of cost — without analytical allocation across Price, Usage, Yield and Substitution buckets, the variance becomes a recurring P&L noise that hides genuine procurement, shop-floor and process problems.
- **Logic:** Run BOM cost reconciliation at month-end by: (1) extracting standard cost roll-up per finished good from the BOM master; (2) capturing actual material issue per production order from the inventory ledger at actual issue rate; (3) capturing actual output from the production output report; (4) computing variance per material per production order and splitting into Price (PPV), Usage, Yield, and Substitution buckets using the classical variance formulas; (5) posting each bucket to its own GL account with monthly absorption rules.
- **Config:** BOM master with standard quantity and standard rate per component, production order master with planned versus actual, inventory issue ledger at actual rate, production output report per order, GL chart with four variance accounts (PPV, Usage, Yield, Substitution), variance threshold per finished good category, and monthly variance absorption rules (to COGS vs to WIP).
- **Output:** A monthly variance dashboard where every finished good's standard-versus-actual gap is split into four buckets per material, attributed to procurement, shop-floor, process or planning, posted to the relevant GL, and aggregated to a single P&L variance line that ties back to the trial balance — converting an opaque cost gap into four actionable variance streams.

### BillDesk MDR Reconciliation: Bill Aggregator and Institutional Merchant Pricing

Source: https://www.terra-insight.com/insights/billdesk-mdr-reconciliation-india/

- **Problem:** BillDesk's settlement file looks superficially similar to a Razorpay or PayU settlement export, but it carries a biller-share column that depends on whether the bill payment is routed through Bharat BillPay or through a direct biller channel, and the MDR slab depends on whether the biller is a regulated utility, a government department, an insurance company or a private institutional merchant. A utility biller on a Rs 85 crore monthly electricity collection cycle has no automatic way to know whether net banking is being billed flat-fee or percentage, whether the BBPS biller-share matches the regulated apportionment, and whether the per-bill-type slab in the settlement file matches the contracted schedule.
- **Logic:** Reconciliation joins each BillDesk settlement_batch_id to the bank credit by UTR plus date plus net amount, then resolves every bill payment to its biller category and bill type. A per-instrument expected-rate model — net banking either flat per-transaction or percentage by partner bank, credit card at the contracted slab, UPI at the network rate applicable to the biller category, BBPS biller-share against the regulated NPCI fee structure for that bill type — is compared against the actual fee in the settlement file. Variance above 0.10 percentage points on the effective blended rate triggers a per-instrument audit. Zero-rated UPI bill payments under utility BBPS flows are verified at the per-transaction level — any positive network MDR on a contractually zero-rated instrument is flagged as leakage. The bill-cycle level reconciliation ties biller MIS to BillDesk settlement to bank statement as three legs of a single closing.
- **Config:** BillDesk settlement-file ingestion with the published column structure (Customer Reference, Biller Reference, Bill Number, Bill Type, Payment Instrument, Partner Bank Code, Card BIN, UPI Handle, Gross Collection, MDR Amount, Biller-Share, Gateway-Share, GST on MDR, Net to Biller, Settlement Batch ID, Settlement UTR, Settlement Date), per-instrument expected-rate table loaded from the signed biller contract and the BBPS regulated fee schedule, bill-type and biller-category mapping, net banking flat-fee versus percentage rule by partner bank, BBPS biller-share verification against NPCI apportionment, Section 393(1) Sl. 8(v) payment-code 1035 TDS column reconciling to Form 26AS, and GST on MDR reconciliation to GSTR-2B.
- **Output:** A monthly per-instrument effective-rate report that separates net banking, card, UPI and BBPS biller-share into their true cost lines for each bill type, a bill-cycle level closing that ties biller MIS to BillDesk settlement to bank statement, a zero-rated UPI verification ledger flagging any transaction billed at a positive network MDR on a contractually zero-rated instrument, a TDS reconciliation against Form 26AS for the operator deduction, an input-tax-credit claim file for the GST on the BillDesk MDR aligned to GSTR-2B, and a contract-renewal pack that decomposes the prior period's per-instrument and per-bill-type variance against the negotiated schedule.

### Biscuit Segment GST 2.0 Reconciliation (HSN 1905 all at 5%)

Source: https://www.terra-insight.com/insights/biscuit-segment-gst-2-0-reconciliation-fmcg/

- **Problem:** The 22 September 2025 GST 2.0 transition consolidated HSN 1905 biscuits at 5%, eliminating the pre-22-September ₹100/kg price-tier split that placed Parle-G and Tiger at 18% and Marie Gold and Good Day at 12%. The transition opens four parallel reconciliation gaps for Parle, Britannia, ITC Foods, and Sunfeast operators — transition-period closing stock at distributor warehouses needing Rule 42 ITC reversal, distributor scheme cycles that straddle both rates needing per-line rate tagging on the accrual register, credit notes for post-supply discounts needing to follow original invoice rate per Section 34, and GSTR-1 amendments on cross-period dispatches cascading into recipient GSTR-2B mismatches. A brand that hard-codes a single rate per HSN without an effective-date dimension over- or under-accrues on every cross-period scheme through FY 2025-26.
- **Logic:** Maintain an HSN master with a rate-effective-date field — HSN 1905 carries the 18% / 12% / 5% effective-date stack, with 5% in force on and after 22 September 2025. Tag every dispatch invoice line with the rate-as-of-invoice-date. The TPM accrual register reads the dispatch rate (not the period rate) when computing scheme accrual; the credit-note generation module reads the original invoice rate (not the credit-note issue rate) when computing Section 34 credit-note value. Build a transition-stock register at the distributor level — closing stock as on 21 September 2025 by SKU lot, procurement rate, expected onward supply rate — and feed it to the distributor's Rule 42 working pack. Reconcile the period accrual register to the trade-spend GL liability and the credit-note register to GSTR-1 outputs and GSTR-2B recipient credits.
- **Config:** HSN master with rate-effective-date field per HSN; SKU master with HSN linkage and grammage for legacy ₹100/kg working; dispatch invoice header with rate-as-of-invoice-date stamped at booking; scheme master with effective-date stack covering the 22-September-2025 cutover; transition-stock register at distributor level (closing stock 21 September 2025, procurement rate, onward supply rate); credit-note rule that reads original invoice rate; GSTR-1 amendment workflow for cross-period dispatches; DRC-03 workflow for Rule 42 ITC reversal where applicable.
- **Output:** A biscuit segment GST 2.0 reconciliation pack: pre-22-September accrual register at 12% / 18% by SKU and distributor; post-22-September accrual register at 5%; transition-stock register with Rule 42 ITC reversal computation per distributor; cross-period scheme payout register showing per-line rate at original invoice; Section 34 credit-note register split by pre- and post-22-September dispatches; GSTR-1 amendment register for cross-period corrections; GSTR-2B recipient mismatch register feeding distributor follow-ups. The pack cross-foots to the trade-spend GL liability and the output tax liability in the trial balance before each month-end close.

### Blinkit (Zomato) FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/blinkit-fmcg-settlement-reconciliation/

- **Problem:** An Indian FMCG brand selling at scale on Blinkit — typically ₹25 to ₹45 lakh of monthly dark-store invoicing for a single regional or national brand — receives Blinkit settlement files on a T+7 cycle that bundle item-level margin, listing-fee debits, BOGO scheme reimbursement claims, fill-rate penalties, return-to-vendor credit notes and Section 52 TCS withheld at the 0.5 percent notified rate into a single net bank credit. Without a per-SKU, per-dark-store reconciliation discipline, mid-market brands routinely mis-classify the supply under Section 9(5) instead of Section 9(1)/Section 52, lose the TCS credit that should land in the electronic cash ledger, and absorb 2 to 4 percent of Blinkit revenue invisibly inside mis-tagged listing-fee debits and un-recovered BOGO scheme reimbursement variance.
- **Logic:** Ingest each Blinkit settlement file daily with a Blinkit-format parser; decompose the gross invoice into seven canonical buckets — item-level margin, listing-fee debit, ad and slotting invoices (kept separate, 18 percent GST claimed as ITC), BOGO and scheme reimbursement classified by Section 15(2) treatment per scheme, fill-rate and QC penalties, return-to-vendor credit notes, and Section 52 TCS at the 0.5 percent notified rate. Per-SKU reconciliation runs at the Bhujia 200g, Soan Papdi 250g, Aloo Bhujia 150g level against the Blinkit dispatched quantity per dark store. Tag every outward supply in GSTR-1 with the Blinkit TCS-collector GSTIN. Close the three-way Section 52 TCS tie (settlement file ↔ GSTR-8 ↔ GSTR-2A). Verify each BOGO claim against the trade-promotion-management accrual register and scheme master before signing off the cycle. Apply the 22 September 2025 GST 2.0 rate-by-date table on the affected HSN list.
- **Config:** Blinkit settlement-file parser with seven-bucket deduction-taxonomy mapping; SKU master with HSN, GST rate and 22 September 2025 GST 2.0 cut-over flag per pack size; dark-store master with depot-to-dark-store dispatch register; scheme master with Section 15(2) treatment flag per BOGO/slab/listing campaign; listing-fee register per SKU per platform; ad and slotting invoice register routed to marketing GL with 18 percent ITC claim; Section 52 TCS register at the notified 0.5 percent rate (CBIC Notification 15/2024-CT); GSTR-1 outward-supply tagging rule for Blinkit-routed supplies with TCS-collector GSTIN; GSTR-8 ingestion at Blinkit GSTIN per month; GSTR-2A TCS credit reconciliation rule; bank-statement matcher for the T+7 net settlement receipt; clear Section 9(5) exclusion flag (FMCG goods on Blinkit are NOT in the deemed-supplier regime — only the four notified service categories qualify).
- **Output:** Monthly Blinkit settlement pack per brand: gross invoice per dark store per SKU, seven-bucket deduction decomposition with named-line breaks, net bank receipt tied to Blinkit payment advice on the T+7 horizon, Section 52 TCS three-way tie (settlement file, GSTR-8, GSTR-2A), GSTR-1 outward-supply tagging audit trail with Blinkit TCS-collector GSTIN, BOGO and scheme reimbursement register validated against the trade-promotion-management accrual, listing-fee variance per SKU, ad-spend invoice register with ITC posture, scheme reimbursement ageing buckets (0-30 / 31-60 / 61-90 / 90+ days), GST 2.0 rate-by-date audit log, and a leakage summary surfacing un-recovered listing-fee debits, mis-tagged ad-spend deductions and any Section 9(5) versus Section 52 treatment error before it reaches the GSTR-3B cycle close.

### Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why

Source: https://www.terra-insight.com/insights/blocked-itc-section-17-5/

- **Problem:** Section 17(5) permanently blocks ITC on motor vehicles, food and beverages, outdoor catering, club memberships, health services, LTC, and works contracts for immovable property — yet GSTR-2B auto-posts these credits alongside legitimate ones, so any unreversed claim attracts 24% interest under Section 50(3) and up to 100% penalty under Section 74.
- **Logic:** A rules engine scans every GSTR-2B row against Section 17(5) categories using HSN code, SAC code, vendor tag, and expense narration. Matches are routed to mandatory Table 4(B)(1) reversal in GSTR-3B. Statutory-canteen and goods-transport exceptions are whitelisted so eligible credit is preserved.
- **Config:** Vendor master tags for 17(5) categories (cab, catering, club, insurance, works contract), HSN/SAC block lists, and exception rules for Factories Act canteens and transport businesses.
- **Output:** Monthly blocked-ITC reversal report tied to Table 4(B)(1), a claimable-versus-blocked split of every GSTR-2B row, and an audit trail linking each reversal to the statutory clause that triggered it.

### BOGO (Buy-One-Get-One) Scheme Accounting under CGST Section 15(2) for FMCG

Source: https://www.terra-insight.com/insights/bogo-scheme-accounting-fmcg-section-15-2-gst/

- **Problem:** An FMCG brand owner runs a Buy-One-Get-One festive scheme across a 4-6 week window for biscuits, soaps or chocolates; the scheme is operationalised as a primary-sales invoice with two units at one price and a Section 15(2)(b) discount line, then claimed back by the distributor as a reimbursement; if the invoice is miscoded as a free issue the distributor's ITC is at risk under Section 17(5)(h), GSTR-1 misstates outward taxable value, the BOGO master and the invoice ledger drift apart, and the distributor claim register ages past 90 days with disputes — and from 22 September 2025 a GST 2.0 5% rate now applies to the same scheme that ran at 18% one quarter earlier.
- **Logic:** Stamp every BOGO-eligible SKU with the scheme code, scheme period, per-unit discount and qualifying invoice flag; require every BOGO-flagged invoice to carry two units, the gross unit price, the explicit discount line and the resulting net taxable value (Rule 46 disclosure); roll scheme-master eligible quantity against invoice-ledger discounted quantity at month end and against distributor claim register at scheme close; verify that no BOGO invoice has been processed as zero-rated free issue, that no Section 17(5)(h) ITC reversal has been triggered at distributor end, and that the GST rate on the invoice matches the date-of-supply rate (18% pre-22-Sept-2025, 5% on or after); age claims 0-30 / 31-60 / 61-90 / 90+ days from scheme close.
- **Config:** BOGO scheme master per scheme code (SKU list, period, per-unit discount, qualifying primary or secondary); invoice-template gate that forces two-line BOGO disclosure for any scheme-flagged invoice; Section 15(2) discount-treatment rule per scheme (invoice-recorded vs post-supply); GST rate-by-date table with the 22 September 2025 cut-over baked in; distributor claim register feed from DMS; ageing buckets 0-30 / 31-60 / 61-90 / 90+ days; cross-reconciliation rule scheme-master ↔ invoice ledger ↔ claim register at scheme close.
- **Output:** A scheme-close pack per BOGO scheme: scheme-master eligible quantity, invoice-ledger discounted quantity, distributor claim register, three-way variance with named-invoice breaks, GSTR-1 HSN-summary check at the discounted taxable value, distributor ITC posture (no Section 17(5)(h) trigger), and a claim ageing report with 60-day escalation triggers — handed to the trade-marketing and finance controllers ahead of next quarter's scheme calendar.

### Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance

Source: https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation/

- **Problem:** Booking.com bills Indian hotels for commission from its Netherlands B.V. entity in INR or EUR, making the commission an import of service that requires 18% IGST under RCM with self-invoice — while virtual-card versus collect-at-property models, Genius programme discount funding, and forex variance on EUR invoices each create separate reconciliation breakpoints not present in domestic OTA settlements.
- **Logic:** Per booking, identify payment model (virtual-card or collect-at-property), match Booking.com confirmation to PMS folio, derive room revenue at the correct GST slab (12% or 18%), book commission expense at invoice-date rupee value, raise a self-invoice for RCM 18% IGST, claim equivalent ITC, recognise forex variance separately on payment date, and split Genius discount funding between hotel and Booking.com per contract.
- **Config:** Booking.com extranet connector for confirmations and invoices; PMS folio adapter; payment-model classifier (virtual-card versus collect); RCM self-invoice generator with GSTR-3B Table 3.1(d) mapping; forex rate master with RBI reference rates; Genius discount split rule per contract.
- **Output:** A reconciled ledger where each Booking.com booking matches a PMS folio at correct GST slab, RCM IGST is paid and claimed, virtual-card MDR is captured, forex variance is recognised separately, and the GSTR-3B return correctly populates Table 3.1(d) for inward supplies under reverse charge.

### Bosch India SupplyOn Portal: Delivery Data and ASN Reconciliation for Tier-2 Suppliers

Source: https://www.terra-insight.com/insights/bosch-supplyon-portal-asn-reconciliation-india/

- **Problem:** Tier-2 suppliers to Bosch India operate inside a globally-templated commercial regime — SupplyOn as the collaboration platform with EDI 830 / 862 / 856 across both X12 and EDIFACT message families, tight CUM-accounting discipline against the Bosch CRX0 zero-defect quality programme with 10-25 PPM thresholds on safety-critical parts, and a cross-border foreign-currency exposure when Bosch India sources sub-assemblies from Bosch Germany / Hungary or the Tier-2 receives associated technical services from Bosch-side non-resident engineers. A ₹50 crore Bosch book demands SupplyOn portal-export discipline, CUM-drift exception management, CRX0-aligned PPM tracking at the tighter Bosch thresholds, Section 393(2) Sl. 17 / payment code 1057 TDS on any non-resident pay-leg, and INR / EUR FX revaluation on cross-border components.
- **Logic:** Establish daily SupplyOn portal-export discipline for delivery schedules / ASN-acknowledgements / quality notifications, run continuous CUM-shipped vs CUM-received reconciliation per part per scheduling agreement with tight tolerance band, track rolling 12-month PPM per part against CRX0-aligned thresholds (10-25 PPM safety-critical, 100-300 PPM functional-critical, 500 PPM non-critical), maintain a foreign-currency sub-ledger for any cross-border invoicing leg, register and reconcile Section 393(2) Sl. 17 / payment code 1057 TDS deductions on associated non-resident pay-leg fees under the Income Tax Act 2025 effective from 1 April 2026.
- **Config:** Bosch India customer master with sub-records per ship-to plant, SupplyOn portal export mapping for daily delivery-schedule / ASN-acknowledgement / quality-notification parsing, CUM-shipped vs CUM-received register per scheduling agreement with tolerance band, CRX0-aligned PPM threshold matrix per part with rolling 12-month window, foreign-currency sub-ledger for any cross-border invoicing leg with FX revaluation at month-end and settlement, Section 393(2) Sl. 17 / payment code 1057 register for non-resident pay-leg TDS reconciliation, Form 168A and Form 49B reconciliation calendar.
- **Output:** A daily-cadenced SupplyOn delivery-schedule and ASN reconciliation view per part per ship-to plant, CUM drift exception register with ageing and root-cause classification, rolling-PPM dashboard per part against CRX0 thresholds with breach alerts at 60% / 80% / 95% / 100%, foreign-currency sub-ledger with FX revaluation at quarter-close, and Section 393(2) Sl. 17 / payment code 1057 TDS register reconciled to Form 168A and Form 49B with quarterly cut-off action queue.

### NACH Bounce, Re-Presentation, and Successful Collection: Netting the Trail

Source: https://www.terra-insight.com/insights/bounced-debit-re-presented-collected-nbfc-reconciliation-india/

- **Problem:** A NACH debit that bounces on Day 1 and is re-presented and cleared within the T+3 window is a single successful collection event, but parallel systems — the NACH gateway, the loan-management system, and the bank collection ledger — frequently treat the Day 1 bounce and the Day 4 credit as two disconnected events. The result is a phantom over-credit to the borrower, a stale bounced-EMI flag, and a DPD register that no longer matches the collection reality.
- **Logic:** Every NACH presentation carries a unique mandate reference (UMRN) and a batch reference. A representation must inherit the same UMRN and reference the original bounce return. The reconciliation engine ingests the outward presentation file, the inward return file, the representation acknowledgement, and the bank credit, and threads them into a single bounce chain keyed by UMRN and instalment number. When the chain closes with a successful credit, the loan-management system closes one instalment and one bounce — not two.
- **Config:** NACH mandate register with UMRN, amount, frequency, and beneficiary account. Return-code family map — transient (representable) versus structural (not representable). Representation queue with T+3 windowing and per-cycle attempt limits from the sponsor bank. Bounce-chain identifier that links the outward presentation, the inward return, the representation, and the bank credit. Cure logic that reverses the DPD movement and closes the bounced-EMI flag when the chain resolves.
- **Output:** One closed instalment per bounce chain, one closed bounce per cycle, no phantom over-credit to the borrower, a DPD register that reflects the cured position on the collection date, an audit-ready evidence pack per cycle, and an ECL stage classification that is not disturbed by transient bounces cured within the reporting window.

### Brand-Channel Partner Commercial Reconciliation for D2C: Influencer, Affiliate, Reseller

Source: https://www.terra-insight.com/insights/brand-channel-partner-commercial-reconciliation-d2c-india/

- **Problem:** D2C brands acquiring customers through channel partner programmes face a fragmented commercial reconciliation problem — influencer per-post fees plus revenue-share through unique coupon codes, UTM-based affiliate commission with attribution windows and chargeback rules, authorised reseller margin plus co-branding support, each with Section 393 (commission and brokerage) or Section 393(2) (non-resident) TDS treatment and 18 percent GST on registered partner supplies, where unstructured channel-partner reconciliation absorbs 4 to 9 percent of channel-partner spend invisibly across over-paid commissions, missed chargebacks, and mis-applied TDS.
- **Logic:** Maintain a channel-partner master per partner with type (influencer, affiliate, reseller), commercial terms, TDS regime (resident or non-resident), and GST registration status. Match every order to its originating coupon code or UTM, compute commission at agreed rate, apply chargeback for returns and cancellations within window, reconcile partner invoices to computed payable, apply Section 393 or Section 393(2) TDS, and capture 18 percent GST ITC where applicable.
- **Config:** Channel-partner master with commercial terms and TDS regime, OMS order-tagging by coupon and UTM, attribution-window and chargeback-window rules per programme, affiliate-network adapter for invoice ingestion, Section 393 and Section 393(2) TDS rate-and-threshold logic, GST registration status per partner, Form 15CA and 15CB workflow for non-resident payments.
- **Output:** Reconciled channel-partner ledger per partner with commission variance versus agreed rate isolated per campaign or attribution window, chargeback correctly applied for returns within window, TDS deducted at the right regime and reported in Form 26Q or 27Q, GST ITC on registered partner invoices captured cleanly, and a board-ready cost-per-acquisition view per partner type and per campaign.

### Branded Apparel Reconciliation in India — Section 9(1) vs 9(5) Clarification

Source: https://www.terra-insight.com/insights/branded-apparel-reconciliation-india-section-9-1-vs-9-5/

- **Problem:** A pan-India branded apparel principal selling Allen Solly, Van Heusen, Pantaloons, Westside, Zudio, Reliance Trends or similar SKUs through Myntra, Ajio and Flipkart Fashion frequently misclassifies the transaction as a Section 9(5) deemed-supplier case (treating the ECO as the supplier and stopping the brand's own GST liability), when in fact apparel goods are outside the Section 9(5) notified categories and every online D2C sale remains a Section 9(1) normal supply by the brand. The consequence is a mis-filed GSTR-1 where the brand does not report the outward supply, a mis-claimed ITC where the brand does not claim the commission GST, and a mis-reconciled TCS where the brand does not claim the Section 52 credit — three separate compliance breaks from one root confusion. Layered on top: settlement file variances from ECO commission slabs, returns handling and advertising deductions eat 15 to 22 percent of the gross before the brand sees a net remittance, and returns rates of 25 to 40 percent trigger a Section 34 credit note cycle that must complete within the 30 November following FY window.
- **Logic:** Treat every online D2C apparel sale as a Section 9(1) normal supply by the brand principal. Ingest the ECO settlement file weekly or per settlement cycle. Match every settlement line to a brand tax invoice (or a batch of invoices for aggregated settlement runs). Verify the applicable GST rate against the SKU master using the per-piece ₹1,000 threshold — 5 percent for pieces at or below ₹1,000; 12 percent for pieces above ₹1,000. Reconcile the ECO Section 52 TCS on the settlement to the ECO's GSTR-8 filing (available in the brand's TCS credit statement on the GST portal). Reconcile the ECO commission GST to GSTR-2B for input tax credit. Track the returns register from the ECO and issue Section 34 credit notes within the 30 November following FY window. The reconciliation engine chains gross transaction value at the top of the settlement, deductions layer by layer (commission, returns, advertising, logistics, TCS), and net remittance at the bottom — every layer is a separate ledger leg.
- **Config:** SKU master with piece value and applicable GST rate (5 percent below or equal to ₹1,000 piece value; 12 percent above); ECO master with commission slab percentage, returns handling percentage, advertising co-invest slab, Section 52 TCS rate (currently 0.5 percent post-Notification 15/2024), settlement cycle in days (T+7 to T+21 depending on ECO), and ECO GSTIN per state; per-invoice tax invoice register; per-settlement-cycle settlement file ingestion; per-return returns register and Section 34 credit note register with the 30 November following FY window alert; TCS credit statement reconciliation against ECO GSTR-8; commission GST ITC feed into GSTR-2B reconciliation.
- **Output:** A per-settlement-cycle reconciliation pack: gross transaction value, ECO commission (with 18 percent GST), returns handling, advertising co-invest, Section 52 TCS at 0.5 percent, net remittance, and a matched brand tax invoice reference for every line. A month-end GST reconciliation view: GSTR-1 outward supply summary at 5 percent and 12 percent slabs, GSTR-2B ITC claim on ECO commission GST, GSTR-8 TCS credit reconciliation, and Section 34 credit note register with returns cycle ageing against the 30 November window. Variance flags for GSTIN mis-tag at ECO, rate-flip on discounted SKUs crossing the ₹1,000 threshold, commission slab drift, and missing TCS credit at portal reconciliation.

### Breakage and Damage Distributor Claim Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/breakage-damage-fmcg-distributor-claim/

- **Problem:** Indian FMCG cold-chain breakage and damage rarely settles cleanly to a single party. Each damaged line item must be allocated across four candidate liable parties — brand (specification fault), 3PL (cold-chain SLA breach), distributor (godown handling fault), and insurer (recovery against 3PL transit policy) — and the allocation requires four pieces of independent evidence: the distributor breakage register at receipt, the 3PL temperature data logger output, the brand QC sample test report, and the insurer claim form. Mis-allocation either burdens the wrong party with the loss, breaks the Section 34 credit-note window at 30 November, or invalidates ITC at the distributor end via Schedule I treatment failure on inter-state legs.
- **Logic:** Parse the distributor breakage register at consignment receipt — damaged units, batch, HSN, observed cause. Pull the 3PL temperature log for the corresponding trip and reconcile against the contracted cold-chain band. Pull the brand QC sample test report on the disputed batch — pass or fail against specification. Pull the insurer claim form for any line submitted under the 3PL transit policy. Apply the liability matrix: brand-liable if QC fails specification; 3PL-liable if temperature log shows SLA breach (insurance route); distributor-liable if temperature log is in band and QC passes specification but breakage is observed at the godown. Route each line to a credit-note flow (Section 34 for brand-liable), an insurance recovery flow (3PL-liable), or a distributor write-off (distributor-liable). Track ageing per line against the 30 November Section 34 cutoff.
- **Config:** Distributor master with GSTIN, PAN, godown location, cold-chain certification flag. 3PL master with contract reference, cold-chain band (per category), transit-insurance policy number, and SLA-breach penalty schedule. Insurer master with policy number, claim portal URL, and coverage limits. Scheme master flagging cold-chain SKUs (ice-cream, dairy, frozen). Per-consignment evidence pack — breakage register receipt, temperature log download, QC sample report ID, insurer claim ID. Schedule I treatment flag per inter-state credit note. Section 34 cutoff date per FY (30 November). PLISFPI-incremental flag per SKU and per state for beneficiary brands.
- **Output:** A quarterly breakage-and-damage reconciliation pack: opening damage liability, period damage observed, allocation across the four liable parties with evidence references, period Section 34 credit notes issued (with GSTR-1 amendment linkage), period 3PL recovery filed and received, period distributor write-offs, period stale claims past 30 November cutoff, and closing damage liability. Per-distributor ageing buckets. A PLISFPI-incremental netting register for the FY 2026-27 final-year claim. A Schedule I inter-state credit-note register feeding GSTR-1 amendments. An audit pack documenting each damage line's evidence trail and liability allocation rationale.

### Britannia Dairy Cheese and Curd Modern Trade Reconciliation

Source: https://www.terra-insight.com/insights/britannia-dairy-cheese-curd-modern-trade-reconciliation/

- **Problem:** A Britannia Dairy cheese and curd modern trade principal supplying large-format retailers such as DMart, Reliance Smart, and More Retail through cold-chain 3PLs must reconcile a dispatch register, the retailer's settlement file, the 3PL's temperature log, and its own Section 34 CGST credit note register — every week, at DC level and batch level. A temperature-deviation reject that arrives at a DMart back-store without a validated 3PL temperature log becomes an unresolved bad-debt candidate; a BOGO scheme rolled out without a documented pre-supply agreement fails the Section 15(3)(b) test and the discount does not exclude from the taxable value. Manual four-way reconciliation across a modern-trade portfolio of six chains, 30 DCs, 400 SKUs, and weekly settlement cycles loses batch trace and mis-matches temperature excursions to the wrong shipment.
- **Logic:** Ingest the dispatch register keyed by invoice and batch, the modern-trade retailer settlement file (daily or weekly per chain), the 3PL cold-chain temperature log per consignment, and the internal Section 34 CN register. Chain each retailer reject line back to the parent invoice and the 3PL consignment reference; overlay the temperature log for that consignment against the FSSAI storage spec (curd at or below 4°C, processed cheese per label); tag the reject as cold-chain-traceable or supplier-fault; generate a Section 34 credit note for validated rejects and adjust the output tax liability in the month-of-issue GST return. Overlay the Section 15(3) discount treatment book — every trade scheme (BOGO, MRP-off, target-linked) tagged as pre-supply-agreement documented (Yes/No) and ITC-reversal confirmed at recipient level (Yes/No).
- **Config:** Modern-trade retailer master with GSTIN, DC codes, settlement cycle (daily/weekly/fortnightly), and rejection reason-code taxonomy; SKU master with pack size, MRP, HSN, FSSAI storage class (chilled/ambient); 3PL master with GSTIN, TDS payment code (1002 for corporate, 1001 for Ind/HUF), reefer-truck registration, and temperature-log feed format; scheme master with scheme ID, effective dates, pre-supply-agreement document reference, discount treatment (Section 15(3)(a) invoice-level or Section 15(3)(b) post-supply); Section 34 credit note register with reason code (return/deficient/price adjustment) and month-of-issue against the statutory 30 November deadline; TDS deduction schedule for 3PL invoices under code 1002 at 2 percent.
- **Output:** A weekly modern-trade reconciliation pack per retailer chain: invoices dispatched, invoices settled, retailer rejects with 3PL temperature-log overlay, Section 34 credit notes issued in the week, scheme discount treatments logged against Section 15(3) with ITC-reversal status per distributor. A Section 34 credit note ageing report against the 30 November following-FY statutory deadline. A 3PL cold-chain excursion trend by lane and by consignment. A scheme discount register with pre-supply-agreement documentation status flagged red where the agreement predates the supply is not on file. TDS reconciliation on 3PL invoices under code 1002 against Form 26AS at the 3PL PAN level.

### Bulk Drug Park + PLI: The 53 Critical APIs Reconciliation

Source: https://www.terra-insight.com/insights/bulk-drug-park-scheme-pli-53-critical-apis-reconciliation/

- **Problem:** A Tier-2 bulk-drug API manufacturer building a Rs 550 crore Kakinada facility inside the Andhra Pradesh notified bulk-drug park under the parallel DoP Bulk Drug Park scheme must reconcile the PLI Bulk Drug Rs 6,940 crore claim against a molecule master of illustratively three of the 53 critical APIs — Penicillin G, Cephalosporin intermediates and 7-Aminocephalosporanic Acid, all fermentation-based Category A molecules at the 20 percent incentive rate for Years 1 through 4. Simultaneously the applicant must document the mutually exclusive election against the parallel PLI Pharma Rs 15,000 crore Category 2 KSM claim (a Category 2 applicant cannot double-dip on the same molecule), track the capex-vs-milestone matrix against the DoP-set land-allotment / civil-construction / commissioning / commercial-production milestone dates, and reconcile the Andhra Pradesh bulk-drug-park land allotment register with the plot lease terms modelled under Ind AS 116. Each surface is a distinct reconciliation and a break on any one surface — a mis-classified molecule (Category A vs Category B), a missed capex milestone, a duplicated PLI Pharma Category 2 claim on the same molecule, an unreconciled park land-allotment plot record — breaks the annual disbursement cycle.
- **Logic:** Build a molecule master keyed to the DoP 53-critical-APIs list with each molecule tagged Category A (fermentation-based, 20 percent Years 1-4) or Category B (chemical-synthesis-based, 5 percent Years 1-4), the per-molecule per-applicant maximum incentive cap, and the mutually exclusive election flag against PLI Pharma Category 2. Build a capex-milestone matrix per selected molecule with committed capex, capex incurred to date, capex milestone dates (land allotment / civil / equipment / commissioning / commercial production), and the incentive-year eligibility trigger tied to milestone achievement. Ingest the applicant's monthly sales register from the ERP filtered to the DoP-approved molecule list and apply the Category A or Category B incentive rate against sales value (not incremental sales) with the per-molecule cap binding. Track the Andhra Pradesh (or Himachal Pradesh or Gujarat) notified bulk-drug-park land-allotment register with the plot number, allotment date, lease term and lease-payment schedule modelled under Ind AS 116. Compute the Ind AS 20 grant recognition entry with the presentation choice (other income vs net-of-expense), the Section 115JB MAT book-profit adjustment on the grant leg, and the Section 115BAA vs normal-regime trade-off against any Section 35(2AB) R&D weighted deduction on the fermentation-strain-development pipeline. Generate the DoP portal annual claim workbook per molecule per applicant with the statutory auditor certificate template.
- **Config:** Molecule master keyed to the DoP 53-critical-APIs list with Category A / Category B tag, per-molecule maximum incentive cap, mutually exclusive election flag against PLI Pharma Category 2 (per molecule); capex-milestone matrix per selected molecule with committed capex, capex incurred, milestone dates (land / civil / equipment / commissioning / commercial production), incentive-year eligibility trigger; ERP material-code mapping to DoP molecule list (SAP material master, Oracle item master); monthly sales-value register per molecule at the applicable Category A or Category B rate; per-molecule cap binding logic and excess-incentive-foregone tracking; Andhra Pradesh / Himachal Pradesh / Gujarat notified bulk-drug-park land-allotment register with plot number, allotment date, lease term, Ind AS 116 lease liability and right-of-use asset; Ind AS 20 grant recognition template with grants-related-to-income presentation choice; Section 115JB MAT book-profit adjustment schedule; Section 115BAA opt-in flag with the trade-off model against Section 35(2AB) forfeiture on the fermentation-strain-development R&D pipeline; DoP annual claim workbook filing calendar with the statutory auditor certificate template.
- **Output:** An annual PLI Bulk Drug claim pack per selected applicant per molecule: the molecule master with Category A / B classification and mutually exclusive election flag, the capex-milestone matrix with the achievement status for the year, the sales-value register with the incentive computation at 20 percent Category A or 5 percent Category B against the per-molecule cap, the excess-incentive foregone quantified, the Andhra Pradesh notified bulk-drug-park land-allotment plot register with the Ind AS 116 lease disclosure, the DoP annual claim workbook filing template, the statutory auditor certificate schedule, and the accounting entry pack showing PLI grant receivable, other income (or net-of-expense presentation), the Section 115JB MAT book-profit adjustment, and any Section 92BA specified-domestic-transaction disclosure on intra-group transfer of the identified molecule to a downstream Chapter 30 formulator sister entity. The four-year (Years 1 through 4) scheme window forecast rolls the year-by-year approved incentive into the applicant's treasury and Ind AS 20 grant recognition schedule.

### Bullion (B2B) vs Retail (B2C) Jewellery Supply Classification

Source: https://www.terra-insight.com/insights/bullion-vs-retail-gst-supply-classification-jewellery-india/

- **Problem:** A jewellery group running both a bullion wholesale arm supplying other jewellers and refiners and a retail arm selling to walk-in and online customers must classify every outward supply as B2B, B2C-large, or B2C-small before invoice ingestion. B2B supplies (any registered recipient with a verified GSTIN) go to GSTR-1 Table 4 invoice-by-invoice with recipient GSTIN. B2C-large supplies (inter-state, unregistered recipient, invoice value > ₹2.5 lakh) go to Table 5 invoice-by-invoice with place of supply. B2C-small supplies (everything else) go to Table 7 as a state-wise consolidated summary. Rule 46r QR code applies to B2C invoices if the entity's aggregate turnover exceeded ₹500 crore. Section 269ST prohibits cash receipts of ₹2 lakh or more per transaction. Section 25(4)/(5) distinct-person rules govern intra-group bullion-to-retail transfers. Mis-classification collapses recipient ITC availability, breaks place-of-supply detail, and invites a Section 74 audit notice.
- **Logic:** Build a supply-type classifier that runs at invoice ingestion — capture recipient GSTIN (if any) and verify against the GSTN portal, capture place of supply from the recipient address, capture invoice value and payment mode, and apply the three-question sequence: is the recipient GSTIN-verified? (B2B, Table 4) → is the supply inter-state with invoice value > ₹2.5 lakh? (B2C-large, Table 5) → default B2C-small (Table 7). Attach the dynamic QR under Rule 46r if the entity's aggregate turnover in any preceding FY from 2017-18 exceeded ₹500 crore and the supply is B2C. Flag cash receipts above ₹2 lakh for Section 269ST review before invoice acceptance. For intra-group bullion-to-retail transfers between distinct persons (different state GSTINs), value at OMV or 90% of retail price under Rule 28, charge IGST, and file in Table 4 with the recipient GSTIN of the retail arm. Reconcile the outward Table 4 supply to the inward supply captured in the retail arm's GSTR-2B.
- **Config:** Customer master with GSTIN field (verified against GSTN portal), PAN field (mandatory above ₹2 lakh under Rule 114B), state and place-of-supply capture, and a supply-type flag (B2B / B2C-large / B2C-small / distinct-person intra-group); item master with HSN 7108 (bullion, unwrought) or HSN 7113 (finished jewellery) and 3% rate flag; store master with registration GSTIN per state; entity aggregate turnover flag at group level for Rule 46r QR trigger; payment-mode master with Section 269ST enforcement at invoice acceptance; open-market-value reference for intra-group transfers under Rule 28; wholesale-to-retail spread capture for gross-margin reconciliation; e-invoicing IRN QR code integration under Rule 48(4) for B2B supplies where the entity crosses the e-invoicing turnover threshold.
- **Output:** A monthly GSTR-1 filing pack: Table 4 B2B supplies invoice-by-invoice with recipient GSTIN and place of supply; Table 5 B2C-large supplies invoice-by-invoice with place of supply for inter-state invoices above ₹2.5 lakh; Table 7 B2C-small supplies as a state-wise consolidated summary at the tax-rate level; distinct-person intra-group transfers reconciled between the outward Table 4 of the supplying GSTIN and the inward GSTR-2B of the receiving GSTIN; Section 269ST exception list for any cash receipts above ₹2 lakh flagged for finance review; Rule 46r QR code audit trail for B2C invoices at group entities above ₹500 crore turnover; PAN capture reconciliation under Rule 114B for all invoices above ₹2 lakh; wholesale-to-retail margin reconciliation at the SKU level.

### Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns

Source: https://www.terra-insight.com/insights/busy-software-reconciliation-india/

- **Problem:** Busy Accounting Software (dominant among Indian trading, wholesale, and CA-firm segments) runs on DBF tables or proprietary indexed binary (Busy 21+) with no sanctioned real-time API — so CA firms managing 20+ client companies on Busy cannot reconcile bank, TDS, and GSTR-2B across entities without an overnight ASCII/XML batch job.
- **Logic:** Run scheduled ASCII or XML exports from each Busy company directory at end of day, drop files over SFTP to a central location, ingest into an external reconciliation layer that handles multi-company bank, TDS, and GSTR-2B matching, resolve exceptions outside Busy, and post cleared status back via ASCII import. GSTR-2B JSON from the GST portal is consumed externally and matched against the Busy purchase voucher extract.
- **Config:** Busy company directory registry, ASCII and XML export templates aligned to Busy schemas (MASTERS.DBF, VOUCHERS.DBF, GSTINFO.DBF), SFTP job scheduler at EOD, CA-firm client mapping for multi-company consolidation, and ASCII import writeback for cleared voucher status.
- **Output:** A CA-firm or multi-branch trading house running 20+ Busy companies reconciled overnight across bank, TDS, and GSTR-2B streams — GSTIN typo and timing-mismatch exceptions handled externally, cleared status pushed back to each Busy company, and consolidated audit trail available at partner review.

### CA Firm Client Due Diligence and AML Compliance under PMLA

Source: https://www.terra-insight.com/insights/ca-firm-client-due-diligence-aml-india/

- **Problem:** After the Ministry of Finance notification dated 3 May 2023, an Indian CA firm onboarding 80 new clients a year is a reporting entity under PMLA whenever it carries out any of five specified financial activities on a client's behalf — and must run customer due diligence, risk-classify every client, file STRs and CTRs with FIU-IND within 7 working days of suspicion, and retain records for 5 years after engagement closure, with tipping-off itself a criminal offence.
- **Logic:** Operate a three-tier process: a PMLA trigger checklist at engagement intake to decide whether the firm becomes a reporting entity for that client; a risk-classification matrix (Low/Medium/High) that drives standard CDD or Enhanced Due Diligence with PEP screening and source-of-funds review; and a continuous-monitoring loop that surfaces STR/CTR triggers from the firm's reconciliation and ledger workflows. The Principal Officer files with FIU-IND via FINnet 2.0 and locks all records under a 5-year retention vault.
- **Config:** Engagement intake form mapping the five specified activities; PEP and sanctions screening at onboarding; Beneficial Owner threshold of 10% (25% for trusts); EDD memo template for High-risk and PEP-linked clients; STR/CTR red-flag rubric tied to reconciliation outputs; FIU-IND FINnet 2.0 Principal Officer credentials; 5-year retention vault keyed to engagement closure date.
- **Output:** Every client on the firm's book has a documented PMLA assessment on file, risk-classified with rationale, EDD memos where required, an audit trail of ongoing monitoring, STRs filed within 7 working days of suspicion, and full 5-year retention — no FIU-IND enforcement gaps, no Section 13 tipping-off exposure, and a defensible position if the firm itself is examined.

### CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle

Source: https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india/

- **Problem:** A CA firm running outsourced compliance for 80 enterprise clients executes 80 parallel monthly cycles on a shared statutory calendar — onboarding, pulls on the 1st, matching by the 10th, filing by the 20th — and any gap in role allocation, SA 230 evidence capture, or exception triage at scale cascades into missed TDS and GST deadlines across multiple clients.
- **Logic:** Operate a three-role workflow — article clerk for data pulls and first-pass matching, manager for exception review, partner for sign-off — enforced by access control. Anchor the cycle to statutory dates: 1st–5th pulls, 6th–10th matching, 11th–13th exception triage, 14th–18th GSTR-3B prep, 19th–20th filing. Archive source data and audit trail for 7 years to satisfy SA 230.
- **Config:** Batch calendar keyed to statutory due dates, onboarding checklist template (engagement letter, GSTINs, TAN, bank list, Tally backup, COA mapping), exception classification rubric (vendor error, client error, timing, data quality), deliverable pack template (15–50 pages per client), and 7-year archival retention on source JSON/Excel.
- **Output:** A predictable 80-client monthly cycle closed on the 20th with all clients filed, SA 230 working papers archived per client, exception registers signed off by partners, and branded deliverables issued to each client — no missed deadlines, no ICAI documentation gaps.

### GST Monthly Compliance for CA Firms: GSTR-1/3B/9 Workflow at Scale

Source: https://www.terra-insight.com/insights/ca-firm-gst-monthly-compliance-india/

- **Problem:** A CA firm running GST compliance for 180 clients executes the same five-date monthly cadence in parallel — GSTR-1 by the 11th, IFF by the 13th, GSTR-2B from the 14th, GSTR-3B by the 20th, 22nd or 24th depending on state group — and any slippage in 2B-versus-books reconciliation, late-fee tracking or staff allocation across the peak 18th-to-20th window cascades into Section 47 late fee and Section 50 interest exposure across multiple clients at once.
- **Logic:** Anchor the calendar to statutory due dates and segment the book by filing regime (monthly QRMP-out versus quarterly QRMP-in) and by state group (Group A 22nd versus Group B 24th). Run 2B-versus-books matching on supplier GSTIN, invoice number, invoice date and taxable value with Rule 36(4) and Section 16(4) gates. Maintain a late-fee tracker computing Section 47 fee and Section 50 interest per missed filing. Run the annual GSTR-9 and GSTR-9C cycle from October to December alongside the monthly book.
- **Config:** Client master tagged with filing regime, state group, aggregate turnover band and GSTR-9C applicability; 2B reconciliation rules with four exception buckets; late-fee tracker keyed to Section 47 and Section 50; deadline-slot allocation by clerk to spread the 18th-to-20th peak; engagement letter clause that recovers client-caused late fees and interest.
- **Output:** A predictable 180-client monthly cycle with GSTR-1 and IFF filed by the 13th, 2B reconciliation closed by the 17th, GSTR-3B filed by the 20th, 22nd or 24th per state group, late-fee and interest exposure tracked per client, and the annual GSTR-9 and GSTR-9C pack closed by 31 December — without missed deadlines or unrecovered late fees.

### CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients

Source: https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india/

- **Problem:** A CA firm servicing 80 clients with an average of 2.5 GSTINs each faces 200 portal logins every month to pull GSTR-2B, plus 8,000–40,000 ITC line items to match against purchase registers — and IMS enforcement from January 2025 adds an accept/reject triage stage before GSTR-3B filing, multiplying the manual load.
- **Logic:** Run a batch monthly cycle: automated GSTR-2B pulls across every client GSTIN, per-GSTIN isolation of invoice data, IMS status integrated into the purchase register match, Rule 36(4) eligibility flags, and a DRC-01C pre-trigger alert when GSTR-3B ITC is about to exceed GSTR-2B beyond threshold. Exceptions feed an article-clerk queue reviewed by partner before GSTR-3B filing.
- **Config:** Per-client GSTIN master with state-wise registrations, IMS action routing rules (accept/reject/pending defaults by vendor category), DRC-01B and DRC-01C threshold alerts, and a batch calendar engine keyed to the 11th and 20th of the month for GSTR-1 and GSTR-3B filing.
- **Output:** All 50+ client GSTRs reconciled in 6–12 hours of exception review per month instead of 4–6 working days of manual work, zero post-filing DRC-01C surprises, and an audit trail per GSTIN per month that satisfies ICAI working paper standards.

### ICAI CPE Hours and Uniform Compliance for Practising CAs

Source: https://www.terra-insight.com/insights/ca-firm-icai-cpe-uniform-india/

- **Problem:** A 6-partner CA firm with 12 paid assistants and articled clerks must simultaneously satisfy three ICAI compliance tracks — 120-hour rolling CPE blocks per COP-holding member with a structured minimum, annual MEF empanelment across multiple audit categories, and the uniform charges scale from 2026 — without missing the 31 December CPE cutoff or the late-September MEF window.
- **Logic:** Operate three parallel calendars. CPE track: budget 40 hours per COP partner per year (30 structured plus 10 unstructured) and reconcile monthly against the ICAI SSP portal. MEF track: pre-fill the firm-level data block in August, lock partner experience records, submit by mid-September, monitor PDC cut-off publication. Uniform charges track: align engagement letter floor to the recommended scale, document deviations in writing.
- **Config:** Per-member CPE register (target hours, logged hours, POU source, certificate URL), MEF master file with partner experience records, engagement letter template aligned to the recommended fee scale, central calendar with 30 November CPE buffer date and mid-September MEF submission target, quarterly reconciliation against ICAI SSP.
- **Output:** Every COP-holding partner closes the rolling block with at least 120 hours including 60 structured, MEF submitted in window with empanelment ranks confirmed for the four target categories (bank statutory, bank concurrent, PSU, cooperative), and engagement letters issued at or above the recommended fee scale with documented deviations on file.

### CA Firm Pricing and Engagement Letters: India Practice

Source: https://www.terra-insight.com/insights/ca-firm-pricing-engagement-letter-india/

- **Problem:** A mid-sized Indian CA firm running mixed statutory audit, tax audit, GST, and outsourced reconciliation work for 280 clients has no consistent fee grid, prices engagements partner-by-partner, lets retainer scope absorb project work, and uses one-page engagement letters that lack scope-creep, indemnity, and TDS-on-fees clauses — producing realisation gaps, scope leakage, and Section 194J reconciliation disputes at year end.
- **Logic:** Anchor every engagement to a published internal fee grid that references the ICAI Minimum Recommended Scale of Fees by service and city class. Separate retainer scope from project scope in the engagement letter with distinct inclusions lists, fee schedules, and sign-offs. Add three scope clauses (inclusions and exclusions, change-order with hourly rate card, record-state with re-work fee), a liability cap equal to fees received with fraud carve-outs, and an explicit TDS u/s 194J clause naming the 2026 payment-code nomenclature and reconciliation cadence.
- **Config:** Internal fee grid keyed to service type and city class, engagement letter template with separate retainer and project sections, scope inclusions and exclusions list per service line, hourly rate card for change-orders by grade (article, manager, partner), liability cap clause, DPDP Act 2023 data clause, TDS u/s 194J clause with firm PAN and GSTIN, monthly Form 26AS to TDS receivable reconciliation.
- **Output:** Engagement letters that bill predictably across 280 clients with no silent scope absorption, realisation tracking by retainer and project line, year-end TDS receivable reconciled to Form 26AS within one percent, and a documented scope-change history per client that supports partner-level realisation review and fee revisions at renewal.

### Statutory Audit Execution in CA Firms: Working Paper Templates and Documentation

Source: https://www.terra-insight.com/insights/ca-firm-statutory-audit-execution-india/

- **Problem:** A CA firm running 30 to 80 statutory audits in a financial year must execute each engagement under the full SA 200 to SA 720 standards architecture, produce a defensible working paper file for every audit, retain those files for 7 years under SQC 1, and stand ready for ICAI peer review every 3 to 5 years — and any thin file, missing risk assessment, or undated workpaper exposes the partner to disciplinary risk.
- **Logic:** Standardise a 12 to 18 template working paper file mapped to each SA, anchor planning in a documented risk assessment (SA 315) with materiality (SA 320), execute substantive testing through sampling memos (SA 530) and lead schedules, capture audit evidence under SA 500, archive every workpaper dated and cross-referenced for 7-year retention under SQC 1, and run an internal mock peer review every 36 months to identify and close gaps before the ICAI review.
- **Config:** Engagement file template library covering all 12 to 18 workpaper types, materiality formula (typically 0.5 to 1 percent of revenue or 5 to 10 percent of profit before tax), sampling rubric (monetary unit or attribute sampling per SA 530), audit programme keyed to financial statement assertions, partner review checklist with sign-off points, and a controlled electronic archive with 7-year retention plus version history.
- **Output:** A complete, defensible statutory audit file per engagement — engagement letter through signed audit opinion — with full SA 200 to SA 720 evidence trail, partner sign-off at every gate, 7-year SQC 1 archival in place, and the firm passing ICAI peer review without observations on documentation or evidence quality.

### Tax Audit (Form 3CD) Mandate Management for CA Firms

Source: https://www.terra-insight.com/insights/ca-firm-tax-audit-3cd-mandate-india/

- **Problem:** A four-partner CA firm signing 38 tax audit mandates under Section 44AB faces a non-negotiable 30 September deadline, 44 Form 3CD clauses per mandate, the new TDS payment-code regime (codes 1001 to 1092) embedded in Clause 34, a Clause 26 Section 43B reconciliation that requires actual payment evidence, and Section 271B penalty exposure of 0.5% of client turnover (capped at ₹1.5 lakh) if any mandate slips.
- **Logic:** Slot every mandate onto a three-slab Gantt (July to mid-August data collection, mid-August to mid-September field work, mid-September to 30 September sign-off and UDIN), cap intake at partner sign-off capacity, run a uniform 26AS/AIS/TIS reconciliation in parallel as Clause 27 evidence, and automate Clause 34 TDS verification against the new payment-code rate table so the partner only reviews exceptions.
- **Config:** Mandate calendar keyed to 30 September with a 5-day buffer, staffing rule of 1 article clerk per 3 to 4 mandates plus 1 manager per 8 to 10, Clause 34 rule set mapped to payment codes 1001 to 1092 and the rate-by-date table, 26AS/AIS/TIS variance register template, and Section 43B payment-evidence tracker covering GST, PF, ESI, gratuity, and bonus.
- **Output:** All 38 mandates signed and Form 3CD filed by 25 September with a 5-day buffer for ICAI portal failures, UDINs generated, 26AS/AIS/TIS variance registers archived under SA 230 for 7 years, zero Section 271B exposure, and Clause 34 TDS verification reduced from a clerk-week per mandate to partner-exception review only.

### CA Firm Workflow Automation: Practice Management Systems for India

Source: https://www.terra-insight.com/insights/ca-firm-workflow-automation-india/

- **Problem:** A 6-partner CA firm with 420 clients runs more than 7,000 statutory tasks every month against a shared Income Tax and GST calendar. Manual coordination through email, spreadsheets, and WhatsApp creates document gaps, missed task assignments, partner sign-off bottlenecks, and missed TDS or GST deadlines that cascade into client penalties and ICAI documentation gaps under SA 230.
- **Logic:** Adopt a four-layer practice automation stack — client portal for document intake, document workflow for classification and storage, task tracker keyed to statutory due dates, and statutory filing integration for TDS, GST, and ROC. Compare TaxbasePro, ClearTax Pro, Computax, and Webtel on module coverage and integrations, then pair the chosen platform with a reconciliation layer that maps TDS payment codes 1001 to 1092, Section 393, Section 394, Section 393(2), and Section 194J flows automatically.
- **Config:** Practice management platform with client portal, document workflow, task tracker, and TDS or GST filing modules; statutory calendar template per client GSTIN and TAN; vendor master mapped to TDS payment codes 1001 to 1092 and Section 194J rates; role-based access for article clerk, manager, and partner; ICAI SA 230 archival retention of 7 years on source data, matched output, exception register, and sign-off trail.
- **Output:** A predictable monthly rhythm where 420 clients close on the 20th with all TDS and GST filings done, partner sign-offs captured in the platform, ICAI working papers archived per client, and 35 to 50 percent reduction in article-clerk coordination hours released for value-added advisory work.

### Cancelled Flat Resold to New Buyer: Reconciliation and Reversal

Source: https://www.terra-insight.com/insights/cancelled-flat-resold-reconciliation-real-estate-india/

- **Problem:** A registered real estate project in India experiences a booking cancellation and resale — one unit that was booked, part-paid, cancelled with earnest money forfeited, and then resold to a fresh buyer at a possibly different consideration. The event must reconcile simultaneously across four rails: a Section 34 CGST credit note to the cancelled buyer, a fresh tax invoice to the new buyer at the current under-construction rate (5% or 1% affordable), a Form 26QB rectification filed by the cancelled buyer (with the corresponding Form 26AS credit reversed in the developer's account), and a RERA Form 3 quarterly disclosure showing the unit's status change with matching escrow account debits and credits.
- **Logic:** Trigger the cancellation as a single reconciliation event that fans out: (1) issue Section 34 credit note in GSTR-1 of issuance month, ≤ 30 November following FY, at the original supply rate; (2) raise a separate 18% GST invoice on the forfeited earnest money per Section 15(2) tolerating-an-act treatment; (3) request the cancelled buyer to file Form 26QB rectification via TIN-NSDL, track the Form 26AS reversal; (4) refund the balance to the cancelled buyer from the escrow account (net of forfeiture); (5) sweep forfeiture-income to the 30% account; (6) create a fresh booking for the new buyer, raise fresh tax invoice at current rate, collect fresh 1% TDS via new Form 26QB filed by the new buyer; (7) update the RERA Form 3 unit-status register for the quarter with both the cancellation and the resale entries reconciled to escrow movements.
- **Config:** Unit master keyed by unit ID with booking-status history (booked → cancelled → resold); GST credit note register linked to original invoice number and cancellation date; forfeiture-income ledger separate from principal collection ledger; escrow bank statement ingestion for automated matching of refund debits and fresh-buyer credits; Form 26AS integration per buyer PAN for tracking 26QB rectification reversal; RERA state-cadence calendar (MahaRERA monthly, UP-RERA quarterly) driving Form 3 unit-status snapshot generation; policy master for state-specific cancellation-percentage caps where regulators have imposed limits on forfeiture.
- **Output:** A cancellation-and-resale reconciliation packet per unit showing: original booking evidence, cancellation trigger date and reason, Section 34 credit note number and GSTR-1 filing month, forfeiture invoice with 18% GST if applicable, escrow refund voucher with beneficiary PAN, Form 26AS pre- and post-rectification snapshots for the cancelled buyer, fresh-buyer booking evidence, fresh tax invoice at current rate, fresh Form 26QB filed by new buyer, and the RERA Form 3 unit-status snapshot for the quarter — all tied to a single unit ID with an audit trail that survives a RERA inspection or a GST 2A/2B reconciliation query.

### CAM (Common Area Maintenance) GST 18% Above ₹7,500/mo Threshold

Source: https://www.terra-insight.com/insights/cam-common-area-maintenance-real-estate-gst-7500-threshold-india/

- **Problem:** A post-possession residential complex managed by an RWA or CHS collects monthly Common Area Maintenance charges from each unit — the exemption under Notification 12/2017-CTR Sl. No. 77 applies up to ₹7,500 per month per member, but the moment a member's CAM crosses ₹7,500 GST at 18% applies on the full amount (not just the excess) per Circular 109/28/2019-GST, and if the RWA's aggregate turnover exceeds ₹20 lakh under Section 22 registration is triggered independently — creating a mixed-tariff complex where some units are exempt, others fully taxable, and taxable supply heads (transfer charges, guest charges, late interest) run parallel to the CAM exemption test.
- **Logic:** Maintain a per-unit CAM register with tariff, monthly CAM, and threshold flag; evaluate the ₹7,500 test at the unit level every month and classify as exempt or taxable-18%; aggregate to RWA-level turnover for the Section 22 ₹20 lakh registration test; segregate transfer charges, guest charges, late-payment interest and non-CAM services as separately taxable heads; apply Rule 42 ITC apportionment where taxable and exempt output coexist; reconcile per-unit invoice register to aggregate GSTR-1 exempt-vs-taxable split monthly.
- **Config:** Unit master keyed by flat/apartment number with owner, tariff category, monthly CAM amount, threshold flag (above/below ₹7,500); GST registration status of RWA (registered from month X); Notification 12/2017-CTR Sl. 77 exemption logic (per-member per-month ₹7,500 cliff, full-amount taxation above); Circular 109/28/2019-GST reference in the audit trail; Rule 42 ITC apportionment ratio calculator; separately-taxable head classifier for transfer/guest/interest charges; GSTR-1 exempt-vs-taxable HSN split for reporting.
- **Output:** A monthly per-unit CAM invoice register with exempt or taxable flag, GST amount computed at 18% for units above ₹7,500, transfer/guest/interest heads separately taxed; aggregate RWA-level GSTR-1 filing pack with exempt supply and taxable supply split by HSN; Rule 42 ITC apportionment worksheet with taxable-turnover-ratio and reversed ITC in GSTR-3B; audit-ready evidence of threshold-management with tariff-revision alerts before crossings; annual GSTR-9C reconciliation tying CAM register total to GSTR-1 reported turnover.

### Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing

Source: https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india/

- **Problem:** Indian steel and metal manufacturers operating a captive power plant must reconcile a coal procurement ledger (5% GST + ₹400/tonne cess where applicable) feeding a separately-metered generation log, allocate CPP cost on a metered kWh basis to multiple consuming units (sponge iron kiln, blast furnace, rolling mill), navigate the exempt-supply status of electricity under entry 1 of Notification 2/2017 and the consequent Section 17(2) ITC apportionment where the CPP partially exports to grid, layer state electricity duty / cross-subsidy surcharge / wheeling charges from the SERC tariff order, and roll the per-kWh CPP cost into the finished steel costing ledger.
- **Logic:** Run the CPP as a discrete cost centre with its own coal vendor ledger, fuel consumption log, generation log in kWh, manpower roster, depreciation schedule and operating overhead; reconcile coal GRN → coal invoice → GSTR-2B entry monthly; tag every generated kWh by consuming destination (own taxable manufacturing, exempt grid export, inter-unit transfer); apply Section 17(2) apportionment to coal and capex ITC where exempt destination exists; lift cross-subsidy surcharge and electricity duty from the SERC tariff order monthly; allocate net CPP cost on metered kWh basis to consuming units; tie the allocation file back to the finished steel costing ledger with zero unallocated residual.
- **Config:** CPP cost centre with coal vendor master, fuel ledger and GSTR-2B match; per-kWh generation log keyed to consuming unit destination tag (own taxable / grid export / inter-unit); Section 17(2) ITC apportionment formula driven by destination split; state-specific electricity duty and cross-subsidy surcharge rate map updated against the latest SERC tariff order; manpower and depreciation roster for CPP fixed overhead; monthly allocation file with metered kWh per consuming unit; cost roll-up trigger into finished steel costing ledger.
- **Output:** A monthly CPP close where coal procurement ties to GSTR-2B, fuel consumption ties to generation, generation kWh ties to consuming-unit allocation with zero unallocated residual, Section 17(2) ITC reversal is computed where exempt destination exists, state electricity duty and cross-subsidy surcharge tie to DISCOM invoice, and per-kWh CPP cost rolls cleanly into the finished steel costing ledger.

### Car Parking Charges in Real Estate: GST Treatment as Composite Supply

Source: https://www.terra-insight.com/insights/car-parking-charges-real-estate-gst-treatment-india/

- **Problem:** Indian residential developers bundling car parking with an under-construction flat sale must classify the parking as a composite supply under Section 8 of the CGST Act 2017 and tax the whole consideration at the principal supply's rate (5% CGST non-affordable, 1% CGST affordable under Notification 3/2019-CTR effective 1 April 2019). The moment the parking is unbundled — sold post-CC to the same buyer, or standalone to any buyer — the treatment flips to 18% GST under SAC 9973 as clarified for commercial parking by CBIC Circular 177/09/2022-GST. Misclassifying parking as a separate 18% line on an under-construction sale overcollects from the buyer without ITC recovery; treating a post-CC parking sale as a residual 5% line undercollects and exposes the developer to Section 50 interest and Section 73/74 penalty.
- **Logic:** Reconcile every car parking allocation to a customer-unit contract and classify at contract-signing whether the parking is a composite supply bundled with an under-construction flat (rate follows principal supply) or a standalone post-CC sale (18% SAC 9973). Tie the sale-deed line-item view (parking called out separately for stamp-duty purposes) to the GST invoice view (aggregated composite consideration at the principal supply's rate) via a composite-supply classification register. Recompute the classification if the parking sale-agreement date crosses the completion-certificate date.
- **Config:** Customer-unit master keyed by RERA registration number × unit number with associated parking-bay ID, flat consideration, parking consideration, sale-agreement date, completion-certificate date; composite-supply classification register with contract-level flag (composite-under-construction / standalone-post-CC), applicable GST rate (5%/1%/18%), SAC code, and reconciliation view mapping sale-deed line-items to GST invoice aggregation; project master with CC issuance date per phase; classification exception register for parking sold to a different buyer than the flat allotee.
- **Output:** A per-customer-unit classification record showing flat rate, parking rate, composite treatment or standalone treatment, applicable notification, and sale-deed to GST-invoice tie-back; a monthly exception report flagging any parking billed at a rate different from the flat's rate for classification review; an audit-ready evidence pack per customer-unit linking the sale deed, the GST invoice, the composite-supply classification decision, and the CC-date reference.

### CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies

Source: https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india/

- **Problem:** Companies with working capital above ₹5 crore must demonstrate quarterly BRS agreement with bank statements under CARO 2020. Unreconciled items constitute a reportable material weakness.
- **Logic:** Generate quarterly BRS per CARO 2020 Clause 3(ii)(b). Match against Section 143(3)(i) internal controls framework. Flag items exceeding auditor-defined aging thresholds. Cross-reference bank inflows against GSTR-1 declared turnover.
- **Config:** CARO threshold: working capital above ₹5 crore. DBCP portal for digitally signed confirmations (Canara, PNB, BoM, UCO). Form 3CD → Form 26 under new Act with Clauses 49-51.
- **Output:** Audit-ready quarterly BRS, material weakness assessment, DBCP confirmation reconciliation, and turnover-to-bank-inflow cross-reference for GST scrutiny readiness.

### CARO 2020 Reporting Companion: Clause-by-Clause Audit Procedures for Indian Auditors

Source: https://www.terra-insight.com/insights/caro-2020-reporting-companion-india/

- **Problem:** CARO 2020 (Order S.O. 849(E)) requires statutory auditors to report on 21 substantive clauses covering fixed assets, inventory, loans, statutory dues, fraud, borrowing end-use and auditor resignation. Most CARO qualifications trace to weak evidence in clauses (vii) statutory dues, (ix) borrowings, (xi) fraud and (xviii) resignation — areas where ledger-to-portal and ledger-to-bank reconciliation drives the conclusion.
- **Logic:** Each clause is mapped to a working paper template with three columns: assertion under audit, evidence source, and conclusion language. Clause (vii) draws on GST/TDS/PF/ESI reconciliations between liability ledger, challan, portal acknowledgement and bank statement. Clause (ix) draws on lender confirmations, sanction letters and disbursement-to-end-use mapping. Clause (xi) draws on the fraud register, ADT-4 filings and whistle-blower log. Clause (xviii) draws on Form ADT-3 and the outgoing auditor's communication.
- **Config:** CARO 2020 working paper pack with 21 clause-specific templates, evidence-vault links to underlying reconciliations, materiality thresholds (₹1 crore for ADT-4, six months for statutory dues arrears), and pre-defined conclusion language for clean, qualified and adverse reporting.
- **Output:** CARO 2020 annexure ready for attachment to the main audit report under Section 143(11), clause-wise evidence trail accessible during peer review and ICAI quality review, and a deficiency log feeding the next year's planning memorandum.

### Cash Flow Analysis for MSME Lending Using Bank Statement Data

Source: https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india/

- **Problem:** MSME lenders need a cash flow picture to calculate DSCR and loan serviceability, but most MSMEs have no audited cash flow statements — and synthetic P&L approximations introduce multiple inference steps that may not be reliable for the target borrower segment.
- **Logic:** Bank statement transactions are classified into operating (business inflows minus operating outflows), investing (one-time large asset outflows), and financing (loan inflows, EMI outflows, owner capital transfers) cash flow categories. Operating cash flow is the primary repayment capacity indicator. Financing cash flow reveals existing debt burden. Investing cash flow flags capital expenditure intent or asset disposal.
- **Config:** Classification rules distinguish NACH EMI debits (financing) from vendor NACH payments (operating). Large one-time outflows above a configurable threshold trigger investing classification review. Seasonal adjustment window is configurable (3-month, 6-month, 12-month normalisation).
- **Output:** Three-statement cash flow summary: operating, investing, and financing cash flows by month. Rolling average operating cash flow. Calculated DSCR against identified debt service obligations. Seasonal variance flag if monthly operating cash flow swing exceeds 40%.

### Cash Flow Reconciliation: Matching P&L to Actual Bank Movements

Source: https://www.terra-insight.com/insights/cash-flow-reconciliation-india/

- **Problem:** Under Ind AS 7, a cash flow statement must tie to the net change in cash and cash equivalents. Unreconciled bank items, unrecorded TDS receivables, misclassified capex, and unreconciled intercompany flows all propagate into a cash flow statement that does not balance.
- **Logic:** Start from a fully reconciled bank, AR, and AP position, then build cash flow using the indirect method with explicit reconciliation of TDS receivable, advance tax, and non-cash adjustments. Classify each movement cleanly into operating, investing, or financing, and tie capex to the fixed-asset addition schedule.
- **Config:** Pre-requisite checks that bank recon, AR, AP are closed before cash flow preparation; TDS receivable and advance tax split rules; capex-to-FAR mapping; Ind AS 7 classification library.
- **Output:** A cash flow statement whose net change in cash matches the bank ledger movement to the rupee, with audit-ready reconciliation working papers and board-grade free cash flow commentary.

### Cash-to-Bank Reconciliation for UPI and POS Transactions in India

Source: https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india/

- **Problem:** UPI and POS collections credit to bank accounts as T+1 bulk settlements (for example, one ₹48,750 credit covering 23 transactions) net of MDR (1.5–2.5% for credit cards, 0% for RuPay and debit). Matching the bulk credit against invoice-level data without the aggregator settlement file is not feasible at scale.
- **Logic:** Ingest the aggregator or acquirer settlement file per gateway (Razorpay, PayU, Cashfree, PhonePe Business, HDFC/ICICI POS) and disaggregate each bulk credit into gross transactions, MDR, GST on MDR, and any e-commerce-operator TDS (Section 194O / §393(1) Sl. 8(v) code 1035). Match disaggregated items to invoice-level revenue and match the net settlement to the bank credit by UTR or settlement reference.
- **Config:** Gateway-specific settlement parsers, MDR-to-ledger mapping, e-commerce-operator TDS receivable posting under code 1035 (legacy 194O), and T+1 timing tolerance for weekend and holiday settlements.
- **Output:** Daily reconciled UPI and POS revenue with per-transaction audit trail, MDR and e-commerce-operator TDS correctly posted, and a disaggregated settlement ledger ready for GSTR-1 declaration and Form 26AS / Form 168 match.

### Cashfree MDR Reconciliation: 1.6% Promo with 40% UPI Mix Lock-In

Source: https://www.terra-insight.com/insights/cashfree-mdr-reconciliation-india/

- **Problem:** Cashfree's 10-year-anniversary 1.6 percent flat promo is the most attractive published blended rate in the Indian payment-aggregator market, but it carries four conditional terms that compound silently: a 12-month lock from sign-up, a ₹1 crore monthly GTV cap, an international card carve-out tiered at ₹10 lakh, and a 40 percent UPI mix requirement that rescinds the promo entirely for the remainder of the lock if missed in any single month.
- **Logic:** Reconciliation joins the Cashfree settlement file against the merchant OMS and the bank statement, then runs four parallel checks per cycle. Check one verifies the rolling UPI GTV share against the 40 percent floor and flags any month at risk. Check two segregates international Visa/Mastercard GTV and tracks the cumulative ₹10 lakh international threshold against the 2.69 percent promo band and the 2.99 percent overflow band. Check three isolates Amex transactions — Indian-issued at 2.95 percent and Amex-abroad at the standard international rate plus forex. Check four breaks out the EMI and Pay Later instrument set against the independent rate card. Every check carries GST on MDR as a separate line and reconciles to the monthly Cashfree GST invoice.
- **Config:** Cashfree settlement-file ingestion with settlement_id and payment_id joins to the OMS; per-instrument MDR rule set covering UPI, domestic cards, NetBanking, wallets, domestic prepaid, international Visa/Mastercard, Amex domestic and abroad, debit and credit EMI, cardless EMI, and Pay Later; rolling 40 percent UPI mix monitor with a configurable warning band; international GTV cumulative tracker against the ₹10 lakh promo cap; refund non-reversal check; monthly GST invoice matcher for input tax credit; and a promo-eligibility audit log for the 12-month lock period.
- **Output:** A monthly Cashfree fee scorecard with per-instrument effective rate, the rolling UPI mix against the 40 percent floor with an early-warning trigger, the international promo headroom in rupees and days remaining, an exception list for any month where the promo would rescind, a refund-MDR drag estimate, a reconciled GST-on-MDR claim ready for GSTR-2B, and an annual exposure number the controller can take to the board for a renegotiation or migration decision.

### Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling

Source: https://www.terra-insight.com/insights/cashfree-settlement-reconciliation/

- **Problem:** Cashfree's default T+1 settlement cycle arrives before most ERPs have finalised the prior day's order data, creating a recon window mismatch. The separate Cashfree Payouts product for bulk disbursements runs a parallel debit reconciliation that must not be co-mingled with collection settlements.
- **Logic:** Collection-side matching joins Cashfree settlement_id against bank NEFT credit using UTR plus net amount plus T+1 date, then unpacks to order_id with MDR (1.5-2% cards, 0% UPI) and GST on MDR. Payouts-side matching runs an independent track joining outgoing transfer IDs to bank debits and downstream vendor or refund liability. Test-mode and OMS-orphan transactions are isolated.
- **Config:** Dual pipelines — Collection (settlement_id) and Payouts (transfer_id) — T+1-aware window, monthly GST invoice matcher for ITC, and test-mode filter rule.
- **Output:** Two separate reconciliation outputs (inbound settlement ledger and outbound payouts ledger), MDR over-deduction exception list, GSTR-2B ITC claim for MDR GST, and variance explanation trail for auditors.

### Cashless Claim Settlement Reconciliation for Hospitals and Insurers

Source: https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation/

- **Problem:** Cashless claims involve preauth approval, bill enhancement, final settlement, and patient co-pay collection — each creating separate financial entries that must reconcile to a single patient episode.
- **Logic:** Track claim from preauth through final bill, match TPA settlement to approved amount, reconcile patient co-pay against billing shortfall, classify variance as enhancement denial or rate dispute.
- **Config:** IRDAI preauth timeline 1 hour, final settlement 30 days, co-pay tolerance per policy terms, split-payer matching (insurance + patient).
- **Output:** Per-episode reconciliation with preauth-to-settlement trail, co-pay collection status, denied enhancement register, and IRDAI compliance timeline report.

### Casting Process Reconciliation: Melt Loss, Rejection and Auto-Component Material Accounting

Source: https://www.terra-insight.com/insights/casting-melt-loss-rejection-reconciliation-auto-india/

- **Problem:** An Indian aluminium casting supplier producing HPDC transmission housings or GDC cylinder heads must reconcile aluminium ingot inbound to good casting outbound across six process stages (charging, melting, holding, pouring, trimming, finishing or machining), with structural melt loss of 2-4 percent of charged metal at the furnace, rejection rate of 3-8 percent recycled as return-melt, in-house gates and runners recycled, LME-linked RMPV on aluminium ingot per month, Ind AS 16 capitalisation of casting dies depreciated over expected die-cycle life, Section 393(1) Sl. 6(i).D(b) payment code 1024 TDS on conversion-charge billing on principal-supplied material, conversion-service GST at 18 percent under HSN 9988 on free-issue contracts, and Section 394 TCS code 1071 at 1 percent on external sale of dross and machining swarf.
- **Logic:** Maintain per-die master with cycle-counter and expected cycle life and per-furnace charge log capturing virgin-ingot inbound, return-melt charged, dross skimmed and good metal poured. Per shot, log dispatched good casting weight, trimmed-runner weight (recycled in-house), reject castings (recycled in-house), and finishing scrap. Close the metal-balance identity over the month; flag any rejection drift above contracted norm as conversion-cost erosion. Compute LME-linked RMPV claim against contracted monthly reference. Post die-amortisation per cycle under Ind AS 16. Apply Section 393(1) Sl. 6(i).D(b) code 1024 TDS where conversion charge is billed on principal-supplied ingot; apply Section 194Q where the sale is a goods sale. Collect Section 394 TCS code 1071 on external sale of dross and machining swarf.
- **Config:** Aluminium-grade master with LME-reference rule and India-premium calendar; per-die master with cycle-counter, expected cycle life and refurbishment trigger; per-furnace charge-log template; rejection-norm per part per OEM; return-melt accounting rule with in-house recycle flag; supplier-owned versus principal-supplied flag per OEM contract; Section 393(1) Sl. 6(i).D(b) code 1024 versus Section 194Q payment-code map; Section 394 TCS code 1071 buyer master for dross and swarf sales.
- **Output:** A monthly casting reconciliation statement closing the metal balance per furnace charge and per OEM, including dross loss, rejection roll-forward, return-melt cycle and process loss; die-cycle dashboard with refurbishment-trigger alerts; LME-linked RMPV claim per month per grade; conversion invoice at contracted rates with 18 percent GST under HSN 9988 on free-issue contracts; payment-code-mapped TDS register (Section 393 code 1024 or Section 194Q) with quarterly Form 26Q export; Section 394 TCS code 1071 register for dross and swarf external sales; and an audit-ready metal ledger that ties to physical ingot, WIP and finished-casting stock at any OEM-initiated count.

### CCI Cotton Corporation of India Procurement Reconciliation

Source: https://www.terra-insight.com/insights/cci-cotton-corporation-india-procurement-reconciliation/

- **Problem:** A Rajasthan or Bhilwara-belt ginning mill running an FY 2026-27 procurement plan of approximately 45,000 bales at 170 kg per bale — around 7,650 tonnes of cotton — split roughly 65 percent through the CCI MSP channel and 35 percent through direct farmer or private trader channels, must reconcile every CCI-channel dispatch against a season-level Ministry of Textiles MSP notification, the CCI regional office's negotiated or auctioned bale price, the grade premium or discount schedule for the crop year, the freight and storage recovery lines bundled into the invoice, and the mill's own gate-inward quality-test lab report. Manual reconciliation across the four charge lines on the CCI invoice (base, grade, freight, storage), the 5 percent GST computation on the composite invoice, and the Section 8 Sl. 8 code 1031 (194Q) threshold at CCI's corporate PAN produces a monthly cotton-inward pack that is either wrong on ITC or wrong on TDS, exposing the mill at both the GST and income-tax audit.
- **Logic:** Build a CCI procurement register keyed by the CCI dispatch memo number and lot number, capturing the CCI regional office GSTIN, the auctioned or negotiated base price against the reference grade, the actual delivered grade class as marked on the memo, the freight recovery line, the storage recovery line, and the composite 5 percent GST computation. Ingest the mill's gate-inward register with actual bale count, gross weight, tare weight, and net cotton weight. Ingest the quality-test lab report at inward — moisture, trash, staple length, strength, micronaire — and compute the grade class per the mill's own testing. Match every CCI invoice line to the gate-inward record by memo number, lot number, and bale count, and reconcile the grade-adjustment differential where the mill's re-tested grade differs from the CCI-declared grade. Roll up all CCI invoices in the FY by CCI's corporate PAN and apply the Section 8 Sl. 8 code 1031 (194Q) threshold at ₹50 lakh, deducting 0.1 percent on the excess. Split the freight recovery line to code 1014 or 1002 TDS deduction based on the transporter's PAN and status. Feed the composite base + grade + freight + storage + GST into GSTR-2B reconciliation against CCI's outward invoice as filed.
- **Config:** CCI regional-office master with GSTIN, CCI corporate PAN, purchase centre location (Bhilwara, Nagpur, Rajkot, Guntur, Warangal, etc.); MSP master keyed by cotton season with medium-staple and long-staple base rates from the Ministry of Textiles notification; grade premium/discount schedule per crop year with staple length band, strength band, micronaire band, and per-candy adjustment; freight-transporter master with PAN, TDS deduction category (Individual/HUF at 1 percent code 1014, other at 2 percent code 1014 or code 1002); mill quality-testing lab configuration for automated grade classification (staple length, uniformity ratio, strength, micronaire, moisture, trash percent); Section 8 Sl. 8 code 1031 (194Q) threshold at ₹50 lakh with cumulative PAN-level tracking; direct-farmer reverse-charge configuration under Notification 4/2017-CTR with self-invoice generation under Section 31(3)(f); GSTR-2B reconciliation feed for CCI's forward-charge supplies and RCM outward-inward pairing for direct-farmer procurement.
- **Output:** A monthly cotton-inward reconciliation pack for the ginning mill: CCI invoices by regional office, split into base + grade adjustment + freight recovery + storage recovery + GST components; gate-inward bale count and weight variance versus CCI dispatch memo; quality-test lab grade classification versus CCI-declared grade with premium/discount variance line; Section 194Q (code 1031) threshold tracking with cumulative CCI PAN-level purchases and 0.1 percent excess-value TDS deduction; freight-line TDS split by transporter PAN under code 1014 or 1002; GSTR-2B reconciliation of CCI's outward supply against the mill's inward register; direct-farmer procurement reverse-charge self-invoice register with matched ITC entry; and an MSP variance report at season-end showing the mill's average CCI purchase rate versus the notified MSP for medium and long staple, cross-checked against the direct-farmer procurement rate for the same period.

### CCL Products Instant Coffee B2B Export Reconciliation India

Source: https://www.terra-insight.com/insights/ccl-products-instant-coffee-b2b-export-reconciliation/

- **Problem:** A listed Hyderabad-headquartered instant-coffee B2B contract manufacturer running a Kuting Andhra Pradesh plant plus a Vietnam plus a Switzerland leg exports approximately 55,000 MT of instant, freeze-dried, and agglomerated coffee to 90-plus country destinations at a FOB weighted average of USD 6,800 per MT, translating to a Rs 3,164 crore annual India-side export book. Green-coffee input at HSN 0901 attracts 5 percent GST; packaging inputs (HSN 3923 laminate, HSN 4819 cartons, HSN 4823 fibreboard drums), freight, CHA, and process consumables attract 18 percent GST; boiler fuel and power sit outside GST (HSD, state-VAT electricity duty); and the entire manufactured output moves under HSN 2101 zero-rated on LUT under Rule 96A. Manual reconciliation across the green-coffee procurement register, the Kuting plant batch production log, the container dispatch tally against shipping bills, the e-BRC realisation, and the monthly Section 54(3) refund workbook loses input-GST allocation to the wrong tax period, under-claims RFD-01 by excluding legitimate ITC or over-claims by including capital-goods ITC that Rule 89(4) excludes, misses the 9-month FEMA realisation band on trailing receivables, and mis-classifies Section 195 TDS on foreign royalty remittance under the wrong DTAA article.
- **Logic:** Ingest the green-coffee procurement register keyed to lot number, supplier PAN, HSN 0901, moisture and defect grade, and input GST at 5 percent; expand each purchase to the electronic credit ledger and tag by tax period. Ingest the plant batch production log keyed to batch code, input green-coffee kilograms, output instant-coffee kilograms, and process-consumable draw at 18 percent GST. Reconcile plant yield against operating band (typically 2.6 to 3.0 kg green per kg instant); expose yield variance beyond the band as a reconciliation exception. Ingest the container dispatch register keyed to container number, seal number, destination port, shipping-bill number on ICEGATE, and commercial-invoice number; run a five-way match against the packing list and the eventual e-BRC on realisation. Ingest the AD bank e-BRC feed keyed to shipping-bill number, realised currency amount, realised INR amount, and realisation date; compute the FEMA 9-month band per SB and flag trailing receivables. Ingest the packaging, freight, CHA, and process-consumables input register at 18 percent GST; consolidate into the Section 54(3) refund workbook per Rule 89(4) formula, excluding capital-goods ITC from Net ITC and drawback-availed turnover from Adjusted Total Turnover. Generate Form GST RFD-01 monthly against the accumulated refund base. Extract foreign-remittance events (brand-licence royalty, technical-services fees, dividend to foreign shareholder) into a Section 195 register keyed to DTAA article, treaty rate, and Form 15CA/15CB reference. Translate all foreign-currency receivables at each month-end closing rate for the Ind AS 21 forex-variance line.
- **Config:** Green-coffee supplier master with PAN, GSTIN, Coffee Board grower/curer registration, and MSME Udyam registration flag for Section 43B(h) 45-day check; commodity master with HSN 0901 sub-code (unroasted, roasted, decaffeinated) and input GST at 5 percent; process master with HSN 2101 sub-code (instant coffee, freeze-dried, agglomerated, decaffeinated instant) and zero-rated output flag on LUT; plant master with plant code (Kuting AP, Vietnam leg, Switzerland leg), operating yield band, and jurisdiction (India / Vietnam / Switzerland); container dispatch master with container number, destination port, and shipping-bill reference; commercial-invoice master with export currency, FOB rate, gross-up if applicable, and payment terms; AD bank master with e-BRC feed configuration and outward-remittance feed configuration; foreign-remittance master with DTAA article, treaty rate, gross-up flag, Form 15CB certifier, and Form 27Q reconciliation code; Ind AS 21 currency master with month-end closing rates from the RBI reference rate feed; Section 43B(h) MSME flag on packaging and process-consumables suppliers; RoDTEP Appendix 4R rate per HSN 0901 and HSN 2101 sub-code.
- **Output:** A month-end multi-surface instant-coffee export reconciliation pack: green-coffee procurement register with input GST at 5 percent tagged to tax period, plant batch production log with yield variance against operating band, container dispatch register with five-way match against SB, commercial invoice, packing list, and e-BRC status, AD bank e-BRC realisation tally with FEMA 9-month band alert, Section 54(3) refund draft with Rule 89(4) formula applied and capital-goods ITC excluded from Net ITC, RoDTEP scrip ledger against realised shipping bills, Section 195 foreign-remittance register with DTAA article and Form 15CA/15CB reference, and Ind AS 21 forex-variance line reconciled against the currency-wise receivables ledger and the AD bank outstanding-export report. Trailing-receivable exception queue supports the FEMA 9-month compliance discipline; yield variance queue supports the plant operations review; and RFD-01 accumulation ledger supports the monthly working-capital planning cycle.

### CDMO Margin and Transfer Pricing: The Piramal and Syngene Playbook

Source: https://www.terra-insight.com/insights/cdmo-contract-manufacturing-margin-transfer-pricing-pharma/

- **Problem:** A Tier-1 pharma CDMO of the scale of Piramal Pharma Solutions (Digwal, Ennore, Torcan Canada) or Syngene International (Bengaluru, global innovator customers) running a Rs 4,200 crore contract book — illustratively 45 percent cost-plus at an average 18 percent margin, 30 percent fixed-price at an average 32 percent margin, and 25 percent milestone at an average 28 percent margin — must apply Ind AS 115 revenue recognition per contract type (cost-plus over time via input method, fixed-price over time via cost-to-cost input method, milestone at point-in-time on customer acceptance), must flag every intra-group contract above the Section 92BA Rs 20 crore aggregate threshold per associated-enterprise pair for Rule 10D three-tiered transfer pricing documentation (master file + local file + benchmarking study) and Form 3CEB annual filing, must reconcile Section 194Q payment code 1031 buyer-side TDS credit per principal against Form 26AS, and must feed the same intra-group contract register into the annual report Ind AS 24 related-party disclosure so the two disclosure surfaces reconcile at year-end audit.
- **Logic:** Build the contract master with contract type, intra-group flag, Section 92BA marker, associated-enterprise identification for intra-group contracts, principal-entity identification (PAN and GSTIN) for third-party contracts, contract-life value, and budgeted margin populated at inception. Feed the per-contract cost ledger and billing register into a per-contract Ind AS 115 revenue-recognition tracker that applies the method appropriate to each contract type. Extract a per-contract-type margin variance table at monthly close with a root-cause flag on every variance above threshold. Compile a Section 194Q TDS credit register per principal reconciling the CDMO's invoice-level 194Q-expected calculation to the Form 26AS credit and the principal's Form 26Q return line. Compile a Section 92BA intra-group contract register per associated-enterprise pair with the aggregate value tested against the Rs 20 crore threshold, the Rule 10D three-tiered documentation link (master file reference, local file section, benchmarking study reference), and the year-end Form 3CEB feed. Feed the same register into the annual report Ind AS 24 related-party disclosure so the two surfaces reconcile. Refresh the estimate-at-completion cost forecast on every fixed-price contract monthly and raise a completed-contract loss provision alert under Ind AS 37 when the forecast crosses the fixed contract price.
- **Config:** Contract master with per-contract type field (cost-plus, fixed-price, milestone), intra-group flag, Section 92BA marker, associated-enterprise identification (for intra-group contracts) or principal-entity identification (PAN and GSTIN for third-party contracts), contract-life value, budgeted margin, and Ind AS 115 revenue-recognition method assignment; per-contract cost ledger and billing register with month-end refresh; Ind AS 115 method-specific revenue-recognition calculators; per-contract-type margin variance table with root-cause tagging library; Section 194Q TDS credit register per principal reconciling invoice-level expected against Form 26AS and principal Form 26Q; Section 92BA intra-group contract register per associated-enterprise pair with Rs 20 crore aggregate threshold test, Rule 10D master file + local file + benchmarking study reference links, and Form 3CEB annual compilation feed; Ind AS 24 related-party disclosure feed from the same intra-group register; estimate-at-completion cost-forecast refresh loop with completed-contract loss provision alert under Ind AS 37.
- **Output:** A month-end CDMO margin and transfer pricing reconciliation pack: aggregate revenue recognition decomposed by Ind AS 115 method per contract type, per-contract-type margin variance table with root-cause flags, per-principal Section 194Q TDS credit reconciliation against Form 26AS, per-associated-enterprise-pair Section 92BA intra-group contract register with the Rs 20 crore threshold test outcome and the Rule 10D three-tiered documentation status, estimate-at-completion refresh on every fixed-price contract with completed-contract loss provision alerts under Ind AS 37, and the feed into both the year-end Form 3CEB filing and the annual report Ind AS 24 related-party disclosure. The pack serves as the audit reference for both the Ind AS 115 revenue-recognition disclosures and the transfer pricing scrutiny defence for the intra-group contract population, and it materially compresses the time between the tax return filing and the Form 3CEB accountant's certificate.

### CGHS and ECHS Hospital Pharma Billing Reconciliation for Empanelled Suppliers

Source: https://www.terra-insight.com/insights/cghs-echs-hospital-pharma-billing-reconciliation-india/

- **Problem:** Empanelled CGHS and ECHS hospital pharmacies bill against rate-list pricing on the Schedule of Rates, submit monthly bills in a defined file format, and wait T+60 to T+180 for settlement minus deductions across four classes (non-formulary, rate-list mismatch, prescription compliance, beneficiary ID) that eat 4-9% of gross billing, with Section 393(1) Sl. 6(i) government contractor TDS (codes 1023/1024) on top — no generic AR module reconciles prescription line to dispense to claim to deduction memo to bank credit.
- **Logic:** Reconcile CGHS and ECHS as two parallel customer streams keyed by scheme-card number and beneficiary ID, tie each prescription line to dispense entry by drug code with quantity and batch, validate against the approved CGHS drug list and the Schedule of Rates ceiling per item, tag deductions on the settlement memo by class (non-formulary, rate-list mismatch, prescription compliance, beneficiary ID), age unresolved deductions for dispute, separate Section 393(1) Sl. 6(i) contractor TDS line (codes 1023/1024) from the gross-net calculation and tie to 26AS, ensure GST on disallowed lines is reversed in matching credit notes.
- **Config:** Customer master keyed by scheme (CGHS or ECHS) and paying authority bank account, beneficiary-card validation table with expiry and dependant status, approved drug list with Schedule of Rates ceiling per HSN and pack size, prescription compliance ruleset (signature, specialty endorsement, diagnosis, batch, expiry, quantity match), deduction taxonomy with four-class code map, monthly bill-file format template per scheme, Section 393(1) Sl. 6(i) government contractor TDS expected rate by payee type (code 1023 at 1% Ind/HUF, code 1024 at 2% other), GST rate map by HSN with credit-note rule for disallowed lines, optional ABHA identifier as a non-PII reconciliation key where ABDM linkage applies.
- **Output:** A daily reconciled view per scheme showing dispensed prescription lines to monthly bill file submitted to settlement memo received with deduction class-coded by reason and aged, gross-net reconciliation tying the bill total to net bank credit through Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) and GST liability, deduction recovery progress per dispute, monthly bill-submission compliance status (filed, acknowledged, under-process, paid, deduction-disputed), and the Form 26AS credit match per quarter per paying authority.

### CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims

Source: https://www.terra-insight.com/insights/cghs-reconciliation-india/

- **Problem:** CGHS empanelled hospitals bill at their own rates but are reimbursed at CGHS-approved rates, creating systematic rate gaps that accumulate across thousands of claims per year.
- **Logic:** Match claim submissions to CGHS rate master by procedure code, validate referral chain from wellness centre, reconcile settlement from CGHS city office against billed amount.
- **Config:** CGHS rate master (differs from NABH rates), referral validity period, ~38 lakh beneficiaries, settlement through city-wise CGHS offices.
- **Output:** Rate variance report (hospital rate vs CGHS rate), referral validation status, pending settlement tracker, and revenue write-off analysis.

### CGMP Consulting Fees: Section 37 Deduction and TDS Under 194J and 195

Source: https://www.terra-insight.com/insights/cgmp-remediation-consulting-fees-section-37-deduction-pharma/

- **Problem:** An Indian listed pharma group running a multi-year post-Form 483 CGMP remediation programme engages a US-parent CGMP consulting firm, an India-subsidiary CGMP consulting firm, and one or more Indian sub-contractor labs as part of the same programme. Each consultant invoice must simultaneously satisfy the Section 37 wholly-and-exclusively test for revex deductibility, the correct TDS classification (Section 194J code 1005 at 10 percent for Indian residents, Section 195 for non-residents), the applicable DTAA rate for the non-resident (India-USA Article 12 at 15 percent for US-domiciled consultants, subject to the make-available test), the Tax Residency Certificate and Form 10F on file for the foreign consultant before the remittance, and the Form 15CA / Form 15CB pair filed on the CBDT portal before AD Bank release. Rule 44BB is petroleum-scoped and does not apply to pharma CGMP consulting — a mis-characterisation attempt fails an assessment. Missing any hop breaks the invoice-to-remittance chain, exposes the pharma group to short-deduction interest under Section 201, and can trigger a disallowance under Section 40(a)(i) or 40(a)(ia) at the tax audit if the TDS was not deducted or was under-deducted.
- **Logic:** Build a consultant master keyed by vendor code, PAN or overseas tax identifier, residency (India resident / US resident / other DTAA country), TRC and Form 10F on file with expiry date, service category (CGMP consulting / data-integrity audit / method validation / regulatory response drafting), and payment terms. For each invoice raised against the remediation programme, map to the specific Form 483 observation being addressed and to the work-order reference. Classify TDS at source — Section 194J code 1005 at 10 percent for India residents above the Rs 30,000 annual threshold, Section 195 at the DTAA rate for non-residents with TRC + Form 10F on file, Section 195 at the domestic rate where TRC or Form 10F is absent. For every non-resident remittance, file Form 15CA Part C plus Form 15CB on the CBDT portal before the AD Bank release; retain the accountant's certificate in the evidence file. Store the Section 37 wholly-and-exclusively test evidence per invoice — narrative link to observation, work-order reference, business-restoration argument, and cross-link to the internal remediation programme approval. Confirm Rule 44BB non-application in the year-end tax audit working paper. At year-end reconcile the aggregate CGMP consulting cost claimed under Section 37 in the tax return to the Ind AS 37 provision utilisation and to the ledger control total.
- **Config:** Consultant master (vendor code, PAN or overseas TIN, residency country, TRC on file with expiry, Form 10F on file with expiry, service category, payment terms); Form 483 observation register with sub-work-order breakdown; work-order register with capex/revex tag and budgeted vs actual; Section 194J code 1005 TDS workbook (payee PAN, invoice, threshold check at Rs 30,000, TDS at 10 percent, TRACES challan); Section 195 remittance workbook (invoice, residency, DTAA rate applied, TRC + Form 10F on file, Form 15CA Part C + Form 15CB filing reference, AD Bank remittance reference, challan); DTAA rate schedule (India-USA Article 12 FIS 15 percent for US consultants, other DTAA rates for consultants from other jurisdictions); make-available test evidence per non-resident invoice; Section 37 wholly-and-exclusively test evidence pack per invoice with observation link; year-end tax audit reconciliation of Section 37 claim to Ind AS 37 provision utilisation and ledger control total; Section 40(a)(i) and 40(a)(ia) exposure flag on any invoice where TDS was not deducted or under-deducted.
- **Output:** A consultant-wise invoice register that closes four sub-registers in one view. Section 37 evidence pack per invoice with the observation link and business-restoration argument for tax audit. Section 194J code 1005 TDS register on Indian consultants with TRACES challan match. Section 195 remittance register on foreign consultants with DTAA rate applied, TRC/Form 10F on file, and Form 15CA/15CB filing reference. DTAA TRC evidence file with expiry dates tracked. A year-end reconciliation cross-tying the aggregate CGMP consulting cost claimed under Section 37 to the Ind AS 37 provision utilisation and to the ledger control total, with any Section 40(a) disallowance exposure flagged for pre-emptive correction before the return is filed.

### Chargeback Reconciliation for Payment Gateways: A Finance Team Guide

Source: https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway/

- **Problem:** Chargebacks reverse card payments up to 120 days post-transaction, appear as deductions in future settlement statements, and attract fees of ₹500–₹2,000 each. Card network thresholds (Visa 0.9%, Mastercard 1.0%) can trigger higher MDR, rolling reserves, and account termination.
- **Logic:** Match each chargeback deduction in the settlement file to the original transaction in the order management system, reverse the revenue, issue a GST credit note, and post the chargeback fee to a fee expense account. Track the rolling reserve balance as a receivable from the gateway and age it against the 90–180 day release window.
- **Config:** Settlement parser with chargeback line detection, order-management system matching by gateway transaction ID, GST credit note linkage for revenue reversal, and rolling reserve sub-ledger.
- **Output:** Accurate revenue net of chargebacks, GST credit notes filed in the correct return period, chargeback fee expense captured in full, and a rolling reserve ledger tied to future cash release.

### Chargeback Dispute Won: Recovery Reconciliation Label Gap

Source: https://www.terra-insight.com/insights/chargeback-dispute-won-recovery-streaming-payment-gateway-india/

- **Problem:** Chargeback-won recoveries return money to a streaming merchant weeks or months after the original settlement, but payment gateway settlement files rarely provide a distinct label — the credit lands as a generic adjustment or a refund reversal. Without a dedicated chargeback lifecycle log, the ledger loses the linkage between the original transaction, the dispute case number, the representation evidence, and the recovery.
- **Logic:** Track every disputed transaction through a four-state lifecycle: Filed (acquirer notification), Represented (evidence submitted within 30 days), Won (network decision in merchant's favour), Lost (network decision against). Attach a case_id that persists across all states. Match the settlement credit at Won to the case_id, not just to the original payment_id, so the reconciliation records the dispute outcome as well as the money movement.
- **Config:** Chargeback lifecycle log with four states, mandatory case_id capture from acquirer notifications, positive-credit classifier that separates refund_reversed from chargeback_reversed, GL entry templates per state (Receivable at Filed, reversal at Won, write-off at Lost), and a Section 34 gate that prevents auto-generation of credit notes for chargeback_reversed events.
- **Output:** Chargeback case ledger with full audit trail from filing to recovery, disputes-won recovery register matched to acquirer case IDs, correctly classified settlement analytics that do not pollute refund rate, and clean GSTR-3B position with no false credit notes.

### Chargeback reconciliation in India — matching disputes, deductions, and representment

Source: https://www.terra-insight.com/insights/chargeback-reconciliation-india/

- **Problem:** Chargebacks appear in payment gateway settlement reports as negative deductions — often without a direct order reference — sometimes for transactions up to 120 days old under Visa and Mastercard rules. Without order-level matching, chargebacks are misclassified as refunds or MDR adjustments and written off as unexplained variances.
- **Logic:** Matching scans every negative line in the settlement report and classifies it as chargeback, refund, MDR adjustment, or fee reversal using payment_id, dispute reference, and amount signature. Chargebacks are linked back to the original order by card BIN plus last-four plus amount plus transaction date, even when no order_id is present, and flagged against the 5-10 day dispute window for representment.
- **Config:** Multi-gateway ingestion (Razorpay, PayU, Cashfree) with gateway-specific chargeback code mapping, dispute-window SLA tracker, and representment evidence packager.
- **Output:** Classified chargeback register linked to originating orders, representment response pack within the dispute window, lost-chargeback write-off journal, and Section 34 credit note decision log where supply was reversed.

### Chocolate and Confectionery GST 2.0 Reconciliation

Source: https://www.terra-insight.com/insights/chocolate-confectionery-gst-2-0-reconciliation-fmcg/

- **Problem:** Indian FMCG chocolate and confectionery brands run their largest distributor scheme cycles around the festive Q3 window — October to December — with build-up trade load-in beginning in late August. The CBIC GST 2.0 rate rationalisation moved chocolate (HSN 1806), sugar confectionery (HSN 1704), and biscuits (HSN 1905) from 18% to 5% effective 22 September 2025, splitting the Q3 scheme cycle across two GST regimes. Modern trade gondolas in October simultaneously hold pre-22-September stock at the 18% MRP overprint and post-22-September fresh stock at the 5% MRP, and the per-scheme credit-note settlement must reconcile to the underlying invoice rate at the time of supply, not the credit-note-issue rate.
- **Logic:** Maintain a rate-effective-date field per HSN per SKU per scheme line. For each Q3 scheme settlement, split the accrual base by secondary-sale date around 22 September 2025. Pre-22-September secondary sales settle via credit notes at the original 18% rate; post-22-September secondary sales settle at 5%. Split the credit-note cycle into two GSTR-1 amendment streams, one per rate. Separately track the MRP-protection credit flow on pre-22-September stock that sells through at the old MRP — this credit is independent of the trade-scheme accrual and must not be double-counted in the Section 15(2) cycle. Per-scheme, validate the three-prong Section 15(2) test and capture distributor ITC-reversal acknowledgement before the credit note is issued.
- **Config:** HSN-effective-date table (1806 from 18% to 5% on 22 September 2025; 1704 from 18% to 5%; 1905 from 18% to 5%; aerated beverages to 40% NSAB); scheme master per scheme code with rate-straddle flag, Section 15(2) treatment flag, geography and category filters; secondary-sales feed from DMS by distributor by SKU by date split around 22 September 2025; dispatch-invoice register by invoice number by HSN by rate; credit-note register linked to original invoices with rate-specific lines; MRP-protection register for re-stickering or absorption flows on pre-22-September stock; GSTR-1 amendment month per credit-note-rate split; Section 393(1) Sl. 18 (194H) distributor commission TDS rate at 5% with payment codes 1015/1016.
- **Output:** A per-distributor Q3 reconciliation pack splitting scheme settlements into pre-22-September 2025 (18% rate) and post-22-September 2025 (5% rate) buckets; credit-note ledger linked invoice-by-invoice to the original dispatch with rate-specific lines; GSTR-1 amendment lineups in the right month for each rate-effective period; MRP-protection credit flow isolated from trade-scheme accrual; Section 15(2) qualification register with ITC-reversal acknowledgement per scheme; CFO-level summary of Q3 scheme cost at blended effective rate and the IMS reconciliation state with each distributor.

### Clinical Trials and CRO Fees: What Section 35(2AB) Allows

Source: https://www.terra-insight.com/insights/clinical-trial-cro-expenditure-section-35-2ab-eligibility-pharma/

- **Problem:** A Tier-1 Indian innovator pharma company running a DSIR-approved R&D innovation centre commissions clinical CROs for Phase 2 dose-finding and Phase 3 registration studies at aggregate outsourced fees of the order of Rs 60 crore per molecule programme. The Section 35(2AB) reconciliation surface is a per-CRO per-invoice carve-out between the clinical trial expenditure operating under contract linked to the DSIR-approved facility (with the trial protocol filed at DSIR) — which is eligible for the 100 percent weighted deduction — and the regulatory strategy consulting or market-access research portion of the same CRO umbrella, which is not scientific research within the meaning of Section 35(2AB) and drops to Section 37 general-deduction treatment. Each CRO invoice must be flagged for eligibility, matched to a TDS challan under Section 194J (India-domiciled CRO) or Section 195 (foreign CRO or foreign parent) at the applicable Finance Act or DTAA rate, retranslated under Ind AS 21 where the payable straddles a reporting date, and certified in Form 3CL by the DSIR-empanelled Chartered Accountant with the invoice-level supporting evidence chain intact.
- **Logic:** Build a CRO contract register keyed to each contract with the Section 35(2AB) eligibility flag per scope-of-work line item, the DSIR facility linkage (Form 3CM approval reference), and the DSIR-filed protocol acknowledgement. Extract each CRO invoice with the scope-of-work line, the eligible-versus-non-eligible split, the invoice currency (INR for domestic CROs, USD or other for foreign CROs), the transaction-date spot rate for the rupee-equivalent expenditure feed, and the reporting-date closing rate for Ind AS 21 retranslation of any unsettled payable. Match each CRO invoice to the TDS challan — Section 194J code 1005 at 10 percent for India-domiciled CROs, Section 195 at the applicable DTAA rate for foreign CROs — with the CIN (challan identification number) as the reconciliation key. Feed the eligible-portion aggregate to the Form 3CL year-end certification and the eligible-versus-Section-37 split to the Form 3CLA return-of-income schedule. Hold the CRO payable ledger with the running forex-retranslation trail as a distinct control column so the transaction-date rupee value flowing into the Section 35(2AB) claim base is not conflated with the subsequent forex movement on the payable.
- **Config:** R&D facility master keyed to the DSIR Form 3CM approval reference (facility name, address, three-year renewal cycle, approved scope); CRO master keyed to each CRO's PAN and Section 194J code 1005 or non-resident status under Section 195 (with the applicable DTAA article and rate); CRO contract register keyed to contract reference with the scope-of-work line items, the Section 35(2AB) eligibility flag per line, the DSIR facility linkage, and the DSIR-filed protocol acknowledgement; CRO invoice register with invoice-level Section 35(2AB) eligibility flag, invoice currency, transaction-date spot rate, and reporting-date closing rate; TDS challan register matched invoice-by-invoice with CIN as the reconciliation key; Ind AS 21 forex retranslation working per foreign CRO payable straddling a reporting date; Form 3CL supporting-evidence file per invoice; Form 3CLA return-of-income schedule with the eligible-versus-Section-37 split; Section 40(a)(i) disallowance monitor for any foreign CRO invoice where the TDS challan is missing or late-deposited.
- **Output:** A year-end Section 35(2AB) CRO expenditure certification pack per DSIR-approved facility: the aggregate eligible outsourced CRO expenditure with per-CRO per-invoice detail, the Section 37 non-eligible carve-out with the regulatory strategy consulting and market-access research lines separately disclosed, the Form 3CL DSIR-empanelled Chartered Accountant certification with the invoice-level supporting-evidence chain intact, the Form 3CLA schedule feed for the ITR-6 filing, the TDS challan reconciliation showing every CRO invoice matched to a Section 194J or Section 195 deposit with the CIN reference, the Ind AS 21 forex retranslation trail for foreign CRO payables, and a Section 40(a)(i) exposure flag for any foreign CRO leg where the TDS chain is incomplete. The pack feeds the ITR-6 return and stands as the defence file at any subsequent Section 148 reopening or scrutiny under the assessment cycle.

### Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities

Source: https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation/

- **Problem:** A multi-brand cloud kitchen operator runs five to fifteen virtual brands from one commissary under a single GSTIN, but each brand lists separately on Zomato, Swiggy, and Magicpin — making GSTIN-level filing accurate for tax while leaving brand-level P&L and unit economics invisible to operators.
- **Logic:** Tag every aggregator order with its brand listing ID, allocate shared kitchen costs via a cost driver (orders, prep time, ingredient weight), separate commissary-to-kitchen stock transfers from revenue flows, and produce a brand-level contribution margin alongside the GSTIN-level GSTR-1 and GSTR-3B filings without breaking tax compliance.
- **Config:** Aggregator settlement file connectors with brand ID parsing per order; brand-to-GSTIN mapping table; kitchen cost allocation rules with selectable driver; commissary stock-transfer module with intra-state and inter-state IGST handling; brand sub-ledger for commission, TDS 194O, TCS Section 52, and ad spend.
- **Output:** A reconciled monthly view that produces a tax-compliant GSTR-1 at GSTIN level and a brand-by-brand P&L showing revenue, COGS, commission, marketing spend, and contribution margin — supporting menu engineering, brand wind-down, and capital allocation decisions.

### CMP (Conversion Manufacturing Price) Garment Export Reconciliation

Source: https://www.terra-insight.com/insights/cmp-conversion-manufacturing-price-garment-export-reconciliation/

- **Problem:** The CMP model splits the economic value of a garment export shipment across three regulatory surfaces that live in different books. The foreign brand supplies fabric, trims, hangtags, and labels free-of-cost — value that is real, is invoiced by the brand to its nominated mill in Bhilwara or Ludhiana, and moves into the CMP exporter's factory on a Rule 55 delivery challan, but never appears on the exporter's purchase ledger. The exporter invoices only the conversion charge, typically 25 to 40 percent of FOB, at 5% GST under Notification 11/2017-CTR Entry 26. The shipping bill is filed at the full FOB export value at which the brand takes title in the destination market, and the RoDTEP claim is calculated on that FOB value under Appendix 4R for DTA exports. Reconciling the four registers — free-issue inbound, production floor, CMP invoice, and shipping-bill FOB — is what makes the difference between a clean Section 143 posture and a retro-liability notice on unaccounted fabric.
- **Logic:** Build a per-brand-PO free-issue inbound register that captures brand PO number, brand-nominated mill, fabric HSN, quantity in metres, brand-invoiced fabric value (used only for Section 143 exposure quantification, not booked as purchase), and Rule 55 delivery-challan number and date. Age each PO against the 12-month Section 143 clock. Feed the register into the production floor system by style code and cutting plan; capture wastage percentages against contracted norms. Match CMP conversion invoices to production output by style code and shipment reference at the contracted rate per piece. Match the shipping bill to the same shipment reference and reconcile the FOB value to the brand's take-title price via the sales-contract addendum. Reconcile the RoDTEP scrip credit in the DGFT portal to the shipping-bill entitlement per Appendix 4R rate for the HS Code. Any mismatch is either a Section 143 flag (age fabric approaching 12 months), a wastage flag (exceeding norm), or a RoDTEP under-claim (scrip credited below expected).
- **Config:** Brand master with brand code, contracted CMP rate per piece by product family, RoDTEP applicability flag, and Section 143 principal designation (brand's Indian agent or exporter as recipient); style master with style code, HS Code (Chapter 61/62/63), fabric HSN, GSM norm, and contracted wastage percentage; free-issue inbound register with brand PO, mill delivery challan, HSN, quantity, brand-invoiced value; production register with style code, cutting-plan quantity, output quantity, wastage; CMP invoice register with shipment reference, quantity, conversion charge, 5% GST; shipping-bill register with FOB value, HS Code, RoDTEP entitlement per Appendix 4R rate; DGFT RoDTEP scrip ledger reconciliation cadence.
- **Output:** A monthly CMP reconciliation pack: opening free-issue fabric stock in metres by brand PO, receipts, issues to floor, wastage, closing stock, and Section 143 ageing (POs approaching 12 months flagged); production output versus cutting-plan variance; CMP invoice value reconciled to production output at contracted rate; shipping-bill FOB reconciled to brand take-title price by shipment; RoDTEP entitlement per shipping bill versus scrip credited in the DGFT portal; Section 143 deemed-supply liability exposure for POs crossing the 12-month clock; ITC-04 register handoff for the quarterly or half-yearly filing depending on aggregate turnover.

### Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge

Source: https://www.terra-insight.com/insights/co-operative-bank-statement-ocr/

- **Problem:** Co-operative and RRB bank statements have no shared core banking standard, producing wildly inconsistent column layouts, handwritten supplement pages, and narration codes that dedicated bank parsers cannot pre-map.
- **Logic:** A generic column-variant fallback engine matches headers against a library of 300+ known Indian bank column names and uses positional inference for unrecognised headers, flagging low-confidence rows for credit team review.
- **Config:** Lenders with high co-operative bank submission volumes can justify dedicated parser profiles for specific institutions; otherwise the generic fallback handles extraction with narration classification defaulting to 'Other' for unrecognised local payment codes.
- **Output:** A transaction table with extracted debit, credit, and balance rows, with narration classification confidence scores that allow the credit team to identify which rows require manual verification.

### Coaching and EdTech Revenue Recognition under Ind AS 115: Course Fee Performance Obligations

Source: https://www.terra-insight.com/insights/coaching-edtech-revenue-recognition-ind-as-115-india/

- **Problem:** Indian coaching institutes and ed-tech platforms must recognise course-fee revenue under Ind AS 115 with performance obligation identification, contract liability unwind, refund-liability accounting, and ed-tech aggregator commission treatment under Section 9(5) of CGST and Section 393(1) Sl. 8(v) payment code 1035 (replacing 194O) — all while reconciling unearned revenue, withdrawal events, and the marketplace settlement to tutor-level payout.
- **Logic:** Identify performance obligations per course type (over-time live delivery, point-in-time access); compute transaction price net of refund-policy variable consideration; recognise revenue over time using straight-line or sessions-delivered measure; hold contract liability and refund liability with disclosed unwind; for marketplace transactions reconcile gross to commission to TDS to GST to supplier payout; reconcile monthly to GSTR-1, GSTR-3B and TDS quarterly returns.
- **Config:** Ind AS 115 course-revenue configuration with performance obligation taxonomy per course type, refund-policy schedule, contract liability and refund liability subledgers, course-progress measure (straight-line vs sessions), marketplace settlement engine with Section 9(5) CGST classification check, Section 393(1) Sl. 8(v) code 1035 TDS deduction at 0.1% above ₹5 lakh, GST 18% on commission, supplier-tutor payout calculator and bank reconciliation.
- **Output:** A month-end revenue close where every active course's contract liability unwinds correctly into revenue per Ind AS 115, refund liability movement matches withdrawal events, marketplace gross reconciles to platform commission plus supplier payout plus TDS plus GST, and the disclosures align with GSTR-1, GSTR-3B and TDS quarterly returns — auditable for the statutory audit and any peer review.

### Coastal Corporation Marine Export Reconciliation — Visakhapatnam

Source: https://www.terra-insight.com/insights/coastal-corporation-marine-export-reconciliation-visakhapatnam/

- **Problem:** A listed Visakhapatnam-based marine exporter shipping approximately 600 MT of vannamei shrimp per month to the US market at a weighted FOB of USD 6,200 per MT — aggregate monthly export value in the Rs 30 crore range — must reconcile per-shipment EIC Health Certificate issuance from EIA-Chennai after antibiotic-residue lab clearance, MPEDA RCMC-anchored shipping-bill filing on ICEGATE, RoDTEP scrip credit under Appendix 4R for HSN 0306, Section 54(3) refund of unutilised input tax credit on zero-rated supplies under the LUT route, e-BRC realisation matching against the shipping-bill and BL number with a 9-month FEMA realisation window, and the monthly fx-variance GL cycle between invoice-booking date and realisation date under Ind AS 21 and Section 43AA. Manual reconciliation across six independent regulatory rails loses Health Certificate reference linking, orphans RoDTEP scrip against shipping bills, delays Section 54(3) refund filing beyond the two-year limitation, and creates unmatched export debtors in the fx-variance schedule that surface as audit qualifications at year-end.
- **Logic:** Build the shipping bill as the anchor record — Health Certificate number, MPEDA RCMC, RoDTEP opt-in flag, LUT reference, invoice number, foreign-currency value, invoice-date exchange rate, BL number — and expand each shipping-bill line into six downstream reconciliation legs. Leg 1: EIC Health Certificate reference from the pre-shipment inspection lot register, keyed to the invoice's lot IDs; expose Health Certificate gaps as blocking exceptions before shipping-bill assessment. Leg 2: RoDTEP scrip register from DGFT dashboard, matched to shipping-bill FOB and Appendix 4R rate; expose scrip-not-credited exceptions after the notified issuance window. Leg 3: Section 54(3) refund register from GSTR-1 export invoice extract and GSTR-2B input tax credit extract; run the Rule 89(4) formula per tax period and generate the Form GST RFD-01 draft. Leg 4: e-BRC register from DGFT dashboard, joint-matched to shipping-bill number and BL number; expose realisation gaps against the 9-month FEMA window. Leg 5: fx-variance schedule from the debtor sub-ledger, mapping invoice-date rate, period-end rate, and realisation-date rate; generate the fx GL entry and the ICDS Schedule 3CD disclosure line. Leg 6: overseas commission agent payment register with Section 195 TDS deduction where the commission is chargeable to tax in India; generate Form 15CA and 15CB workflow.
- **Config:** Shipping-bill master with SB number, ICEGATE reference, HSN code (0306.17 for frozen vannamei), FOB value in foreign currency and INR, invoice reference, BL number, container seal, Health Certificate number, MPEDA RCMC, LUT reference, RoDTEP opt-in flag; Health Certificate master with certificate number, EIA jurisdiction (EIA-Chennai for Andhra coast), lab-report reference, lot IDs, importer name, destination country; RoDTEP master with Appendix 4R rate table by HSN and effective date; Section 54(3) config with LUT reference, GSTR-1 export invoice feed, GSTR-2B input tax feed, Rule 89(4) formula parameters; e-BRC config with AD bank code, DGFT dashboard feed, 9-month FEMA realisation deadline flag; fx-variance config with RBI reference rate feed, AD bank card rate feed, Section 43AA restatement schedule, Ind AS 21 monthly restatement flag; overseas commission agent master with agent PAN or Section 90 DTAA relief certificate, Section 195 TDS rate, Form 15CA/15CB workflow trigger.
- **Output:** A month-end marine export reconciliation pack: shipping-bill register by port and destination country with Health Certificate linkage, RoDTEP scrip issuance status by shipping bill against Appendix 4R rate, Section 54(3) refund draft with Rule 89(4) formula computation and GSTR-1 to GSTR-2B feed, e-BRC realisation status against shipping bill and BL number joint key with 9-month FEMA aging bucket, fx-variance schedule with invoice-date, period-end, and realisation-date rates and the resulting fx gain or fx loss GL entry, Section 195 TDS workflow on overseas commission with Form 15CA/15CB draft, and a consolidated export receivables aging bucket with realisation gap flag. The pack feeds the year-end statutory audit disclosure on foreign currency monetary items, the transfer-pricing report where the US importer is a related party, and the Section 65 GST audit on the zero-rated supply refund claim.

### Cold-Chain 3PL Reconciliation for Dairy and Frozen FMCG

Source: https://www.terra-insight.com/insights/cold-chain-3pl-fmcg-reconciliation-dairy-frozen/

- **Problem:** Indian dairy and frozen FMCG brands run their outbound cold-chain through contracted 3PL operators like Snowman Logistics and Coldex, incurring per-pallet-day storage charges, per-consignment fixed handling, reefer line-haul, and ancillary charges. The 3PL raises consolidated invoices 15 to 45 days after billing periods close, while the shipper's despatch ledger, ASN/GRN register, temperature-excursion log, and QC-reject register live in separate systems. Temperature-deviation claims (SLA breaches beyond FSSAI Schedule 4 Part V bands) and spoilage claims (QC-reject entries) both flow into 3PL cost recovery but require different evidence chains. Section 393(1) Sl. 4 code 1023 TDS at 2% sits on every 3PL invoice, and PLISFPI scheme beneficiaries must certify incremental sales net of unrecovered spoilage — leaving the year-end 3PL payable and spoilage recovery over- or under-stated by 8 to 22 percent of gross freight spend without structured reconciliation.
- **Logic:** Build a per-billing-period 3PL invoice register keyed by 3PL vendor code, storage chamber, temperature band, and consignment ID. In parallel, aggregate the despatch ledger by consignment with ASN, GRN, and shipped units. Match every invoice line to a despatch or a chamber occupancy day, then overlay the temperature-log excursion register keyed by lane and time-window to surface SLA breaches. Match each QC-reject register entry to its root-cause classification (SLA breach recoverable vs brand-borne) and quantify the recoverable claim at contract rate. Apply Section 393(1) Sl. 4 code 1023 TDS at 2% on invoice value net of GST for non-Individual/HUF 3PLs, code 1001 at 1% for Individual/HUF. Cross-foot the closing 3PL payable to invoice-in-transit plus SLA and spoilage credit receivable before month-end close.
- **Config:** Vendor master with 3PL legal form (Company / LLP / Partnership / Individual / HUF) and PAN driving TDS code assignment; contract master with per-pallet-day rate per temperature band, per-consignment fixed handling, reefer lane rate card, and SLA temperature bands per product category; despatch ledger feed from SAP or ERP with ASN, GRN, consignment ID, product batch, units; temperature-log data-logger feed with lane, chamber, timestamp, reading; QC-reject register feed with reject reason code, unit count, batch, and root-cause classification; SLA breach detection rule (excursion beyond band for grace window); spoilage claim quantification rule; Section 34 CGST credit-note linkage; PLISFPI net-eligible-sales computation.
- **Output:** A month-end cold-chain 3PL reconciliation pack: opening 3PL payable, period invoice value gross and net of TDS, period SLA-credit accruals, period spoilage-credit accruals, period spoilage brand-borne, TDS deposited under code 1023 / 1001, and closing payable — reconciled to the AP subledger and Form 26AS at 3PL PAN. Per-lane and per-chamber SLA breach summary feeds the 3PL scorecard for the next contract review. Per-consignment spoilage classification feeds the PLISFPI incremental-sales certification for scheme beneficiaries and the QC-audit pack.

### Commercial Card Billed at Consumer Rate (or Vice Versa): MDR Audit Path

Source: https://www.terra-insight.com/insights/commercial-card-billed-consumer-rate-mdr-india/

- **Problem:** B2B SaaS companies, enterprise services merchants, and hotel chains with a high share of commercial or corporate cards in the customer mix absorb material leakage because gateways route the entire card volume to the 3% premium slab regardless of BIN tier. A consumer card billed at the corporate 3% slab costs the merchant 0.5 to 1 percentage point per affected transaction, and the gap is invisible at the blended fee column. The reverse direction — commercial card billed at the consumer slab — erodes gateway margin and triggers retroactive reclassification, which arrives as an unexplained fee true-up in a later settlement cycle.
- **Logic:** For every card transaction on the settlement file, derive card tier (consumer, commercial, premium-rewards) from the BIN against the acquirer's BIN-tier table, not from the gateway's classification field alone. Compute expected fee as contracted slab for that BIN tier and network times gross. Compare to actual fee column. Aggregate effective rate per network per card tier monthly. Flag consumer-tier effective rate above the contracted consumer slab and commercial-tier effective rate below the contracted commercial slab. Cross-reference any retroactive fee true-up against the same BIN-tier classification.
- **Config:** Acquirer BIN-tier reference table refreshed quarterly with first-six-digit ranges marked consumer, commercial, premium-rewards. Per-network contracted slab table for consumer, commercial, premium, international. BIN-tier rule in the MDR rule set per gateway and network. Per-transaction expected-fee column versus actual-fee column. Monthly effective-rate-by-tier report by gateway. Retroactive fee true-up detector that joins later-cycle adjustments back to the originating BIN classification. Recovery register feeding the merchant-fee leakage class.
- **Output:** A monthly effective-rate matrix by network by card tier showing where the consumer tier is reading above contracted consumer slab and where the commercial tier is reading below the contracted commercial slab. A per-gateway BIN-classification variance log showing transactions where the gateway tier differs from the acquirer tier. A quarterly fee true-up reconciliation aligning retroactive adjustments to BIN classification. A standing dispute register tracking BIN-tier claims filed and accepted.

### Commercial / Corporate Card MDR: The Hidden 3% Premium Slab

Source: https://www.terra-insight.com/insights/commercial-corporate-card-mdr-3-percent-india/

- **Problem:** Commercial and corporate Visa and Mastercard products carry a higher network interchange than consumer credit, and gateways route them to a 3% premium slab in every published rate card. The audit problem is that the gateway's BIN classifier silently auto-routes any BIN it tags as commercial into the 3% bucket, and the merchant settlement file rarely exposes the BIN or the tier evidence per transaction. Consumer volume routed to the commercial bucket leaks at 100 basis points per affected transaction; commercial volume routed to the consumer bucket creates a delayed retroactive fee true-up that is impossible to contest without the BIN-tier reconciliation.
- **Logic:** Per-transaction BIN-tier reconciliation joins each settlement-file row to an acquirer-provided BIN-tier schedule mapping the first six digits of the card number to one of consumer credit, commercial, corporate, premium signature, premium infinite, rewards, debit, or prepaid. The merchant's contracted slab is keyed on network plus tier and read into an expected-fee column. Actual fee is the gateway-deducted MDR. Variance equals actual minus expected with a 5 basis-point tolerance to suppress rounding. Per-network per-tier effective-rate matrix surfaces both over-charge (consumer-as-commercial) and under-charge (commercial-as-consumer) drifts on the same monthly dashboard.
- **Config:** Acquirer BIN-tier reference table refreshed quarterly. Contracted rate card object keyed on network and product tier per gateway. CARD_TIER_VARIANCE rule with directional flag (over-charge versus under-charge) and 5 basis-point slab-delta tolerance. Retroactive fee true-up detector that joins later-cycle adjustments back to originating BIN classification. GST credit-note matcher to GSTR-2B for the 18% reversal line on any recovered MDR. 90-day rolling dispute window aligned to gateway retrospective-adjustment cut-offs.
- **Output:** A per-gateway per-network per-tier effective-rate matrix updated monthly. A bidirectional variance log separating consumer-billed-as-commercial leakage from commercial-billed-as-consumer pending true-up exposure. A dispute pack export per BIN with transaction-ID-level evidence and the contracted-slab versus actual-slab calculation. A GST credit-note reconciliation schedule against GSTR-2B. A recoverable-amount running total fed into the broader merchant-fee leakage register.

### Flat Sold After Completion Certificate: Why No GST Applies (Schedule III Entry 5)

Source: https://www.terra-insight.com/insights/completion-certificate-flat-sale-no-gst-india/

- **Problem:** An Indian residential developer transitioning a project from under-construction to ready-possession must correctly identify the moment each unit's supply switches from taxable (5% CGST non-affordable / 1% CGST affordable under Notification 3/2019-CTR) to out-of-GST-scope (Schedule III Entry 5 CGST Act 2017), applying the switch on a unit-by-unit consideration-flow basis rather than a project-level cutover, and reversing proportionate ITC on unsold stock at CC date under CGST Rules 42 and 43.
- **Logic:** Anchor every sale to two date fields — the CC (or first-occupation) date from the municipal-authority portal, and the consideration-received date from the bank statement. For each unit, classify the sale as Schedule III (entire consideration post-CC) or under-construction (any consideration pre-CC); apply 5%/1% only where under-construction. On CC date, compute the exempt-to-total carpet-area ratio for the project, reverse that fraction of cumulative ITC under Rule 42/43 in the CC-month GSTR-3B, and true-up in GSTR-9.
- **Config:** Project master keyed by RERA registration + municipal approval file number with CC date, OC date, competent-authority reference; unit master with carpet area, agreement date, agreement value, CC status at agreement, first-consideration date, last-consideration date; consideration receipt log tied to bank statement credit with buyer PAN and 26QB reference; ITC reversal register capturing cumulative ITC claimed on inputs/services/capital goods, carpet-area-based reversal ratio, GSTR-3B period, GSTR-9 true-up amount.
- **Output:** A unit-level GST classification register showing Schedule III units and under-construction units with the CC date and consideration flow evidence per unit; a monthly GST invoice register reconciled to GSTR-1 with the taxable-vs-exempt split; a CC-month ITC reversal working paper tying Rule 42/43 reversal to unit inventory list and cumulative ITC ledger; an annual GSTR-9 true-up pack tying the reversal to closing unsold stock.

### Concurrent Audit of Banks and NBFCs in India

Source: https://www.terra-insight.com/insights/concurrent-audit-bank-nbfc-india/

- **Problem:** RBI mandates concurrent audit coverage of 60 percent of advances and deposits at public sector banks and 50 percent at private banks; NBFC-Upper Layer and large NBFC-Middle Layer entities follow the Scale-Based Regulation framework. Output is a monthly report to the Audit Committee covering credit, operations, treasury, KYC/AML, statutory dues, and revenue leakage.
- **Logic:** Coverage is allocated to large branches, forex branches, risk-rated branches, treasury, central processing units, and data centres. A sampling matrix scopes every high-value transaction and a percentage of low-value transactions each month. Revenue leakage is quantified across interest under-charging, fee under-recovery, charge omission, commission gaps, and forex margin under-recovery.
- **Config:** Engagement coverage matrix mapped to RBI percentage requirements, monthly sampling plan keyed to transaction size bands, focus-area checklist per RBI directive, revenue leakage recomputation worksheet, and Audit Committee reporting template with risk rating and action tracker.
- **Output:** Monthly concurrent audit report to the Audit Committee, quantified revenue leakage finding per month, KYC/AML and statutory compliance flags, NPA migration alerts, and an action tracker that closes the loop on prior observations.

### Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs

Source: https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india/

- **Problem:** RBI's Concurrent Audit Master Direction requires daily 100% verification of suspense, nostro, clearing, settlement, and NACH return-file reconciliations at high-risk branches and NBFCs in Scale Based Regulation upper and middle layers. Items aged beyond 6 months must be reported to the Audit Committee with 100% IRAC provisioning past 1 year.
- **Logic:** Daily reconciliation runs at T-morning: previous day's closing position is matched to current day's opening for every clearing, nostro, and suspense account. Nostro balances are matched to SWIFT MT940 :62F: closing. NACH return files (received T+1 to T+2 from NPCI) are matched against presentation file by UMRN, with return codes classified (01 retry, 20 NPA risk, 25 collections escalation).
- **Config:** Daily cut-off scheduler, UMRN-keyed NACH matcher with return-code classifier, suspense aging buckets (7, 30, 90 days), and SBR-tier NBFC scope extension.
- **Output:** Daily concurrent-audit memo on reconciliation completeness, aging list of suspense items for branch head escalation, nostro confirmation aligned to MT940, and 100% IRAC provisioning evidence for items past 1 year.

### Consignment Stock and Vendor-Managed Inventory Reconciliation for Indian Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india/

- **Problem:** Consignment-stock and vendor-managed inventory arrangements at Indian OEMs defer the supplier's GST invoice from dispatch to consumption — stock moves to the OEM premises under Rule 55 challan without GST and without a Section 31 invoice, ownership stays with the supplier, and the invoice attaches to the consumption event when the OEM pulls from the consignment store or the VMI bin; the operational discipline must close three loops (Rule 55 dispatch to OEM GRN, OEM consumption report to supplier invoicing, ageing-of-on-site stock to consumption velocity) and must guard against the deemed-supply risk on stock that sits beyond a six-month operational threshold without consumption; on a typical fastener supplier holding ₹1.8 crore of average VMI inventory at a Bajaj Chakan dock across 240 SKUs, even a small share aging past the six-month line can crystallise ₹3-5 lakh of deemed-supply GST exposure plus the Ind AS 115 revenue-recognition timing question on slow-moving SKUs.
- **Logic:** Stamp every Rule 55 consignment-or-VMI dispatch with destination (OEM consignment store / VMI bin location), SKU code, dispatched quantity, supplier's inventory tag remaining on the goods through dispatch; track the running on-site stock per SKU per location with days-since-last-consumption and ageing buckets (0-30, 31-60, 61-90, 91-180, 181-365, 365+); ingest the weekly OEM consumption report by SKU and reconcile against the supplier's on-site stock model; trigger the Section 31 GST invoice on the agreed cadence (typically monthly aggregation of weekly consumption); recognise Ind AS 115 revenue on the consumption event; surface ageing-past-six-months candidates for replenishment-pause, return-to-supplier under Rule 55 reverse leg, or explicit consumption acknowledgement to close the deemed-supply exposure window.
- **Config:** OEM customer master with consignment-store and VMI-bin location codes; SKU master with VMI minimum-maximum bin levels, agreed unit price, GST rate, Ind AS 115 control-transfer policy (consumption); Rule 55 dispatch challan series for consignment-and-VMI movement; weekly OEM consumption report ingest with SKU-level opening, replenishment, consumption, closing; monthly invoicing engine with Section 31 invoice trigger on aggregated weekly consumption; ageing model with six-month operational safe-harbour threshold; deemed-supply provisional accrual policy for stock past the threshold; replenishment-pause and replenishment-acceleration triggers.
- **Output:** A daily on-site stock position per OEM per SKU with days-since-last-consumption and ageing-bucket flags; the weekly OEM consumption reconciliation pack tying OEM consumption to supplier replenishment to supplier invoicing; the monthly Section 31 invoice generation queue with SKU-level consumption aggregation; the deemed-supply ageing register flagging SKUs past the operational threshold with provisional accrual entries; the Ind AS 115 revenue-recognition log per consumption event; and a board-visible consignment-and-VMI dashboard by OEM and SKU family.

### Coromandel International NPK Complex NBS Claim Reconciliation

Source: https://www.terra-insight.com/insights/coromandel-international-npk-complex-nbs-claim-reconciliation/

- **Problem:** An illustrative Coromandel International-scale NPK complex fertilizer manufacturer selling 3.5 lakh MT per month across 21 notified NPKS grades — Gromor 20-20-0-13, Gromor 14-35-14, Godavari 16-20-0-13, 10-26-26, 12-32-16 and the rest of the portfolio — must reconcile grade-wise plant despatch and retail sales, an independent Fertilizer Control Order nutrient composition audit per lot, the weekly e-Urvarak subsidy claim workbook keyed to Aadhaar-biometric retail sale, the Department of Fertilizers sanction letter, and the DBT credit into the manufacturer's designated bank account — alongside a Section 54(3) inverted-duty refund cycle on 5 percent NPKS output against 18 percent packaging and 12 percent logistics inputs, and a Section 8 Sl. 8 code 1031 (Section 194Q) TDS obligation on raw-material procurement (rock phosphate, muriate of potash, ammonia, sulphuric acid) that routinely crosses the Rs 50 lakh per-supplier annual threshold. Manual grade-wise reconciliation across 21 grades and 70 lakh bag-level authenticated retail sales per month loses per-lot subsidy accrual, under-reports the Rule 89(5) refund base, and mis-classifies raw-material TDS across suppliers.
- **Logic:** Build a grade master with the FCO-mandated N-P-K-S percentage for each of the 21 NPKS complex grades, tie every plant despatch batch to its FCO sampling report and its grade code, and carry the per-bag nutrient content as an immutable attribute to the retail-sale event captured on e-Urvarak. Ingest the weekly retail-sale extract from iFMS by retailer by grade by bag, compute per-bag subsidy at (N kg × notified N-rate) + (P kg × P-rate) + (K kg × K-rate) + (S kg × S-rate) for every bag, aggregate by grade and by retailer for the claim week, and generate the signed claim workbook for iFMS upload. Reconcile the uploaded claim against the DoF-side extract, resolve any query cycle before sanction, and match the sanction letter value to the claim workbook value. Match the DBT bank credit to the sanction letter net of any deduction. Extract the packaging input register (HDPE woven bags at HSN 6305, PE liners at HSN 3923, printed labels at HSN 4911) and the eligible logistics input register (GTA at 12 percent, rail freight at 5 percent) and feed the Rule 89(5) refund workbook under the Notification 14/2022 amended formula, excluding input services and capital goods from Net ITC. Apply Section 8 Sl. 8 code 1031 (194Q) TDS on raw-material invoices above the Rs 50 lakh per-supplier annual threshold, remit to TRACES, and reconcile against the supplier's Form 26AS.
- **Config:** Grade master with grade code (Gromor 20-20-0-13, Gromor 14-35-14, Godavari 16-20-0-13, 10-26-26, 12-32-16, and the other 16 grades), FCO-mandated N-P-K-S percentages, and bag-level nutrient content; NBS rate schedule with the DoF-notified annual per-kilogram rate for each of the four nutrients (N, P, K, S), versioned by effective date; retailer master with retailer code, iFMS registration ID, e-Urvarak PoS terminal ID, and address; plant despatch batch master with batch code, grade, tonnage, FCO sampling report reference, and lot rejection flag if composition failed; iFMS retail-sale extract feed per week; DoF sanction letter register; DBT bank credit feed from the manufacturer's designated bank account; packaging input register with HSN 6305, 3923, 4911, and other packaging materials at 18 percent input GST; logistics input register split between blocked-credit road freight, eligible-credit GTA at 12 percent, and rail freight at 5 percent; raw-material supplier master with PAN, GSTIN, and aggregate FY procurement value flag for the Rs 50 lakh 194Q threshold crossing.
- **Output:** A monthly grade-wise NBS claim and refund reconciliation pack: plant despatch and retail-sale tally by grade by lot, FCO composition audit exclusions by lot, weekly e-Urvarak claim workbook by retailer by grade by week for the month, DoF sanction letter reconciliation with any deduction flagged, DBT bank credit reconciliation against sanction letter, Section 54(3) Rule 89(5) inverted-duty refund draft with input services and capital goods excluded from Net ITC per the amended formula, GST RFD-01 filing base, and Section 8 Sl. 8 code 1031 (194Q) TDS reconciliation on raw-material procurement above the Rs 50 lakh per-supplier annual threshold. Grade-level margin walk from MRP realised at retail to DoF NBS reimbursement funds the manufacturer's operating margin communication to management and the board.

### Cost Audit under Section 148 for Auto-Component Manufacturers

Source: https://www.terra-insight.com/insights/cost-audit-section-148-auto-component-manufacturer-india/

- **Problem:** Cost audit under Section 148 of the Companies Act 2013 is a separate statutory regime from financial audit applicable to auto-component manufacturing as a regulated sector under the Companies (Cost Records and Audit) Rules 2014. The applicability test, CRA-1 cost records maintenance, CRA-2 cost auditor appointment, CRA-3 cost audit report, and CRA-4 XBRL filing run on a different calendar with a different scope than the statutory financial audit. Cost-audit-specific data — capacity utilisation, normal vs actual capacity, yield ratios, abnormal loss, per-product margin, related-party transfer pricing — is operational rather than financial and requires a separate data discipline at the manufacturer.
- **Logic:** Determine cost-audit applicability annually based on turnover thresholds (₹35 crore cost records, ₹50 crore aggregate plus ₹25 crore individual product for regulated sectors). Maintain CRA-1 cost records continuously through the year — per-product cost of production, per-cost-centre overhead allocation, per-process yield, per-furnace and per-machine-line capacity utilisation, abnormal loss with cause analysis, related-party pricing. Appoint cost auditor under CRA-2 within 30 days of Board approval. Receive CRA-3 cost audit report by 180 days from FY close. File CRA-4 XBRL within 30 days of report receipt.
- **Config:** Annual applicability checker keyed to turnover thresholds. Product master with CETA tariff heading and regulated-sector flag. Cost-centre master per furnace, per machine line, per assembly station. Normal-capacity baseline per cost centre updated annually. Yield-standard per process updated annually. Overhead allocation matrix per cost centre. Abnormal-loss capture per process with cause taxonomy. Related-party transaction register with arm's-length pricing reference. CRA-2 appointment filing calendar. CRA-3 report receipt tracker. CRA-4 XBRL filing calendar.
- **Output:** An annual cost-audit applicability conclusion with documented threshold check, a CRA-1 cost records file maintained continuously through the year with per-product cost of production, per-cost-centre capacity utilisation, per-process yield variance, abnormal loss with cause, and related-party pricing. A CRA-2 appointment filing on MCA. A CRA-3 cost audit report received from the cost auditor. A CRA-4 XBRL filing on MCA. An audit-defensible trail linking the cost-audit data to the underlying production records and financial books.

### Cotton Bale Quality Testing and CCI Lab Recovery Reconciliation

Source: https://www.terra-insight.com/insights/cotton-bale-quality-testing-cci-recovery-reconciliation/

- **Problem:** A vertically integrated ginning-plus-spinning facility procuring cotton bales through CCI MSP channel must reconcile the HVI (High Volume Instrument) lab test report per bale against the CCI grade certificate that maps HVI parameters to grade code and premium/discount percentage; against the CCI tax invoice line-item premium/discount computed against the notified FAQ MSP; against the mill's inward gate register (bale count and gross weight); against the lab-fee outflow ledger at the original tender and the lab-fee recovery credit on the next lot's invoice. Manual reconciliation across the six-document trail typically loses per-bale HVI lines, mis-maps grade certificates to invoices when lot numbers repeat across seasons, and under-recovers lab fees when the next lot ships to a different depot — leaving crores in ITC exposure and un-recovered lab charges at year-end audit.
- **Logic:** Build a bale-lot master keyed by CCI lot number and season year. Ingest the HVI lab report as a per-bale parameter grid (UHML in mm, micronaire, strength in g/tex, uniformity ratio, Rd, +b) and match every bale against the CCI grade certificate that carries the same lot reference. Compute expected premium or discount per bale from the CCI grade certificate against the notified FAQ MSP for the season, and reconcile against the invoice line item. Track the per-bale lab-fee outflow at the original grading tender, and match against the lab-fee recovery credit on the next-lot invoice by lot reference. Reconcile the inward gate register (bale count and gross weight at receipt) against the invoice quantity and the CCI grade certificate. Chain every document to the lot reference and surface breaks (missing HVI line, grade-to-invoice premium mismatch, un-recovered lab fee, gate-receipt shortfall) as exceptions.
- **Config:** Bale-lot master with CCI lot number, season year, source channel (CCI MSP versus private-market versus imported), FAQ MSP rate for the season, and reference HVI parameter thresholds (fibre length, micronaire band, strength floor); HVI parameter grid per bale from the lab report; grade certificate template mapping HVI parameters to grade code and premium/discount percentage; invoice ingestion template with base MSP, premium line, discount line, GST rate (typically nil or 5 percent for raw cotton per current CBIC notification), and total; lab-fee outflow ledger keyed by original tender-lot and lab-fee recovery credit template on next-lot invoice; inward gate register with bale count and gross weight; Section 16 CGST ITC eligibility flags (invoice received, goods received, supplier return furnished, 180-day payment window) per invoice; Section 34 CGST credit-note deadline tracker for post-supply quality claims.
- **Output:** A per-lot reconciliation pack: HVI parameter grid summarised against grade certificate (bale-wise match rate); invoice line-item premium/discount tie-out against expected from grade certificate; inward gate register quantity and weight variance flagged; lab-fee outflow ledger balance against recovery credit expected on next lot; GST ITC eligibility status per invoice; any post-supply quality claims tracked against the Section 34 credit-note deadline. Season-close pack summarises total procurement value (base MSP plus net premium minus net discount), net lab-fee recovery position (outflow paid at grading minus recovery credit received on subsequent lots), ITC claimed against GSTR-2B tally, and residual quality claims pending credit-note settlement — audit-ready before the year-end statutory audit begins.

### Cotton Supply Chain Reconciliation for Textile India

Source: https://www.terra-insight.com/insights/cotton-supply-chain-reconciliation-textile-india/

- **Problem:** A mid-tier Coimbatore or Erode spinner-weaver buying cotton bales from a mix of CCI MSP procurement and ginner spot supply, and running grey fabric through a network of Udyam-registered powerloom weaver-suppliers, must reconcile four interlocking layers on every quarterly close: procurement-source split (CCI vs ginner) at the bale-lot level; bale quality parameters (fibre length, micronaire, strength, trash) driving premium/discount over the MSP base; the Section 43B(h) 45-day payment clock at every downstream Udyam-flagged supplier; and the 3× RBI-rate interest computation on any overdue invoice. Missing the clock on a single ₹32 lakh powerloom weaver bill disallows the full bill amount as expenditure in the FY it was booked, plus loads a non-deductible taxable interest into the supplier's hands — the buyer loses the deduction, the supplier still pays tax on the interest.
- **Logic:** Ingest the CCI auction record and every ginner spot invoice, decompose each line into base rate (MSP-linked or spot-market) × quality-parameter adjustment × quantity, and chain the bale-lot ID from procurement into the gin-to-spin-to-weave production register. On the payables side, tag every vendor with a Udyam number, classification (Micro / Small / Medium — 43B(h) only fires for Micro and Small), and agreed payment terms (in-writing agreed date up to 45 days, or default 15 days where no written agreement exists). On every invoice, calculate the Section 15 MSMED due date, run an ageing clock at 30, 40, and 44 days, and hard-flag any invoice not paid by day-45. For overdue invoices, compute Section 16 interest at three times the RBI bank rate compounded monthly from due-date-plus-one to actual payment date, capture the disallowance flag on the buyer's tax schedule, and reconcile against the supplier's supplementary interest invoice.
- **Config:** Vendor master with Udyam number, classification (Micro / Small / Medium), Udyam certificate copy, agreed payment terms (with copy of written agreement where present), and a 43B(h)-in-scope flag; CCI portal feed for auction lot and MSP-linked base rate lookups; bale quality master for premium/discount grid over MSP base (fibre length in 2 mm bands, micronaire 3.5-5.0 range, strength g/tex grid, trash % grid); procurement-source split flag on every purchase order (CCI-MSP / ginner-spot / broker-aggregated); Section 15 payment clock (default 15 days or agreed date up to 45 days) on the payables ageing; Section 16 interest rate feed pulling the current RBI bank rate × 3; disallowance schedule feeding the tax return of the buyer with the sum of 43B(h)-disallowed expenditure for the FY; supplier interest invoice reconciliation to close the loop on the taxable-in-supplier's-hands interest income.
- **Output:** A month-end cotton procurement and MSME payment reconciliation pack: procurement-source split by bale-lot with MSP-linked base × quality adjustment × quantity for CCI lots and spot-rate × quality adjustment × quantity for ginner lots; Udyam-flagged vendor list with classification and agreed payment terms; open-invoice ageing bucketed at 0-30 / 31-40 / 41-44 / 45+ days with the 45+ bucket carrying the 43B(h) disallowance flag; per-overdue-invoice Section 16 interest computation with days-overdue, bank-rate applicable, and compounded interest amount; a disallowance schedule feeding the buyer's income-tax return and Form 3CD Clause 22 disclosure; and a supplier interest invoice reconciliation confirming the supplementary invoice was received and the taxable interest amount was captured on the supplier's books.

### Courier and Last-Mile Reconciliation for Indian E-commerce and D2C Brands

Source: https://www.terra-insight.com/insights/courier-last-mile-reconciliation-india/

- **Problem:** A D2C brand with ₹6.8 Cr annual courier spend across Blue Dart, DTDC, DHL Express, India Post and 3-5 D2C-focused partners reconciles per-AWB tariff against partner-specific structures (per-shipment vs slab vs zone), weight-dispute resolution within 14-day window with volumetric-weight upgrade, OTP-delivery verification tied to COD remittance lifecycle on T+3 to T+7 SLA, Section 393(1) Sl. 6(i) codes 1023/1024 TDS withholding at 1 or 2 percent with 194C(6) nil-deduction declaration framework, Section 52 CGST TCS credit where aggregators are used, and Section 9(5) classification scoping where applicable. Failure on any rail cascades — weight-dispute losses compound, COD remittance lag distorts working capital, TDS mis-classification creates assessment risk.
- **Logic:** Build a per-AWB master keyed by courier partner, service tier, declared weight, volumetric L×B×H, declared value, origin pin and destination pin. Apply partner-specific tariff card per slab per zone with rate-card version on booking date. Resolve volumetric-weight disputes within 14-day window with one of three outcomes (accepted, contested-write-off, unresponded-billed). Track OTP-delivery confirmation per AWB and tie to COD remittance file from courier on T+3 to T+7 contracted SLA. Deduct Section 393(1) Sl. 6(i) codes 1023/1024 TDS at 1 percent (individual/HUF) or 2 percent (company/firm) on courier invoice; maintain Section 194C(6) declaration register for small-transporter PAN-declarations. Classify SAC 996819 standard courier invoices at 18 percent forward charge; separate Section 52 CGST TCS credit where aggregator-rolled invoices applicable.
- **Config:** Courier partner master with tariff card per slab per zone per service tier and rate-card version; AWB master keyed by partner, declared weight, volumetric, origin and destination; weight-dispute register with 14-day window and outcome flag; OTP-delivery confirmation per AWB tied to COD remittance file; COD ageing per courier per delivery date against contracted T+X SLA; Section 393(1) Sl. 6(i) codes 1023/1024 TDS challan ledger with 194C(6) declaration register; Section 52 CGST TCS reconciliation per aggregator with GSTR-2B credit tracking; SAC 996819 18 percent ITC reclamation register.
- **Output:** A per-AWB tariff reconciliation with partner-specific zone and slab match, weight-dispute outcomes by AWB, OTP-confirmation vs COD remittance reconciliation with ageing per courier, Section 393(1) Sl. 6(i) codes 1023/1024 TDS challan compliance log with 194C(6) declaration validation, monthly SAC 996819 ITC reclamation and Section 52 CGST TCS credit roll-up to GSTR-3B, quarterly 26Q filing with partner-wise TDS deducted, and a partner-performance scorecard with weight-dispute rate, OTP-success rate and COD-remittance-lag KPI.

### Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements

Source: https://www.terra-insight.com/insights/counterparty-spread-analysis-statements/

- **Problem:** Fabricated bank statements are often constructed with deliberate variety in counterparty names to appear realistic. However, the resulting distribution — many counterparties at similar frequencies — is structurally unlike genuine accounts, which show strong concentration in a few dominant payees and a long tail of occasional transactions.
- **Logic:** Compute the counterparty frequency distribution across all transactions. Measure concentration: what share of transactions involve the top 5 counterparties? What is the ratio of unique counterparties to total transactions? Genuine accounts typically show the top 5 counterparties accounting for 30–60% of transactions; fabricated accounts show a flatter distribution with no dominant names. Also check for the absence of expected Indian consumer/business counterparties given the account type.
- **Config:** Calibrate for account type (salary vs business current vs MSME). Exclude self-transfers and ATM entries from counterparty analysis. Apply minimum transaction count threshold (50+ transactions for meaningful distribution analysis). Cross-reference against known Indian consumer platform names for consumer account validation.
- **Output:** Counterparty concentration metrics (top-5 share, unique counterparty ratio), distribution classification (concentrated / normal / unusually flat), and a flag for absence of expected counterparties given account type, presented in the fraud signals section of the analysis report.

### Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes

Source: https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india/

- **Problem:** Form 16A from March 2026 uses legacy section codes, while Form 131 from April 2026 uses new payment codes. Finance teams must match records across both eras without losing credits or triggering duplicate tax payments.
- **Logic:** Identify every TDS receivable and payable record that spans the April 1, 2026 cut-over by financial year. Build an equivalency table between legacy section codes and Income Tax Act 2025 payment codes. Treat paired entries as equivalent matches on vendor, amount, and period. Route unmatched items to a cross-era review queue with a clear era flag.
- **Config:** Three-year cross-era window from April 1, 2026 through March 31, 2029 (FY 2025-26 correction cut-off). Dual-mode reconciliation enabled by default during transition. Era-flagged exception queue for PAN mismatches and amount variances.
- **Output:** Reconciled TDS receivable ledger spanning both eras, era-flagged exceptions, cross-era variance reports for audit, and protected credit claims for income tax returns.

### Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why

Source: https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements/

- **Problem:** Cryptocurrency exchange transactions in a bank statement indicate capital allocation to a volatile asset class, potential income that may be non-recurring, and PMLA compliance obligations for lenders. Manual statement review misses exchange transactions that route through non-obvious payment entity names.
- **Logic:** Match transaction descriptions against exchange names, wallet service names, and trading platform references in the cryptocurrency category. Record transaction count, total debit (investments), total credit (sale proceeds or withdrawals), and top five matched terms. Flag large credits identified as crypto sale proceeds for income treatment review.
- **Config:** Enable for NBFC, HFC, and digital lending underwriting. Include international exchange payment entity names for complete coverage. Cross-reference with suspicious patterns detection for P2P or structuring indicators in crypto-adjacent transactions.
- **Output:** Cryptocurrency risk section in the credit report with transaction count, total debit, total credit, top five matched terms, and an income recurrence assessment flag for large credit entries.

### CUM Quantity Drift: The Auto-Component Reconciliation Problem Nobody Talks About

Source: https://www.terra-insight.com/insights/cum-quantity-drift-auto-component-india/

- **Problem:** Auto OEM scheduling agreements run on cumulative quantities reset year-start or model-start. A single dropped, duplicated or mis-quantity ASN permanently shifts the supplier's CUM-shipped out of step with the OEM's CUM-received. Each later call-off looks normal in isolation, so the drift goes undetected for weeks while output GST, ITC, Section 393(1) Sl. 8(ii) TDS base and year-end audit positions silently move out of agreement.
- **Logic:** Run a four-way CUM match per part and ship-to point on every cycle: 862 CUM-required vs 856 CUM-shipped (inside delivery tolerance) vs OEM GRN CUM-received vs periodic tax-invoice billed quantity. Compare CUM-shipped against CUM-received continuously, not just last shipment to last receipt. Raise a standing CUM-drift exception the moment the two diverge, carry it as an open item until a joint correction is agreed, and re-anchor at every reset marker. Tie the billed quantity to confirmed-received quantity, not raw ASN, so GST output and Section 393(1) Sl. 8(ii) TDS base do not inherit the drift.
- **Config:** Part master keyed by OEM plant code, scheduling-agreement number and ship-to point, with delivery tolerance and reset marker (year-start / model-start) per agreement. EDI map for 862 (CUM-required, firm-from date), 856 (CUM-shipped), and OEM GRN (CUM-received). Periodic tax-invoice generator that bills confirmed-received quantity per window. Standing CUM-drift exception queue with originating-ASN traceability. Period close-out reconciliation pack triggered at month-end, quarter-end, year-end (1 April reset) and model-end.
- **Output:** A per-part rolling CUM reconciliation showing CUM-required vs CUM-shipped vs CUM-received vs billed quantity, with drift flags the day they appear; an originating-ASN trace for every drift line; a periodic tax-invoice quantity-reconciliation pack tying invoiced to confirmed-received; a reset re-anchor record at year-start and model-start; and a cross-period close-out exception register routed to AR, GST and TDS leads.

### Customs BCD on Cotton + MMF Textile Import Reconciliation

Source: https://www.terra-insight.com/insights/customs-bcd-cotton-mmf-textile-import-reconciliation/

- **Problem:** A Bhilwara or Ludhiana suiting mill importing raw wool from Turkey and polyester staple from China must reconcile every Bill of Entry against four independent data feeds — the CIF invoice from the foreign supplier, the customs house agent (CHA) bill breaking down BCD, AIDC, Social Welfare Surcharge, and IGST paid at port, the freight-forwarder invoice covering ocean freight, inland transport, and port handling, and the ICEGATE-populated GSTR-2B entry that unlocks the IGST credit in the following month's GSTR-3B. A single mismatched BoE reference between CHA and GSTR-2B leaves the IGST credit unclaimed for the period; a wrongly captured HSN routes the shipment through a stale duty rate; an ADD notification effective from a mid-month date changes the incidence for shipments cleared before or after that date. Manual spreadsheets across import cells, treasury, and GST teams typically leak 2 to 5 percent of IGST credit annually and mis-state landed cost on high-value shipments.
- **Logic:** Build a BoE-anchored reconciliation register keyed by BoE number and BoE date. Ingest the CIF invoice from the supplier, the CHA bill of costs, the freight-forwarder invoice, and the ICEGATE BoE PDF for every commercial import. Match each BoE to its GSTR-2B Table 3.5 (Import of Goods) entry by BoE number and BoE date; where the BoE appears in the importer's register but not in GSTR-2B, raise a CHA follow-up. Compute the landed cost per shipment from CIF plus BCD plus AIDC plus Social Welfare Surcharge plus ADD (where applicable) plus CHA charges plus freight-forwarder charges — excluding IGST which is recoverable. Feed the recoverable IGST amount to the GSTR-3B ITC claim in the correct month. Maintain a date-versioned and origin-versioned HSN-to-duty-rate table so that the BoE for any shipment applies the rate in force on the Bill of Entry date for the actual country of origin.
- **Config:** Supplier master with foreign supplier name, country of origin, INCOTERM (typically CIF for landed-basis imports); HSN master with date-versioned BCD, AIDC, Social Welfare Surcharge, and IGST rates for HS 5101 (raw wool), HS 5201 (raw cotton), HS 5401 (synthetic filament), HS 5501/5503 (synthetic staple); ADD notification table with HSN, origin country, effective date, sunset date, and rate; CHA master with GSTIN, PAN, and TDS payment code 1023 (services with material supplied) or 1024 (services without) for CHA service invoice TDS; freight-forwarder master with GSTIN, PAN, and TDS payment code 1002 (other resident contractor 2%) or 1014 (freight for goods carriage) as applicable; Advance Authorisation and EPCG scheme flag per import where duty-free import is claimed against export obligation, with bond register reference and export obligation tracking; landed-cost fair-value settings for inventory capitalisation under Ind AS 2.
- **Output:** A month-end BoE reconciliation pack with every commercial import of the period: BoE number and date, port of clearance, foreign supplier and country of origin, HSN, CIF value in USD and INR, BCD paid, AIDC paid, Social Welfare Surcharge paid, ADD paid (where applicable), IGST paid, CHA charges, freight-forwarder charges, landed cost, and IGST credit availability in GSTR-2B. The pack cross-foots the GSTR-3B ITC claim in Table 4(A)(1) to the sum of GSTR-2B Import of Goods entries; it flags every BoE in the importer register that has not appeared in GSTR-2B by the return due date for CHA follow-up; and it provides the auditable landed-cost roll-forward that feeds inventory valuation and the annual statutory audit. IGST credit leak rate falls from a typical 2 to 5 percent under manual tracking to a materially lower single-digit percentage under automated BoE-to-GSTR-2B matching.

### Customs Duty SCN Matching for Indian Electronics Manufacturing

Source: https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india/

- **Problem:** EMS companies importing high-value electronics components face customs SCNs (Show Cause Notices) on assessable-value disputes, HS classification challenges (8536 vs 8537 vs 8542), exemption misuse claims, additional customs duty plus IGST short-paid arguments, and SVB provisional vs final assessment cycles — with reconciliation against bills of entry, TR-6 challans, EDD payments, and the refund-with-interest mechanism under Section 27 of the Customs Act.
- **Logic:** Hold a bill-of-entry register keyed by part number, declared HS, assessable value, BCD, IGST, EDD; tag every SVB-flagged related-party import as provisional with the SVB case reference; build a parallel SCN ledger with notice reference, demand value, contested ground, response status, and contingent liability classification; tie refund claims under Section 27 to the original challan and adjudication / appellate order; track Section 129E pre-deposit on appeal.
- **Config:** Customs configuration with bill-of-entry register, HS code master with related-party flag, SVB provisional assessment tracker, SCN register with adjudication / appellate stage tag, Section 27 refund claim builder, Section 129E pre-deposit tracker, GSTR-2B IGST reconciliation against bill of entry.
- **Output:** A monthly customs close where every bill of entry ties to its TR-6 challan and the IGST entry in GSTR-2B, SVB-flagged provisional assessments roll up with EDD aging dashboard, SCN provisions reflect the current adjudication stage and contingent liability classification, Section 27 refund queue tracks dropped SCNs and finalised provisional assessments, and Section 129E pre-deposits are mapped to active appeals.

### D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts

Source: https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india/

- **Problem:** D2C apparel and beauty brands run two parallel settlement flows — 3PL cash remittance for COD orders (T+5 to T+10 from delivery, net of RTO and COD handling charges) and gateway payouts for prepaid (T+1 to T+2, net of MDR) — and collapsing them into a single revenue line hides RTO leakage, commission errors, unremitted cash, and working-capital lag that commonly runs 20–30% on COD-heavy categories.
- **Logic:** Maintain two independent receivable sub-ledgers: gateway receivable matched against Razorpay, PayU, or Cashfree payouts, and 3PL receivable matched against Delhivery, Shadowfax, or Shiprocket remittance. Match at AWB level for COD and order-ID level for prepaid. Reverse RTO provisional revenue, book reverse-logistics fees, and track inventory return. GST on MDR (18%) and GST on 3PL fees (18%) are booked as separate ITC claims against different expense heads.
- **Config:** Order management connector with AWB-to-order mapping, 3PL adapters for Delhivery, Shadowfax, Shiprocket, Ecom Express; gateway adapters for Razorpay, PayU, Cashfree; RTO classification rules; reverse-logistics fee schedule per 3PL; inventory return trigger to stock ledger.
- **Output:** Two reconciled sub-ledgers with AWB-level COD cash traced from delivery to bank credit, order-ID-level prepaid cash traced from transaction to payout, RTO leakage isolated, 3PL commission errors surfaced, and working capital lag quantified for board reporting.

### Daily vs Monthly Reconciliation: When Each Approach Makes Sense

Source: https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india/

- **Problem:** Monthly-only reconciliation breaks at scale: NBFCs above 1,000 daily NACH mandates, payment aggregators with RBI daily settlement obligations, and e-commerce platforms with daily seller payouts cannot wait until month-end to catch a systematic error affecting hundreds of thousands of transactions.
- **Logic:** Match frequency to data availability and risk: daily for bank and platform settlements, weekly for TDS (Form 26AS updates 3–7 days after challan), monthly for GSTR-2B (generated on the 14th). Ingest data via API or SFTP and route same-day exceptions within defined SLAs. The month-end close becomes a sign-off rather than a matching exercise.
- **Config:** Frequency-per-reconciliation-type matrix, API and SFTP bank connectors, same-day exception routing with role-based SLAs, and batched weekly TDS and monthly GSTR-2B runs.
- **Output:** Intraday visibility into settlement and bank variance, daily exception backlog below 24 hours, and a month-end close that signs off a reconciled position rather than building it from scratch.

### Dairy Inverted-Duty Refund under Rule 89(5) — Post-GST-2.0 (2026)

Source: https://www.terra-insight.com/insights/dairy-inverted-duty-refund-rule-89-5-post-gst-2-0-2026/

- **Problem:** A Kwality Ltd or Parag Milk Foods dairy processing operation with a monthly output of Rs 40 to 50 crore of packaged milk and value-added dairy products accumulates unutilised input tax credit on the credit ledger because packaging inputs (HSN 3923 plastic bottles, HSN 4819 paperboard cartons) attract 18 percent GST while the output packaged milk (HSN 0401, HSN 0403) attracts 5 percent. The Rule 89(5) refund formula caps the recoverable amount, and after Notification 14/2022 Net ITC excludes input services and capital goods — meaning dairy-cold-chain logistics services, plant depreciation, and refrigeration capital goods contribute to the accumulated ITC but do not increase the refundable amount. The 56th GST Council rate rationalisation of September 2025 must be verified per HSN before every monthly claim. Monthly Form GST RFD-01 filing must reconcile turnover of inverted-rated supply, Net ITC on inputs, Adjusted Total Turnover, and tax payable on inverted-rated supply — all sourced from GSTR-1, GSTR-3B, and the purchase register — before the two-year outer limit under Section 54(1) expires.
- **Logic:** Segregate every input invoice by HSN and by GST rate on the purchase register; tag each input as input goods, input services, or capital goods; compute Net ITC for the tax period as input tax credit availed on input goods only (post-Notification 14/2022). Segregate every output invoice by HSN and by GST rate on the sales register; compute turnover of inverted-rated supply as the aggregate value of taxable outputs where input rate exceeds output rate (packaged milk, standard curd, yogurt, buttermilk under HSN 0401, 0403, 0404). Compute Adjusted Total Turnover as total turnover in the state excluding exempt and non-GST supplies. Compute tax payable on inverted-rated supply as output GST liability on the inverted-rated turnover. Apply the amended Rule 89(5) formula: Max Refund = ((inverted-rated turnover x Net ITC) / Adjusted Total Turnover) minus (tax payable on inverted-rated supply x (Net ITC / (ITC availed on inputs + input services))). Where the formula yields a negative number, no refund arises — carry the unutilised ITC forward. Where positive, populate Form GST RFD-01 with the computed values and file within the two-year outer limit from the return due date.
- **Config:** Purchase register HSN master with GST rate flag per HSN (3923 packaging at 18 percent, 4819 cartons at 18 percent, 0403 cream input at 5 percent, and every other input HSN); input classification flag (input goods, input services, capital goods) per Notification 14/2022; sales register with HSN and output GST rate per HSN (0401, 0402, 0403, 0404, 0406 for dairy); inverted-rated supply flag per output SKU triggered where input-weighted-average rate exceeds output rate; Rule 89(5) formula engine with pre-14/2022 and post-14/2022 modes for historical reconciliation; monthly RFD-01 draft generator populating turnover of inverted-rated supply, Net ITC on inputs, Adjusted Total Turnover, and tax payable; two-year outer limit clock against Section 54(1) relevant date per tax period; 56th GST Council rate change effective date flag with per-HSN verification alert.
- **Output:** A month-end inverted-duty refund pack for the dairy processing entity: turnover of inverted-rated supply of goods (packaged milk, curd, yogurt output value) with HSN-level detail; Net ITC on inputs (goods only, excluding input services and capital goods per Notification 14/2022) with input-HSN detail; Adjusted Total Turnover per the state registration; tax payable on inverted-rated supply per GSTR-3B; Rule 89(5) Max Refund computation with the formula shown step-by-step and the input-services exclusion effect quantified; Form GST RFD-01 draft ready for electronic filing on the common portal; two-year outer limit ageing per tax period against the Section 54(1) relevant date; carry-forward register for tax periods where the formula computed a negative refund. The pack is audit-ready for the jurisdictional refund officer's Form GST RFD-02 acknowledgement and subsequent Form GST RFD-06 sanction cycle.

### Damaged Jewellery Return and Section 34 Credit Note for Jewellers

Source: https://www.terra-insight.com/insights/damaged-tampered-jewellery-return-section-34-credit-note-india/

- **Problem:** When a customer returns damaged or tampered jewellery — a chain snapped at the clasp, a ring bent out of round, a diamond chipped on the girdle — the retailer must run four coordinated reconciliations before the Section 34 statutory deadline. First, issue a Section 34 credit note under Rule 53 within the 30 November-following-FY window with the original invoice reference, the returned taxable value split by tax-rate row (3% gold, 5% making, 0.25% diamond, 18% ancillary), and the customer refund voucher. Second, amend the original GSTR-1 line and declare the credit note in GSTR-1 Table 9A/9B. Third, reduce output tax liability in GSTR-3B for the credit-note month. Fourth, reverse Rule 42 ITC under Section 17(5)(h) on components of scrapped damaged inventory, and — if the event is covered by the retailer's jewellers block or Standard Fire policy — file the insurance recovery claim separately without netting against the credit note. Retailers who process returns without this coordinated four-step run miss the November deadline, over-claim ITC on scrapped stock, or double-book insurance recovery against the customer refund.
- **Logic:** Every damaged return event triggers a state machine: return-register entry (piece, invoice reference, condition assessment) → repair-versus-scrap decision → Section 34 credit note (full or partial value, all tax-rate rows) → GSTR-1 amendment (Table 9A registered, 9B unregistered) → GSTR-3B output tax reduction → Rule 42 ITC reversal (only on scrapped, not on repair-and-restock) → insurance claim (only on covered peril) → customer refund (same payment mode, Section 269ST cash limit). Cross-reference the return register against the credit-note register at month-end; every return with a scrap outcome must have a matching Rule 42 reversal entry; every credit note must fall within the Section 34(2) window measured from the original invoice date; every insurance claim must have a peril category and a separate GL account distinct from the customer-refund account.
- **Config:** Return register with serial number, date of return, original invoice reference, piece description, condition assessment (repairable, scrappable, insured peril), refund mode; credit-note master with consecutive serial number, Section 34(2) deadline calculated from original invoice date, tax-rate row split (3% / 5% / 0.25% / 18%), GSTR-1 table target (9A registered, 9B unregistered); Rule 42 reversal calculator with per-piece component identification (making charges ITC, packaging ITC, hallmarking ITC) and Section 17(5)(h) applicability flag; insurance policy master with covered perils, excess, and claim-filing timeline; customer master with GSTIN (registered) or PAN and address (unregistered for above-threshold refunds); Section 269ST cash-refund threshold monitor.
- **Output:** A monthly reconciliation pack: return-register-to-credit-note match with 100% coverage of return events by credit-note serial numbers; Section 34 aging report showing all open returns approaching the November-following-FY deadline (60-day, 30-day, 15-day, 7-day buckets); credit-note-to-GSTR-1 declaration reconciliation by Table 9A/9B; GSTR-3B output tax reduction working per tax-rate row (3% / 5% / 0.25% / 18%); Rule 42 ITC reversal register per scrapped piece with GSTR-3B Table 4(B) mapping; insurance claim register with recovery-to-write-off reconciliation kept distinct from customer-refund flow; audit-ready evidence pack per return event (invoice, return register, credit note, refund voucher, GSTR-1 row, GSTR-3B row, Rule 42 reversal, insurance claim if applicable).

### Dairy Reconciliation in India: Fat + SNF Milk Procurement Cornerstone

Source: https://www.terra-insight.com/insights/dairy-reconciliation-fat-snf-milk-procurement-india/

- **Problem:** A district milk cooperative union running 42,000 farmers across 1,800 village dairy societies at 1.85 lakh litres of daily peak procurement must reconcile every farmer session's fat percent plus SNF percent accrual, the society-to-union daily receipt with re-tested lab variance, the union-to-federation monthly transfer invoice, Section 194C code 1001/1002 society commission TDS keyed to each society's PAN, Section 194K cooperative dividend TDS on the annual patronage bonus paid to non-society investors, and the Rule 89(5) inverted-duty refund cycle created by 5 percent packaged milk output against 18 percent packaging input GST. Manual reconciliation across three cascading hops loses per-session premium adjustments, over-states society closing balance on commission runs, and mis-attributes 18 percent packaging ITC to the wrong tax period — exposing the union to Section 73/74 GST notices at year-end audit and to Form 26AS mismatches at every society's income-tax audit.
- **Logic:** Build a farmer sub-ledger keyed on the AMC receipt from every village dairy society, expand each session accrual into the two-axis formula components (volume, base rate, fat kg times premium, SNF kg times premium), and carry the session-level fat percent and SNF percent as immutable attributes to the society-to-union receipt line. Ingest the chilling-centre re-test tally by society by day, match by weight and fat and SNF against the society's declared value, and expose variance beyond the tolerance band as a reconciliation exception on the society commission run. Aggregate society commission accruals monthly, key each society to its PAN and TDS code 1002, and generate the monthly commission run with TDS computed and remitted before the credit is passed to the society's cooperative account. Feed the federation's monthly settlement invoice against the union's own farmer plus society plus transport plus TDS accruals, and reconcile the differential against the union's operating margin line. Extract packaging input GST at 18 percent and packaged milk output GST at 5 percent from the union's or federation's GSTR-1 and GSTR-3B into the Rule 89(5) refund workbook, apply the amended formula (Net ITC excludes input services and capital goods per Notification 14/2022), and generate the GST RFD-01 filing base every month or quarter.
- **Config:** Farmer master with farmer code, village dairy society code, PAN (where filed), bank account for direct settlement, and shareholding record for patronage bonus; VDCS master with society code, GSTIN (if registered above the threshold), PAN, TDS payment code 1002, and society commission slab; district union master with union code, chilling-centre network, and pasteurisation dairy assignment; federation master with dividend and patronage-bonus register split between society holders and non-society investors; two-axis pricing schedule (base rate per litre, fat premium per kg-fat, SNF premium per kg-SNF) versioned by effective date; fat and SNF variance tolerance band per union (typically 0.1 percent absorbable as sampling variance; larger variances flagged); GSTR-1 and GSTR-3B feed for the Rule 89(5) refund workbook; e-Urvarak-analogue society commission portal feed if the union operates one; Section 43B(h) MSME flag on packaging suppliers (corrugated carton and tetra-pak converters are frequently MSME-registered).
- **Output:** A month-end multi-level dairy procurement reconciliation pack: opening balance of farmer sub-ledger by VDCS, session accruals by farmer by shift, society-to-union receipt tally with fat and SNF re-test variance, closing farmer sub-ledger balance, monthly society commission run with code 1002 TDS reconciled against the union's TDS remittance schedule, federation monthly settlement invoice reconciled against the union's own accrual base, Rule 89(5) refund draft with the amended Net ITC formula and the packaging-input invoice register mapped by tax period, and — at year-end — the cooperative dividend and patronage-bonus register split between society holders (no TDS) and non-society holders (Section 194K TDS deducted). Per-farmer premium tally supports the union's annual bonus true-up cycle and the federation's price stability communication to the general body.

### DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers

Source: https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india/

- **Problem:** DAP-2020 offset clause obligates foreign defence vendors to discharge 30%+ of contract value above ₹2,000 crore through Indian DPSU/MSME purchases, DRDO technology transfer or training, with multiplier rules (1x direct, 1.5x MSME, 1.5-3x tech transfer), DOMW annual return and audit, banked-offset draw-down at contract award, and mirror-tracking obligations at the Indian recipient — reconciled over discharge periods of 7+ years, often beyond the main contract execution.
- **Logic:** Reconcile offset obligation per contract against cumulative multiplier-adjusted discharge value, classify each discharge transaction by category (direct purchase, MSME purchase, tech transfer, training, investment) and apply correct multiplier, maintain banked-offset register with credit earned/used/lapsed status, file DOMW annual return with documentation per transaction, mirror-track at Indian recipient with offset reference on every related purchase order, manage DOMW audit cycle and disallowance remediation.
- **Config:** Contract master with MoD contract number, contract value, DAP category, offset obligation amount, discharge schedule; offset discharge ledger with transaction category, multiplier applied, gross value, multiplier-adjusted value; banked-offset register with earned/used/lapsed status and validity; DOMW annual return workflow; Indian-recipient mirror ledger with offset reference per PO; MSME-status verification process for multiplier claims; technology-transfer agreement repository.
- **Output:** A quarterly offset reconciliation dashboard per contract showing cumulative obligation, cumulative discharge (gross and multiplier-adjusted), discharge percentage against obligation, banked-credit balance and validity, DOMW annual return status with disallowance lines, Indian-recipient mirror reconciliation, multiplier-applied audit trail per transaction category, and projected discharge against contractual schedule.

### Debtors and Creditors Reconciliation: Ledger Matching Best Practices

Source: https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india/

- **Problem:** Indian AR and AP must reconcile to three counterparty records simultaneously: Form 26AS (TDS deducted by customer), GSTR-1 (GST declared), and the counterparty's GSTR-2B. Unpaid invoices older than 180 days also force ITC reversal under CGST Section 16(2)(b).
- **Logic:** Match AR by invoice, customer GSTIN, and TAN against Form 26AS and counterparty GSTR-2B. Age balances into 0–30, 31–60, 61–90, 91–180, and 181+ buckets; flag the 181+ bucket for mandatory ITC reversal. Run SA 505 balance confirmations for any debtor above ₹10 lakh and for the top ten by value.
- **Config:** Age-bucket rules linked to the 180-day ITC reversal rule, disputed-invoice flagging, counterparty GSTIN and TAN keys, and balance-confirmation workflow for top debtors.
- **Output:** A reconciled AR and AP register with age analysis, ITC reversal list, disputed-invoice subledger, and external confirmation pack for statutory audit.

### Defaulted Gold Loan Auction Surplus: Borrower Liability Not NBFC Income

Source: https://www.terra-insight.com/insights/defaulted-loan-gold-auction-surplus-borrower-liability-nbfc-india/

- **Problem:** A defaulted gold loan is auctioned under the RBI Fair Practices Code, the sale realises more than the outstanding dues, and the NBFC must reconcile auction proceeds against principal, interest, and auction costs, park the residual surplus as a borrower payable, and never let that surplus touch an income code. The reconciliation between auction proceeds, dues, borrower liability register, and general ledger is where the highest-stakes audit finding in gold-loan operations is either prevented or created.
- **Logic:** For each auctioned loan, compute the dues waterfall: outstanding principal + accrued contractual interest to auction date + documented auction costs (advertisement, assay, auctioneer commission, storage). Reconcile the auctioneer's proceeds credit against the loan account, apply the waterfall, book the residual to a per-borrower liability code, and post the corresponding entries. The four-way tie is auction proceeds → dues recovery → borrower liability → general ledger. Any variance is investigated the same day; nothing is coded as 'other income' by default.
- **Config:** RBI Fair Practices Code parameter set — auction notice period (seven days), reserve price factor (85% of assay), assay reference source, auction cost heads with cap policy, borrower liability retention policy (claim window before treatment change). Gold-loan LMS event codes for pledge, top-up, auction notice, auction conducted, auction proceeds received, surplus posted. Chart of accounts with dedicated borrower-liability codes segregated from interest and other income.
- **Output:** Auction register tying every auctioned loan to notice, reserve, sale, and settlement dates; four-way reconciliation report reconciling proceeds → dues → borrower liability → GL; borrower liability sub-ledger by loan account and borrower with claim status; monthly variance log for statutory auditor and RBI inspection; zero surplus amounts posted to any income code.

### Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments

Source: https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india/

- **Problem:** Indian defence manufacturers reconcile under Defence Acquisition Procedure 2020 with milestone-based payments across five procurement categories, offset-discharge obligations of 30% on contracts above ₹2,000 crore, MoD vendor codes alongside PAN, Performance Bank Guarantees of 5-10% held through warranty, retention money sitting 24-36 months past delivery, customs duty on imported components, and Section 393(1) Sl. 6(i) contractor TDS on every sub-contracting payment.
- **Logic:** Reconcile each contract against DAP-2020 category-specific milestone schedule, track offset discharge against the 30% obligation using Defence Offset Management Wing documentation, maintain dual identifier (MoD vendor code + PAN) on every invoice, age PBG by validity period with 90/60/30 day expiry alerts, age retention money by contract milestone with release-request trigger at warranty expiry, deduct Section 393(1) Sl. 6(i) codes 1023 / 1024 on sub-contractor payments and Section 393(2) Sl. 17 code 1057 on foreign technical-service payments.
- **Config:** Contract master keyed by MoD contract number with DAP category tag, milestone schedule, offset obligation amount, PBG register and retention schedule; vendor master with MoD vendor code, PAN, GSTIN and MSME flag; offset discharge register with multiplier rules; customs duty register per imported component shipment; Section 393(1) Sl. 6(i) deduction matrix with codes 1023 / 1024 default.
- **Output:** A weekly defence-contract dashboard showing milestone-billed-vs-paid by contract, offset discharge percentage against obligation, PBG status with expiry alerts, retention money aged by milestone and contract, customs duty reconciled against landed cost, monthly Section 393 TDS challan tied to sub-contractor payments by codes 1023 / 1024.

### Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply

Source: https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india/

- **Problem:** Defence contracts over 3-7 year programmes run through 5-9 milestone payment stages (advance through SAT and retention release), with MoD vendor code carried alongside PAN, advance bank guarantee against the 10-15% advance, GST time-of-supply splitting goods/services per milestone, Section 393(1) Sl. 6(i) codes 1023 / 1024 TDS on sub-contractor pay, Section 393(1) Sl. 8(ii) code 1031 on purchase, Section 393(2) Sl. 17 code 1057 on any foreign technical-service payment, advance recovery scheduled against later milestones, and ARC/RPC release certificate closing 30+ months after final acceptance.
- **Logic:** Encode milestone schedule per contract with deliverable, buyer acceptance step and payment trigger, maintain dual identifier (MoD vendor code + PAN) on every invoice, age milestone-billed vs paid against contract calendar, run advance bank guarantee with reducing exposure against recovery schedule, apply GST time-of-supply per milestone leg (goods at invoice, services at advance receipt), deduct Section 393(1) Sl. 6(i) codes 1023 / 1024 on subcontractor invoices and Section 393(1) Sl. 6(iii) code 1027 on professional fees, manage ARC/RPC release-request lifecycle after warranty expiry.
- **Config:** Contract master with milestone schedule, deliverable type per milestone, payment percentage per milestone, retention rate, PBG rate, warranty period; vendor master with MoD vendor code, PAN, GSTIN, MSME flag; advance bank guarantee register with face value and reducing-balance schedule; GST time-of-supply rule per milestone leg; Section 393(1) Sl. 6(i) / Sl. 6(iii) / Sl. 8(ii) vendor rate matrix; ARC/RPC release-request workflow; CDA (Controller of Defence Accounts) payment-cycle tracker.
- **Output:** A weekly defence-contract reconciliation dashboard per contract showing milestone-billed vs paid with stage detail, MoD vendor code and PAN cross-reference status, advance balance with recovery schedule progress, GST time-of-supply applied per leg, monthly Section 393 TDS challan tied to subcontractor pay, ARC/RPC release-request lifecycle status, CDA payment ageing, and total working-capital position across active contracts.

### Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts

Source: https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india/

- **Problem:** Indian defence vendors hold Performance Bank Guarantees of 5-10% of contract value and retention money of 5-10% withheld per progress payment, both running in parallel through contract execution and a warranty period of 24-36 months — with PBG auto-extension cycles every 6-12 months, bank PBG charges at 0.5-1% per quarter attracting GST 18% (ITC eligible), retention release tied to ARC/RPC certificate issuance taking 30-180 days post warranty expiry, and a lapsed PBG creating contractual covenant breach.
- **Logic:** Maintain dual ledgers (retention money and PBG) per contract with milestone link, age each retention slice by withholding milestone, track PBG instrument with bank, validity, auto-extension status and 90/60/30 day expiry alerts, capture quarterly PBG bank-charge invoices with GST ITC claim, manage warranty-expiry trigger for release request, age ARC/RPC release request from submission to certificate to bank-credit, monitor cumulative working-capital tied up across both ledgers.
- **Config:** Contract master with retention rate, PBG rate, warranty period, ARC/RPC trigger; retention ledger per milestone with withholding date and release-target date; PBG register with bank name, instrument number, face value, issuance date, current validity, auto-extension flag, quarterly charge schedule; GST input-credit workflow for PBG bank charges; release-request workflow with submission, follow-up, ARC issuance, bank credit; cumulative working-capital report.
- **Output:** A weekly defence-contract dashboard per contract showing retention held by milestone and age, PBG face value and current validity with expiry alerts, quarterly PBG bank-charge ITC claimed, warranty period remaining, release-request status (not-due, due, submitted, in-review, ARC-issued, credited), and total working-capital tied up in retention + PBG across all active contracts.

### Deferred Revenue Reconciliation for Indian SaaS Companies

Source: https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india/

- **Problem:** SaaS contracts with multiple performance obligations (subscription + implementation + support) require separate revenue recognition schedules under Ind AS 115, and quarterly reconciliation of deferred revenue against cash and P&L is error-prone.
- **Logic:** Decompose multi-element arrangements into performance obligations, generate per-obligation recognition schedule, reconcile aggregate deferred revenue balance against cash collections and recognized revenue.
- **Config:** Ind AS 115 five-step model, OIDAR classification for GST, LUT for export SaaS, MCA Schedule III disclosure requirements, quarterly reconciliation cycle.
- **Output:** Performance obligation-wise revenue schedule, deferred revenue waterfall report, Ind AS 115 disclosure package, and cash-to-revenue reconciliation.

### Booking Deposit Forfeiture GST: Section 15(2) and the Tolerating-an-Act Argument

Source: https://www.terra-insight.com/insights/deposit-forfeiture-real-estate-cancelled-booking-gst-india/

- **Problem:** An Indian real estate developer cancels a booking, forfeits the earnest money per the standard clause in the allotment letter, and must decide whether the forfeiture attracts GST. Pre-2022 industry practice treated the forfeiture as damages outside GST. CBIC Circular 178/10/2022-GST reversed that read for pre-agreed forfeiture — it is now a supply of tolerating an act under Schedule II 5(e) at 18% (SAC 999794) or same-rate-as-principal depending on attachment. The developer must classify every forfeiture line correctly, issue a tax invoice, land the output liability in GSTR-1 and GSTR-3B, and reconcile the cancellation ledger to the GST returns to survive an audit.
- **Logic:** Classify every cancellation and forfeiture at the ledger line: outright cancellation with no unit transfer → SAC 999794 at 18%; rebooking with modified purchase or deferred payment penalty → same rate as principal under-construction supply (5% / 1%). Compute GST on forfeited amount using Section 15(2) transaction value rules — treat contract clause as inclusive or exclusive per its plain reading. Issue tax invoice for the forfeiture. Post output liability to GSTR-1 line at the correct SAC and rate. Reconcile the cancellation register total to GSTR-1 outward supply total and to GSTR-3B Table 3.1(a). Track buyer-side TDS (Section 194IA legacy / Section 393 payment codes) refund position separately — the forfeiture GST does not disturb the buyer's TDS position on any amounts already remitted.
- **Config:** Cancellation register keyed by unit code, buyer, booking date, cancellation date, gross booking amount, earnest money paid, refund due (net of forfeiture), forfeited amount, SAC classification (999794 vs principal-rate), GST rate (18% / 5% / 1%), GST amount, tax invoice number; contract clause library storing the standard forfeiture wording per project; GSTR-1 SAC-summary tie-back per return period; GSTR-3B Table 3.1(a) reconciliation to cancellation register plus other B2C outward; RERA cancellation notification calendar (state-specific timelines for buyer notification and refund of net amount).
- **Output:** A cancellation ledger tied line-by-line to the GSTR-1 outward supply table by unit code and invoice; a monthly SAC 999794 outward supply subtotal that reconciles to GSTR-1 Table 5/7 and to GSTR-3B Table 3.1(a); a per-project forfeiture GST reserve balance for cash-flow forecasting; an audit-ready evidence pack per cancelled booking containing the booking agreement, cancellation letter, forfeiture clause reference, tax invoice, GST rate rationale (Circular 178 paragraph 7 mapping), and refund payment evidence.

### Gold Deposit / Savings Scheme Customer Liability Tracking for Jewellers

Source: https://www.terra-insight.com/insights/deposit-gold-scheme-jewellery-customer-liability-tracking-india/

- **Problem:** A customer paying a fixed monthly instalment toward a future jewellery purchase — the standard 11+1 gold-savings scheme where the customer pays eleven monthly instalments and the jeweller adds a twelfth-month bonus — is not revenue on the instalment date. The paid-in cash is a customer deposit that Ind AS 32 classifies as a financial liability and Ind AS 115 paragraphs 106 to 108 present as a contract liability. Revenue attaches only on the delivery day when control of the finished piece transfers. GST does not attach to any instalment; it attaches only to the final HSN 7113 delivery invoice. The twelfth-month bonus is imputed interest — Section 393(1) Sl. 12 TDS applies where the annual imputed interest to a single customer breaches the ₹40,000 threshold. Companies (Acceptance of Deposits) Rules 2014 Rule 2(1)(c)(xii)(a) exempts the collection from the Section 73 / 76 deposit-acceptance regime only if the redemption falls within 365 days of scheme start.
- **Logic:** Track every scheme collection through five parallel books. First: a per-customer, per-scheme balance-sheet contract-liability sub-ledger under Ind AS 115, incremented on each instalment receipt with no P&L impact. Second: a per-scheme age register with the scheme start date, flagging balances that will breach the 365-day Rule 2(1)(c)(xii)(a) window before redemption. Third: a scheme-master reconciliation with the twelfth-month bonus commitment, generating an imputed-interest accrual under Ind AS 109 amortised-cost measurement. Fourth: a per-customer bonus register that aggregates bonus imputed interest across all schemes for a single customer in the financial year, flagging schemes crossing the ₹40,000 Section 393(1) Sl. 12 threshold for TDS deduction at bonus credit. Fifth: a delivery-day invoice generator that issues the final HSN 7113 3% gold invoice, SAC 9988 5% making-charge line, HSN 7102/7103 0.25% diamond line, and reverses the full scheme balance from the contract liability into revenue on the same day.
- **Config:** Scheme master with scheme start date, monthly instalment amount, tenor (must be within 365 days for Rule 2(1)(c)(xii)(a) exemption), bonus commitment (fixed rupee or fixed percentage), exit terms (full refund / cancellation charge / forfeiture), and delivery mechanism (customer-chosen jewellery on maturity day). Customer master with PAN and scheme aggregation across multiple schemes for Section 393(1) Sl. 12 threshold monitoring. Instalment collection sub-ledger with per-customer, per-scheme balance updated on each instalment. Contract-liability GL account under Ind AS 115 with sub-analysis by scheme age band. Imputed-interest accrual GL account under Ind AS 109 amortised-cost with monthly unwind. Bonus TDS register with Section 393(1) Sl. 12 code 1002, threshold monitoring per PAN, deduction schedule at bonus credit event. Delivery-day invoice template with HSN 7113 / SAC 9988 / HSN 7102 / HSN 7326 tax-rate split and full liability reversal in one accounting entry.
- **Output:** A monthly reconciliation pack: contract-liability roll-forward by scheme with opening balance, instalments received, redemptions, exits, and closing balance; scheme age register with days-since-start banding and flags for balances approaching the 365-day Rule 2(1)(c)(xii)(a) limit; imputed-interest accrual working with month-end unwind entry and Ind AS 107 quantitative risk disclosure inputs; bonus TDS register aggregated per customer PAN with Section 393(1) Sl. 12 threshold status; delivery-day revenue recognition reconciliation matching contract-liability reversals to HSN-split invoice values on the delivery invoice; exit-event reconciliation matching refund payouts to contract-liability de-recognition and cancellation-charge GST supply where applicable.

### Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders

Source: https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements/

- **Problem:** Gambling-related transaction outflows in an applicant's bank statement may indicate income allocation risk, impulsive spending patterns, or over-reliance on variable income sources — all of which are relevant to repayment capacity assessment.
- **Logic:** Match every transaction description against a list of 130+ gambling and betting platform names covering fantasy sports, poker, rummy, offshore casinos, and sports betting apps. Record transaction count, total debit, total credit, and the top five matched platform names. Compute gambling outflows as a share of average monthly income to contextualise the signal.
- **Config:** Enable for credit underwriting workflows at NBFCs, HFCs, and digital lending platforms. Calibrate the income-share threshold based on lender policy. Exclude small one-off entries if below a de minimis debit threshold set by the lender.
- **Output:** Gambling risk section in the credit report showing transaction count, total debit, total credit, and top five matched platform names. Flagged if gambling outflows exceed the lender-defined income-share threshold.

### Deterministic Reconciliation and Audit Reproducibility Under Indian Statute

Source: https://www.terra-insight.com/insights/deterministic-reconciliation-audit-reproducibility-india/

- **Problem:** Statutory audit in India increasingly requires that reconciliations closed months or years ago be re-derivable at will. The Companies Act 2013 Section 128 requires books of account to be preserved for eight financial years; Rule 3(1) requires an inextinguishable audit trail on every transaction and edit from 1 April 2023 onward. Ind AS 8 requires the auditor to distinguish a prior-period error from a legitimate change in estimate — an exercise that presumes the original computation can be reconstructed. Most reconciliation tools cannot make this bar. When software upgrades happen, tolerance defaults shift, rounding conventions creep, matching heuristics evolve — and a Q3 FY 2024-25 close re-run in Q1 FY 2026-27 returns numbers different from what was originally signed off. The audit gap that opens between the sealed artifact and the current re-run is where qualified opinions, disclosure caveats, and revenue-leakage restatements live.
- **Logic:** Deterministic reconciliation means that same inputs plus same configuration always return the same envelope — an exact reproduction of matches, exceptions, totals, identity checks, and signatures. The engine pins its execution environment per artifact: engine version, configuration version, industry preset, calendar, rounding convention, source-data hash. When the artifact is re-executed for audit purposes, the environment is reconstituted from the pin, and the run proceeds against the same source inputs to return the byte-identical envelope. This is a property of every delivered artifact, not a future covenant. Newer engine versions operate only on new closes going forward and cannot alter previously signed artifacts. The auditor treats the re-run as evidence rather than opinion: the numbers behind the FY signed off two years ago are the numbers computed today under identical execution.
- **Config:** The version pin embedded in the envelope: engine version, configuration version (industry preset name and revision, tolerance table, calendar, cutoff dates, half-up paise-exact rounding convention), source-data hashes for each input feed (bank statement, book ledger, GSTR-2B extract, portal export), statutory rate tables in effect at the transaction dates (TDS payment codes 1001-1092 versus legacy 194/195, GST rates pre- and post-22-September 2025), and the signed hash of the envelope itself. All of these travel with the envelope from the moment it is closed, so no reconstruction is needed beyond loading the pin.
- **Output:** A re-execution of a previously signed reconciliation returns the same envelope, byte for byte. Match counts, exception counts, gross-net-tax buckets, identity check results, and the envelope signature are all identical. The auditor can accept the artifact as computed evidence — reproducible, not asserted. Under Ind AS 8, a delta observed between the original artifact and a fresh close is attributable to a specific driver (new data, changed estimate, mechanical error) rather than opaque software drift. Under the Rule 3(1) audit-trail proviso, the reproducibility of the artifact turns the trail from a compliance record into substantive evidence.

### Devi Sea Foods Processing Plant Reconciliation — Andhra Pradesh

Source: https://www.terra-insight.com/insights/devi-sea-foods-processing-plant-reconciliation-ap/

- **Problem:** A Bhimavaram vannamei processing plant of the scale that Devi Sea Foods operates — 120 MT of raw shrimp per day at peak season, drawn from around 2,500 aquaculture ponds averaging 2 to 3 acres each across the Krishna and West Godavari delta, at an illustrative farmer settlement of Rs 380 to Rs 420 per kilogram for count grade 30/40 vannamei — must reconcile pond-wise farmer procurement against a CAA farm registration base, an antibiotic-residue lab certificate per pond per harvest cycle, a USFDA compliance cost workbook that splits every entry between Ind AS 16 capex and Section 37 revex, and the shipping-bill-to-e-BRC realisation cycle under the FEMA nine-month clock. A break at any hop — an expired Food Facility registration, a pond-level antibiotic failure lost between the freezer batch and the shipping bill, a mis-classified LC-MS/MS instrument booked as revex, or an unreconciled shipping bill drifting past 270 days — cascades into a USFDA Import Alert 16-124 listing, a Section 143(3) assessment adjustment, or a FEMA contravention exposure.
- **Logic:** Build a pond-level supplier master keyed to the MPEDA farmer identifier and the CAA farm registration, and carry the stocking-cycle post-larvae lot, feed issue quantity, water quality reference, and pre-harvest antibiotic sampling reference on the pond record through the crop. At harvest, calculate the pond-wise farmer settlement on the count-grade schedule and issue a procurement lot number at the plant weighbridge that inherits the pond identifier. Carry the pond identifier onto the processing plant lot, the freezer batch, the pre-shipment sampling reference drawn by the plant QA team for the EIA, the NABL EIA lab analytical report number, the Export Health Certificate serial from the regional EIA, and the shipping bill filed at ICEGATE. Ingest the USFDA compliance cost workbook with a capex/revex tag on every entry — LC-MS/MS instruments and validation instrumentation to Ind AS 16 capex with a fixed-asset register entry and useful life; DUNS renewals, Food Facility renewals, consumables, reagents, PCQI training, and third-party audit fees to Section 37 revex in the year of incurrence. Feed the shipping-bill register into the e-BRC reconciliation keyed by SB number, book the fx-variance to the dedicated Ind AS 21 forex GL, and age unreconciled shipping bills against the FEMA nine-month clock with escalations at 180 and 270 days.
- **Config:** Pond master with MPEDA farmer identifier, CAA registration, survey number, tank area in hectares, water source, effluent treatment reference, stocking-cycle number, and SPF post-larvae lot lineage from a CAA-authorised hatchery; count-grade price schedule keyed by species (Penaeus vannamei, Penaeus monodon) and count band (30/40, 40/50, 50/60, 60/70, 70/80, 80/100, 100/200) with effective-date versioning; feed supplier master with GSTIN, HSN 2309, 5 percent GST rate, and Section 43B(h) MSME flag; processing plant lot numbering rule and freezer-batch template that carries pond identifier forward; EIA lab master with NABL accreditation reference and analyte panel (chloramphenicol nil, nitrofuran metabolites nil, tetracyclines 100 ppb, USFDA sulphonamides listed); Export Health Certificate serial series from the regional EIA; shipping bill register with SB number, date, FOB USD/INR, LUT reference, RoDTEP election, and destination country; USFDA compliance cost workbook with capex/revex tag, DUNS reference, Food Facility registration number, and FSVP-supporting document register; fixed-asset register for laboratory capex with Ind AS 16 useful-life and depreciation-method fields; capital-goods ITC refund route tracker separate from the Rule 89(4) zero-rated refund base; AD Category-I bank master for e-BRC upload and realisation; and forex-fluctuation GL under Ind AS 21 with favourable and unfavourable buckets.
- **Output:** A monthly plant reconciliation pack: pond-wise farmer procurement register with count-grade settlement, feed-issue reconciliation against FCR benchmark, and CAA registration status per pond; per-pond antibiotic-residue lab certificate register with pass/fail status and quarantine flag on the plant's supplier risk register; USFDA compliance cost workbook with capex and revex totals rolled up for management review, the fixed-asset register update for any laboratory capital addition in the period, and the Section 37 revex ledger tied to the tax computation; shipping-bill register with e-BRC realisation status, fx-variance booked to the Ind AS 21 forex GL, and ageing against the FEMA nine-month clock with 180-day and 270-day escalations. Year-end pack rolls up USFDA facility inspection readiness with the full pond-to-shipping-bill traceability spine reproducible on 24-hour notice, and the audited capex/revex classification for the USFDA compliance cost workbook flowing into the Notes on Accounts.

### Dhampur Sugar Distillery Molasses vs Cane-Juice Ethanol Reconciliation

Source: https://www.terra-insight.com/insights/dhampur-sugar-distillery-molasses-cane-juice-ethanol/

- **Problem:** A 400 KLPD integrated distillery in western Uttar Pradesh runs a 40/30/30 feedstock split across B-heavy molasses, C-heavy molasses, and cane-juice-direct ethanol during the 2025-26 EBP season. Each grade attracts a distinct notified per-litre price from the Oil Marketing Companies (illustrative: Rs 60.73/L B-heavy, Rs 56.28/L C-heavy, Rs 65.61/L cane-juice-direct); each batch carries a grade tag from fermenter charge through dispatch; each of the three OMCs (IOCL, BPCL, HPCL) allocates monthly through an Expression of Interest tender with fortnight-window lifting; each OMC deducts TDS at 0.1 percent under Section 8 Sl. 8 code 1031; and the 5 percent ethanol output GST against 18 percent packaging and chemical input GST accumulates a Section 54(3) inverted-duty refund cycle every period. Manual reconciliation across batch production log, grade-price schedule, three OMC settlement streams, TDS remittance, and Rule 89(5) refund workbook loses per-batch grade attribution on around one dispatch in fifty, mis-attributes packaging input GST between tax periods, and leaves TDS 26AS gaps open for the following filing quarter.
- **Logic:** Ingest the batch production log with an immutable grade tag locked at fermenter charge, carry the grade tag through distillation and dispatch, and reconcile expected ethanol output against actual litres produced using the notified per-grade conversion factor with a plant-specific tolerance band. Match every dispatch to the OMC EOI allocation, the tanker gate weighbridge reading, the OMC depot inbound weighbridge reading with density correction to 15 degrees Celsius, and the OMC settlement invoice keyed to the notified per-grade price. Reconcile TDS deducted by each OMC under code 1031 at 0.1 percent against the distillery's Form 26AS at the filing quarter close. Extract packaging input GST at 18 percent, chemical input GST at 18 percent (with separate 12 percent and 5 percent lanes where applicable), and ethanol output GST at 5 percent from GSTR-1 and GSTR-3B into the Rule 89(5) refund workbook, apply the amended Notification 14/2022 formula with input services and capital goods excluded from Net ITC, and generate the GST RFD-01 filing base every month or quarter.
- **Config:** Feedstock master by grade (B-heavy, C-heavy, cane-juice-direct) with the notified per-litre price and the notified conversion factor per season; batch master with fermenter identifier, grade tag, feedstock quantity, expected and actual ethanol litres, and yield variance; OMC master for IOCL, BPCL, HPCL with EOI allocation reference, contract price schedule, depot destination, and credit period; tanker weighbridge master keyed to gate outbound and OMC depot inbound with density-corrected volume conversion at 15 degrees Celsius; TDS payment code master with code 1031 (Section 194Q equivalent) at 0.1 percent per OMC PAN; GSTR-1 and GSTR-3B feed into the Rule 89(5) refund workbook with a packaging-input ledger, chemical-input ledger, input-services ledger (excluded from Net ITC), and capital-goods ledger (excluded from Net ITC); Section 43B(h) MSME flag on HDPE-drum and laminate suppliers where they are MSME-registered.
- **Output:** A month-end distillery reconciliation pack: batch production log with grade tag and yield-variance flag; OMC-wise dispatch register with allocated versus lifted, weighbridge-reconciled quantity, and settlement value at notified grade price; three OMC monthly settlement invoices matched to the distillery's own sales register; Form 26AS reconciliation for TDS deducted under code 1031 by each OMC; Rule 89(5) refund draft under the Notification 14/2022 amended formula with input services and capital goods correctly excluded from Net ITC; Section 43B(h) MSME payables ageing on packaging and chemical suppliers; and — at year-end — the aggregate season summary of ethanol produced by grade, revenue realised by grade, GST refund claimed by tax period, and TDS credit reconciled by OMC PAN for the distillery's income-tax return.

### Diagnostic Lab Revenue Reconciliation: Test Aggregator and B2B Channel Recovery

Source: https://www.terra-insight.com/insights/diagnostic-lab-revenue-reconciliation-india/

- **Problem:** Diagnostic lab revenue spans five channels — walk-in B2C, hospital B2B, corporate empanelment, online test aggregators, and home collection — each with a different rate card, settlement cycle, and tax overlay, and aggregator settlements routinely leak 1.0–2.0% to misclassified packages and uninvoiced add-ons.
- **Logic:** Decompose each aggregator settlement file into booking-level lines, match every line to the LIMS booking by aggregator ref + test code, apply the contractual per-test lab-share rate, classify variances as package-vs-individual misclassification, courier add-on shortfall, convenience-fee absorption, or retroactive rate-card drift, and overlay GST exemption boundary plus TDS deductor reconciliation.
- **Config:** 5 channel rate cards, 4+ aggregator platform formats, GST exemption test under Notification 12/2017, 18% GST on wellness/courier/home-collection convenience fees, TDS code 1027 for professional services on B2B referrer payments, pure-agent test for radiology sub-contracting.
- **Output:** Per-booking lab-share variance report, channel-wise revenue leakage quantum, TDS receivable register reconciled to 26AS by deductor, GST exempt vs taxable revenue split for GSTR-1, aggregator-wise dispute queue.

### Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works

Source: https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements/

- **Problem:** A fabricated bank statement with plausible-looking individual amounts passes visual inspection because reviewers check individual transactions, not the statistical properties of the full distribution. Fabricated amounts constructed by humans deviate from the digit distributions that genuine financial data produces.
- **Logic:** Run two complementary forensic checks on the full set of transaction amounts: (1) Compare the distribution of leading digits against the expected frequency distribution for naturally occurring financial data — significant over-representation of any digit range is a fabrication signal. (2) Analyse the transaction amount sequence for unnatural rhythms, fixed-step progressions, or suspicious clustering that would not arise in independent real-world spending events.
- **Config:** Apply to accounts with 50 or more transactions for reliable statistical power. Calibrate for account type — salary accounts, fixed-EMI-heavy accounts, and ATM-dominated accounts require adjusted baselines before digit distribution comparison is meaningful.
- **Output:** Two flags: a digit-distribution anomaly flag (clean / flagged / insufficient data) and a sequence pattern flag (organic / patterned / review), both presented in the fraud signals section of the analysis report with the specific deviation metrics that triggered the classification.

### Diners Club Credit Card MDR: 2.95-3.5% Economics for Indian Merchants

Source: https://www.terra-insight.com/insights/diners-club-mdr-india/

- **Problem:** Diners Club is billed at 2.95-3.5% across Indian gateways — Cashfree explicitly lists 2.95%, Razorpay and PayU bucket it with Amex and international at 3% — but Diners typically represents under 2% of total card volume at an Indian merchant. A blended 2% deduction line therefore absorbs the Diners cost without itemisation, and the merchant cannot tell whether Diners was billed at its premium slab or averaged into the consumer rate. Either the merchant cross-subsidises Diners through low-cost UPI and Visa/Mastercard, or the gateway under-recovers on the small Diners tail and silently reclaims it via reclassification, a rate revision, or a renewal true-up.
- **Logic:** Per-cycle Diners isolation extracts Diners-network transactions from the settlement file using BIN ranges (Diners BIN families 300-305, 309, 36, 38, 39) or the network identifier where the gateway publishes one, sums the gross transacted volume and the total fee deducted on the Diners subset, computes effective Diners MDR as fee divided by volume, and compares it against the contracted Diners slab and against the blended rate. A DINERS_EFFECTIVE_RATE_GAP variance is raised when Diners effective MDR equals the blended rate to within ten basis points (indicating Diners has been priced flat rather than at its contracted premium slab), or when Diners effective MDR exceeds the contracted slab by more than the audit tolerance.
- **Config:** Network rule keyed to Diners BIN ranges with fallback to network identifier; contracted Diners slab loaded from the gateway agreement; blended-rate rule recording the merchant's headline contracted rate; DINERS_EFFECTIVE_RATE_GAP variance class with a ten-basis-point slab-delta tolerance; flat-pricing flag raised when Diners effective rate matches the blended rate; GST-invoice matcher for the 18% line against the gateway tax invoice; refund-MDR retention flag and a 90-day rolling recovery window.
- **Output:** A per-cycle Diners effective-rate row showing fee, volume, effective rate, contracted slab, basis-point variance, and recoverable or exposed amount; a flat-pricing alert when Diners is absorbed into the blended line; a dispute-pack export with per-transaction Diners evidence and expected-versus-actual fee calculation; a GST-invoice reconciliation schedule against the gateway's tax-invoice line; and a renegotiation brief showing the annualised Diners cost-of-acquiring gap that the CFO carries into the gateway conversation.

### DISCOM Settlement Reconciliation for Power Generators in India

Source: https://www.terra-insight.com/insights/discom-settlement-reconciliation-india/

- **Problem:** Indian power generators face a structural DISCOM settlement reconciliation gap — state DISCOMs pay on 90 to 180 day cycles under PPAs that split tariff into fixed capacity and variable energy components (or a single levelised renewable tariff), SLDC energy accounting in 15-minute blocks creates DSM exposure on scheduled-vs-actual deviation, REC inventory accumulates monthly with trade settlement on IEX or PXIL day-specified sessions, and the Late Payment Surcharge Rules 2022 entitle a base MCLR-plus-2 percent recovery escalating 0.5 percent per month capped at MCLR plus 5 percent — each rail has its own data source and an audit-readable close needs all four reconciled to the generator's revenue ledger.
- **Logic:** Tie each monthly DISCOM invoice to the SLDC energy accounting statement (scheduled MUs in 15-minute blocks) and to the SCADA-recorded actual generation, decompose tariff into fixed capacity and variable energy under PPA terms with deemed generation events flagged separately, compute the DSM charge or credit per 15-minute block on the regional slab against the day-ahead forecast, age each invoice from due date and apply the LPS Rules 2022 slab progression for the LPS receivable booking, tie REC issuance in the registry to generation MUs and tie REC sales on IEX or PXIL sessions to trade proceeds net of exchange fee and TCS reaching the generator bank account, and keep the GST exemption on electricity sale (Notification 2/2017 entry 104) separate from any taxable ancillary service component under SAC 998633.
- **Config:** PPA master per DISCOM offtake with tariff structure (fixed plus variable or levelised), deemed-generation clauses, billing cycle and dispute resolution clause, SLDC energy accounting ingest by 15-minute block with scheduled and actual MWh per period, DSM rate table by regional slab and frequency band updated per CERC notification, REC registry account with issuance pending and issued status, IEX and PXIL trade settlement ingest with exchange fee and TCS line items, LPS ageing buckets keyed to PPA due date with MCLR-plus-X slab progression, PRAAPTI portal monthly outstanding ingest for cross-check, and GST line-treatment table separating exempt electricity sale from taxable ancillary services.
- **Output:** A monthly reconciled view per DISCOM showing invoice raised vs SLDC energy accounting vs SCADA actual generation with deviation flagged, DSM charge or credit by 15-minute block aggregated to the period, REC inventory with issued-pending-sold status reconciled to generation MUs and to IEX or PXIL trade proceeds tied to bank credit, an LPS receivable schedule aged by invoice with the slab-progression LPS rate applied and the receivable separated from principal, and a GST classification view splitting exempt electricity sale from any taxable ancillary line for GSTR-3B 3.1(c) versus 4(A)(5) routing.

### DISCOM Tariff True-Up Reconciliation under MERC/KERC: Industrial Consumer Guide

Source: https://www.terra-insight.com/insights/discom-tariff-true-up-merc-india/

- **Problem:** An Indian industrial HT or EHT consumer drawing tens of GWh per year sees its electricity cost reconciled across four rails — the SERC's annual tariff order under the DISCOM's Aggregate Revenue Requirement, the quarterly FPPCA pass-through filed under MYT Regulations, the annual true-up reconciling actuals against approved expense and revenue, and the monthly bill line that carries the true-up recovery or refund — each with its own filing cycle, evidence pack, and working-capital tail.
- **Logic:** Hold the SERC's tariff order rate card per consumer category as the base, ingest each quarter's FPPCA order to derive the per-unit adjustment for the HT category for that quarter, recompute the expected monthly bill from metered units and demand registered, compare against the DISCOM's billed amount line by line (energy charge, demand charge, FPPCA, true-up recovery, electricity duty, cesses), age any variance against the disputed-bill window the SERC's supply code permits, and on true-up order issue translate the category-wise paise-per-unit refund or surcharge into a year-to-date recoverable amount that ties to the monthly bill adjustment line.
- **Config:** Tariff order master keyed by SERC, financial year, consumer category (HT-I industrial, HT-II commercial, EHT) with energy charge, demand charge, time-of-day differentials, electricity duty rate, applicable cess; FPPCA quarterly rate table with state, quarter, category and paise-per-unit adjustment; true-up order register with approved gap, recovery period, monthly recovery schedule; metered consumption ingest per service connection with kWh, kVAh, MD registered, power factor; bill line classification table (energy / demand / FPPCA / true-up / duty / cess / meter rent / service connection); exempt-supply flag for GSTR-3B treatment under Notification 02/2017 entry 104.
- **Output:** A monthly reconciled energy-cost view per service connection showing expected vs billed for energy charge, demand charge, FPPCA, and true-up recovery, with variances coded by reason and aged in the SERC's disputed-bill window; a year-to-date true-up position per category showing recoverable or refundable rupees against the approved order; a GST treatment ledger correctly classifying the electricity component as exempt inward supply outside ITC and the meter-rent or testing-fee component as taxable inward supply at 18% with ITC tracked; and a working-capital position showing refund claims outstanding against DISCOMs with ageing for finance reporting.

### Distributor Commission and Section 393 Sl. 18 (194H) TDS Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/distributor-commission-section-194h-tds-fmcg/

- **Problem:** Indian FMCG brands accrue distributor commission on dispatch — Day 0 of the secondary sale — while the distributor recognises commission income on month-end claim approval, which sits 45 to 120 days after dispatch. Section 393(1) Sl. 18 of the Income-tax Act 2025 (legacy 194H) at 5% applies once per-deductee commission aggregates cross ₹15,000 in the financial year, with TDS reflected in the deductee PAN's Form 26AS. The accrual-versus-recognition lag, combined with payment-code mis-tagging and PAN-level aggregation logic, produces structural Form 26AS gaps that surface as TDS mismatches when the distributor closes its books — typically 8 to 18 percent of the brand's commission cost for the year sits in this disputed zone at 31 March.
- **Logic:** Build a monthly commission accrual register keyed by distributor PAN, distributor GSTIN, scheme code, geography, and category; book accrual on Day 0 of the secondary sale at the commission percentage in the scheme. In parallel, capture the distributor claim recognition register from the brand's TPM portal — claim approval date, gross commission, TDS deduction date, TDS deposit reference, Form 26Q quarterly reference. Cross-foot a per-PAN running aggregate from 1 April to apply the ₹15,000 threshold; flip on TDS at boundary cross. Match the brand's deducted-TDS pool against the distributor's Form 26AS deductee report by quarter, by payment code (1015), and by TAN; classify residual gaps into accrual-payout lag, code mis-tag, PAN-error, threshold-not-crossed, and contested rejections.
- **Config:** Distributor master with PAN, GSTIN, claim-portal ID, agreement type (agent / principal-to-principal), Section 393(1) Sl. 18 rate (5%), and per-deductee FY threshold (₹15,000); scheme master with code, commission percentage, validity dates, and agency-versus-discount treatment flag; secondary-sales feed from DMS by distributor by SKU by period; claim recognition feed from the brand's TPM portal with approval date; TDS posting register with payment code 1015, deposit date, and Form 26Q quarter reference; Form 26AS deductee export from the distributor side or from the brand's TRACES download per TAN; PLISFPI base-year and incremental-sales register for the 53 beneficiary entities.
- **Output:** A quarterly TDS reconciliation pack: brand commission accrual, brand commission payout, brand TDS deducted, brand TDS deposited, brand Form 26Q filed (by quarter, by code 1015), distributor commission income recognised, distributor Form 26AS credit, and the gap aged by reason code. Per-distributor Form 26AS mismatch register surfaces stuck credits with TAN, PAN, and quarter detail. A Section 393(1) Sl. 18 versus Sl. 4 audit register classifies every distributor cash payment to the right payment code, and the PLISFPI beneficiary register reconciles commission cost against incremental-sales certification for the 53 named entities.

### Dispose vs Safekeep Collateral Gold: NBFC Decision Reconciliation

Source: https://www.terra-insight.com/insights/dispose-vs-safekeep-collateral-gold-nbfc-reconciliation-india/

- **Problem:** A gold-loan NBFC account crosses 90 DPD and is classified NPA under RBI Scale Based Regulation norms. The NBFC must decide between safekeep (hold the pledged gold until the borrower redeems) and dispose (auction under RBI procedure). The Fair Practices Code overlays a notice-and-redemption window before any disposal is permitted, and Ind AS 109 impairment depends on which path the NBFC takes.
- **Logic:** Anchor the sequence on regulatory dates — Day 90 NPA, Day 90-120 notice served, Day 150+ auction if no redemption. Reconcile four ledgers end-to-end: default register, notice trail, redemption receipts, and auction proceeds. Every account crossing 90 DPD closes in exactly one of two paths — redemption or auction — with a matching collateral movement and a matching Ind AS 109 impairment stage.
- **Config:** Parameter set per NBFC branch — redemption window in days, reserve-price percentage (85% RBI floor), auction cadence, notice dispatch mode (registered post / speed post / email), unclaimed surplus escalation. Loan-account-level DPD register feeding the NPA classification engine. Auction house or agent contract terms — commission rate, minimum bidder pool, settlement window.
- **Output:** Complete document chain from Day 90 default identification to disposal or redemption closure, with the four ledgers reconciled, the Ind AS 109 ECL re-measured on decision change, and a Fair Practices Code compliance file ready for RBI inspection and statutory audit.

### DMart FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/dmart-fmcg-settlement-reconciliation/

- **Problem:** An FMCG brand owner shipping ₹2.6 to ₹2.8 crore of monthly invoicing into DMart settles on a published 7-day cycle with a 3% prompt-payment discount conditional on clean-cycle adherence; the settlement file format is account-specific, the debits are line-level (listing fee, BOGO scheme reimbursement, QC reject, GRN-vs-invoice tolerance, MRP mismatch), and the brand owner's SAP or Oracle invoice ledger does not natively reconcile against the DMart remittance file; a typical monthly cycle leaks ₹3.5 lakh of listing-fee mis-treatment, ₹1.2 lakh of unsupported QC reject debits, and ₹8.4 lakh of prompt-payment discount that may or may not survive a quarter-end eligibility audit.
- **Logic:** Build a three-way line-level reconciliation across the SAP invoice ledger (canonical billed), the DMart PO and GRN feed (acknowledged), and the DMart remittance file (paid). Join on invoice number and line; classify per-line variance into the five DMart debit categories plus the prompt-payment discount; verify adherence conditions cycle-by-cycle (no open QC reject, no unsettled listing-fee dispute, no scheme-claim variance) before crediting the 3% discount as Section 15(2) trade-discount; cross-link QC reject debits to Section 34 credit notes the supplier issues against the original invoice; age open variance 0-30 / 31-60 / 61-90 / 90+ days from cycle close.
- **Config:** DMart account master with cycle calendar (7-day), prompt-payment discount rate (3%) and adherence-condition list; SAP/Oracle invoice ledger feed at invoice-line grain; DMart PO and GRN feed via supplier portal; DMart remittance file parser per cycle; debit-category taxonomy (listing fee, BOGO reimbursement, QC reject, GRN tolerance, MRP mismatch); Section 15(2) discount-treatment rule per cycle; Section 34 credit-note linkage to QC reject debits; GST rate-by-date table with 22 September 2025 cut-over for biscuits, chocolates, soaps; ageing buckets 0-30 / 31-60 / 61-90 / 90+ days.
- **Output:** A cycle-close pack per 7-day DMart settlement cycle: SAP invoice gross, DMart remittance net, per-line variance against expected with named-invoice breaks across the five debit categories, prompt-payment discount eligibility audit (adherence flag, accrued amount, taken amount, variance), Section 34 credit-note linkage status on QC reject debits, GST rate-by-date check on the cycle's invoices, and an ageing report on open cycles 30+ days — handed to the modern-trade controller for AR closure and to the GST controller ahead of GSTR-1 filing.

### DMS (Distributor Management System) Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/dms-distributor-management-system-reconciliation-fmcg/

- **Problem:** Indian FMCG brands push primary sales out of SAP CO-PA at the distributor-by-SKU grain on a monthly close cycle, while a Distributor Management System — Botree, Bizom, Salesworx, or FieldAssist — pushes weekly secondary sales by SKU by retailer from each distributor's branch. The two streams must reconcile per SKU per distributor per period through the pipeline identity (primary minus secondary minus closing inventory equals stock-in-trade), but SKU-master drift, retailer-code mismatch, wrong scheme reference, and weekly-versus-monthly cadence routinely break the tie-out — and that breakage blocks scheme-claim approval, distorts TPM accrual, breaks PLISFPI incremental-sales certification, and corrupts Section 393(1) Sl. 18 (legacy 194H) commission-TDS reconciliation against Form 26AS.
- **Logic:** Pull the weekly DMS secondary-sales feed at distributor-SKU-retailer-period grain; roll up four or five weekly files to align with the monthly CO-PA primary-sales period. Pull SAP CO-PA primary sales at distributor-SKU-period grain for the same window. Pull closing inventory from the distributor's DMS branch close and breakage/returns from the credit-note register. Run the pipeline identity per SKU per distributor per period; classify residuals into SKU-master breakages, retailer-code mismatches, wrong scheme references, pipeline drift, and cadence-mismatch artefacts. Surface unresolved residuals to the regional finance manager with an ageing clock; clear resolved residuals back to the TPM accrual cycle and the scheme-claim portal so blocked claims unblock with the correct evidence.
- **Config:** SKU master with brand SKU code, distributor SKU code, HSN, GST rate (pre and post 22 September 2025), pack size, and SAP material master cross-reference; distributor master with distributor code, GSTIN, PAN, DMS platform (Botree/Bizom/Salesworx/FieldAssist), beat-plan ID, and Section 393(1) Sl. 18 TDS threshold; retailer master with retailer code, GSTIN where present, beat-plan assignment, and consolidation rules for merged retailer records; scheme master with code, percentage, effective dates, Section 15(2) treatment flag; weekly DMS feed parser per platform; monthly CO-PA primary-sales extract; closing-inventory and breakage/returns feeds; pipeline-residual classification ruleset; ageing-bucket configuration for unresolved residuals.
- **Output:** A monthly DMS reconciliation pack — opening stock, primary sales (CO-PA), secondary sales (DMS roll-up), breakage/returns, closing stock, and pipeline residual — cross-footed to the SAP material ledger and the trade-spend liability account. Per-SKU per-distributor residual register classifies failures (SKU-master / retailer-code / scheme-reference / pipeline-drift / cadence) with ageing buckets and resolution status. Scheme-claim portal receives validated secondary-sales evidence so blocked claims unblock. PLISFPI incremental-sales certification pack ties primary-sales registers to audited DMS evidence. Section 393(1) Sl. 18 commission-TDS ledger reconciles to DMS-derived commissionable secondary sales at distributor PAN level for Form 26AS tie-out.

### DPCO 2013 and NPPA: Reconciling Scheduled-Drug Overcharging Recovery

Source: https://www.terra-insight.com/insights/dpco-2013-nppa-ceiling-price-overcharging-recovery-reconciliation/

- **Problem:** A Tier-1 integrated pharma formulator carrying a scheduled-formulation portfolio of the order of one hundred and eighty formulations across forty-two molecules must reconcile per-SKU MRP against every NPPA ceiling-price notification published under Paragraph 4 of DPCO 2013, flag Paragraph 20 overcharging where the live MRP remains above the notified ceiling after the thirty-day effective-date transition, prepare for Form DPCO-6 demand-notice adjudication for the overcharged principal plus Wholesale-Price-Index-linked interest, and hold an Ind AS 37 provision for the expected recovery quantum. A typical quarterly NPPA notification cycle will revise ceilings on approximately six to twelve molecules — for a portfolio of forty-two molecules the annual notification-response workload runs to twenty-five to forty ceiling revisions requiring SKU MRP realignment, trade-channel repricing, physical restickering at depot, and retail-audit verification of shelf-level compliance within the thirty-day window.
- **Logic:** Build a per-SKU tracker keyed on molecule-strength-dosage-form combination that ingests every NPPA ceiling-price notification as published on the NPPA portal. For each scheduled SKU the tracker maintains: brand name, current MRP, current price to retailer, most recent NPPA notification date, notified ceiling price, effective date (typically thirty days from notification), and a variance flag that fires when MRP exceeds the ceiling. On a notification event the workflow triggers: SAP or Oracle price-master update to the new MRP at or below the ceiling, trade-notification to distributors, physical relabelling or restickering of stock at depot, and retail-audit sampling to confirm shelf-level MRP compliance within the thirty-day window. Post-effective-date sales are audited daily against the ceiling. Any residual overcharging — MRP still above the ceiling on any post-effective-date sale — is quantified as principal (overcharged amount per unit multiplied by units sold) plus WPI-linked interest, and recognised as an Ind AS 37 provision. Form DPCO-6 demand notices received are reconciled against the internally computed exposure and any variance investigated before the representation window closes.
- **Config:** Scheduled-formulation SKU master with molecule, strength (10 mg, 20 mg, 40 mg for atorvastatin as an illustrative example), dosage form (tablet, capsule, syrup, injectable), brand name, GSTIN plant of manufacture, current MRP, current price to retailer, and NLEM 2022 First Schedule match; NPPA notification-monitoring feed from the NPPA portal that ingests every ceiling-price notification with molecule-strength-form parsing, notified ceiling price, notification date, and effective date; per-SKU variance workbook comparing live MRP to the notified ceiling with a variance flag; SAP or Oracle price-master change-management workflow triggered on the notification event with the thirty-day-window countdown; trade-channel notification and distributor communication tracker; depot-level physical relabelling job list with restickering completion audit; retail-audit sampling schedule for shelf-level MRP verification; daily post-effective-date sales audit against the ceiling; Paragraph 20 overcharging quantification register with principal and WPI-linked interest computation; Ind AS 37 provision workbook with recognition-versus-contingent-liability classification; Form DPCO-6 demand-notice receipt-and-response register with the representation-window countdown.
- **Output:** A monthly DPCO-NPPA reconciliation pack: per-SKU compliance status against every active NPPA ceiling-price notification, thirty-day-window countdown for any live notification with SAP price-master update, trade-channel notification, depot restickering and retail-audit sub-status, quantified Paragraph 20 overcharging exposure with principal and WPI-linked interest per exposure line, Ind AS 37 provision movement (opening balance, additions, utilisations against Form DPCO-6 deposits, releases against successful representations), and the outstanding Form DPCO-6 demand-notice inventory with representation-window status. At year-end the pack reconciles the aggregate Ind AS 37 provision balance to the aggregate DPEA deposits made against Form DPCO-6 notices, surfaces the residual contingent-liability disclosure for the notes to accounts, and feeds the next-year monitoring plan with the NPPA notification pattern observed during the year.

### Domestic BIN Charged at International Rate: MDR Leakage Detection

Source: https://www.terra-insight.com/insights/domestic-bin-charged-international-rate-mdr-india/

- **Problem:** Indian-issued cards routinely show up in settlement files billed at 3%+ international MDR with a cross-border forex line layered on, when the issuer country derived from the BIN is India and the contracted domestic slab is around 2%. The over-charge is invisible in blended-rate dashboards and surfaces only at per-transaction grain. Every month the leakage compounds, with 18% GST on the inflated fee flowing through alongside.
- **Logic:** Reconciliation extracts the first six digits of every settled card transaction, looks up the BIN against a current issuer-country registry, and compares the BIN-derived scope to the scope the acquirer applied. Any transaction with BIN-country IN that was charged at an international slab (above ~2.5 percent network MDR) or carries a non-zero forex line is flagged as a mis-classification. The over-charge is the actual MDR minus the contracted domestic rate, applied to the transaction value, with proportional GST.
- **Config:** BIN registry refreshed at gateway-cycle cadence, domestic-versus-international scope rule per network, contracted-rate matrix keyed by network and tier, forex-line presence check (must be zero for BIN-country IN), per-transaction settlement extract feed, monthly exception report with recoverable amount per transaction.
- **Output:** Per-transaction mis-classification report with recoverable over-charge by row, monthly aggregate of recoverable MDR and recoverable GST, fee-adjustment request letter ready for acquirer submission, and a trended BIN-classification dashboard that flags drift before it compounds across a quarter.

### DPIIT Compliance for PLI Textile Claim — Annual Reporting Reconciliation

Source: https://www.terra-insight.com/insights/dpiit-compliance-pli-textile-claim-reconciliation/

- **Problem:** A mid-tier MMF apparel manufacturer at Tiruppur, Surat, or Ludhiana claiming under the ₹10,683 crore PLI Textile scheme must reconcile four separate DPIIT compliance surfaces to a single audited claim: the initial registration commitment (product segment plus Category A ₹100 crore or Category B ₹300 crore investment tier); the quarterly progress reports on Plant and Machinery capitalisation; the annual audit-firm certification of incremental sales over the base-year threshold; and the annual claim application filed within 7 months of FY-end. Segment mis-classification between MMF Apparel (Chapter 61 knit, Chapter 62 woven) and MMF Fabrics (Chapter 54 filament, Chapter 55 staple), P&M investment reported to DPIIT versus actual capitalisation in the fixed-asset register, and base-year adjustment for M&A activity are the three failure modes that surface at DPIIT claim review and lead either to claim rejection or claw-back of prior-year incentive.
- **Logic:** Build a DPIIT compliance register keyed by scheme applicant entity, product segment, and investment tier commitment; expand each quarter's compliance obligation into a check-list (progress report due date, cumulative P&M capitalisation figure, cumulative segment sales figure) and reconcile the quarter's DPIIT-reported number to the source registers — the fixed-asset register for P&M, the GSTR-1 HSN summary for segment sales. At FY-end, reconcile four quarters of DPIIT progress reports to the audited P&L and the audited fixed-asset register; reconcile the segment-level sales in the PLI claim workbook to GSTR-1 HSN summary at 6-digit level, applying the M&A adjustment to base-year sales; feed the DPIIT-empanelled CA firm the audit-ready workbook with source-register cross-references. Track the 7-month filing window from FY-end to the claim submission deadline.
- **Config:** Scheme applicant master with entity name, DPIIT registration number, product segment (MMF Apparel, MMF Fabrics, or one of the 12 Technical Textiles sub-categories), and investment tier (Category A ₹100 crore or Category B ₹300 crore); HSN mapping master keyed by SKU with 6-digit HSN, 2-digit Chapter, and qualifying MMF flag (fibre composition, fibre type); fixed-asset register with Plant and Machinery entries tagged for PLI-qualifying investment; base-year sales master with original DPIIT-registered base and any M&A adjustment; quarterly DPIIT progress report calendar with due dates and the cumulative P&M investment target for the quarter; annual claim workbook template with segment-level sales, incremental sales computation, and the CA certification block; TDS master mapping PLI-adjacent fees to Income-tax Act 2025 Section 8 codes — Sl. 15 code 1005 for CA firm certification fees (professional) and Sl. 4 code 1001/1002 for consultancy firm advisory fees (contractor).
- **Output:** A quarterly DPIIT compliance pack with the progress report draft, the P&M reconciliation to the fixed-asset register, and the segment sales reconciliation to the GSTR-1 HSN summary; an annual PLI claim workbook with the incremental sales computation, the M&A-adjusted base-year sales, the segment mix at 6-digit HSN, the four-quarter P&M capitalisation roll-forward reconciled to the audited fixed-asset schedule, and the audit-firm certification block; a TDS remittance summary for CA firm and consultancy fees under Income-tax Act 2025 Section 8 Sl. 15 code 1005 and Sl. 4 codes 1001/1002; and an audit-ready pack that ties every claim-line to a source register, ready for the DPIIT-empanelled CA firm to certify without additional reconciliation work.

### Handling DRC-01B Discrepancy Notices: Indian Taxpayer Response Playbook

Source: https://www.terra-insight.com/insights/drc-01b-discrepancy-notice-handling-india/

- **Problem:** GSTR-1 outward tax liability for a tax period exceeds GSTR-3B tax paid by a margin that crosses the Rule 88C threshold, triggering a system-generated DRC-01B Part A intimation with a 7-day reply window before the next GSTR-1 filing is blocked and Section 73/74 proceedings begin.
- **Logic:** Reconcile GSTR-1 (B2B, B2C, exports, credit notes, amendments) against GSTR-3B Table 3.1 tax head by tax head for the notice period and the surrounding two periods; identify whether the gap is a true short payment, a timing difference from later-period amendments, a credit note posting lag, or a portal data-fetch artefact; choose between paying differential through DRC-03 or filing a reasoned Part B reply.
- **Config:** Pull GSTR-1, GSTR-3B, and GSTR-2B for the notice period and the two adjoining periods; group outward supplies by tax head and by document type; map each invoice and credit note to the GSTR-3B Table where it was reported; quantify the absolute gap and the percentage gap against Rule 88C thresholds; draft the Part B narrative with statutory references to Rule 88C, Section 50, and Section 73.
- **Output:** Either a DRC-03 challan covering differential tax plus Section 50 interest with the challan number recorded in Part B, or a reasoned Part B reply with reconciliation annexures filed within 7 days; in either case the GSTR-1 filing block is lifted, no Section 73/74 notice is issued, and the period is closed for audit purposes.

### DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice

Source: https://www.terra-insight.com/insights/drc-01b-reconciliation-reply/

- **Problem:** DRC-01B is auto-generated under Rule 88C when GSTR-1 declared liability exceeds GSTR-3B paid tax by more than ₹1 lakh or 20% (whichever is lower). A seven-day reply window on the GST portal determines whether the case closes or escalates to a Section 73 (non-fraud) or 74 (fraud) demand with interest and penalty.
- **Logic:** Reply-preparation reconciliation matches every GSTR-1 invoice to the GSTR-3B output tax figure, classifying the gap as credit-note adjustment, amendment lag, data-entry error, or genuine short-payment. Each classification maps to a DRC-01B Part B option — (a) payment made, (b) adjustment explanation, or (c) other reasons — with supporting evidence attached.
- **Config:** Rule 88C threshold monitor (₹1 lakh or 20%), seven-day reply SLA tracker, DRC-03 voluntary payment workflow for short-payment cases, and reply-option router with evidence-file templates.
- **Output:** Pre-filed DRC-01B Part B reply draft, DRC-03 payment challan for genuine short-payments, evidence pack citing GSTR-1 Table 9 amendments or credit notes, and case-closure record for audit.

### DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice

Source: https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply/

- **Problem:** DRC-01C under Rule 88D is auto-issued when GSTR-3B ITC exceeds GSTR-2B ITC by more than ₹1 lakh or 20% (whichever is lower). Legitimate claims — IGST import ITC via ICEGATE, RCM self-invoiced credits, and amendments — look like excess claims to the portal unless the reply explains each delta within the seven-day window.
- **Logic:** Gap classification splits the GSTR-3B minus GSTR-2B variance into IGST import (Bill of Entry), RCM self-invoice, ISD distribution, previous-period catch-up, or true excess. Each category maps to DRC-01C Part B option (a) payment, (b) eligible ITC with evidence, or (c) other reasons. IMS actions for the next period are adjusted to prevent repetition.
- **Config:** Rule 88D threshold monitor, ICEGATE Bill of Entry evidence fetcher for IGST imports, RCM self-invoice register link, and seven-day reply SLA with DRC-03 workflow for true excess.
- **Output:** DRC-01C Part B reply draft with category-wise variance explanation, ICEGATE and BoE evidence pack, DRC-03 payment for any confirmed excess, and root-cause ticket to adjust IMS actions or RCM booking for future periods.

### DRC-01C under Rule 88D: GSTR-3B vs GSTR-2B Mismatch Notice Response

Source: https://www.terra-insight.com/insights/drc-01c-rule-88d-mismatch-india/

- **Problem:** GSTR-3B Table 4A ITC claimed exceeds GSTR-2B available ITC by more than ₹25 lakh or 20%, triggering a system-generated DRC-01C Part A intimation under Rule 88D with a 7-day reply window before GSTR-1 filing is blocked under Rule 59(6).
- **Logic:** Reconcile the differential line-by-line into four buckets — supplier timing (filed in a later month), ineligible credit under Section 17(5) wrongly claimed, genuine supplier non-filing being recovered, and reversal already made in a later GSTR-3B — then map each rupee of the gap to one bucket before drafting Part B.
- **Config:** Maintain a rolling 3-month GSTR-2A versus GSTR-2B versus purchase register reconciliation, a Section 17(5) blocked-credit register, and a supplier non-filer follow-up tracker. Lock the DRC-01C Part B reply template at the tax-period level with attachments for each bucket.
- **Output:** A Form DRC-01C Part B submission filed within 7 days containing the bucket-wise breakdown, a DRC-03 ARN for any amount paid with Section 50 interest, supporting reconciliation workings, and a re-opened GSTR-1 filing path under Rule 59(6).

### Drone Component Import Withholding Under Section 393(2) Sl. 17: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification

Source: https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india/

- **Problem:** Indian drone OEMs depend heavily on imported components — motors from China and Taiwan, GPS and flight controllers from US and Europe, propellers, gimbals, sensors, and software licences — each foreign remittance triggering Section 393(2) Sl. 17 withholding evaluation: pure-goods imports generally not chargeable, but royalty and FTS components are at DTAA-vs-Act rate determination, Form 15CA/15CB documentation, TRC and Form 10F requirements, and payment code 1057 deposit.
- **Logic:** Classify every foreign invoice line as goods (outside Section 393(2)), royalty (chargeable, DTAA royalty rate), FTS (chargeable, DTAA FTS rate), or interest; collect TRC and Form 10F for DTAA rate availability; file Form 15CA online before each remittance with Form 15CB Chartered Accountant certificate where required; deposit Section 393(2) Sl. 17 code 1057 withholding to government; maintain bank remittance trail referenced to Form 15CA acknowledgement; reconcile foreign-vendor 26AS/AIS data with cross-era legacy-Section 195 references for FY 2025-26 transition invoices.
- **Config:** Foreign-vendor master with country, TRC validity, Form 10F status, GSTIN-not-applicable flag, DTAA rate matrix per country and per income type (royalty / FTS / interest), HSN-to-classification map for goods-vs-service split, Form 15CA filing workflow with Form 15CB CA-certificate trigger above threshold, Section 393(2) Sl. 17 code 1057 ledger with quarterly TDS challan.
- **Output:** A monthly foreign-remittance reconciliation dashboard per foreign vendor showing remittance amount, classification of each line (goods/royalty/FTS/interest), DTAA rate applied vs Act rate, TRC and Form 10F validity, Form 15CA acknowledgement, Form 15CB CA-certificate reference, Section 393(2) Sl. 17 code 1057 deposited, and quarterly TDS return alignment to AIS/26AS.

### Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers

Source: https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india/

- **Problem:** Drone OEMs operate a pre-order / deposit driven sales model with large defence, agriculture and survey customers paying 20-50% advance against orders ranging from ₹50 lakh to ₹50 crore, creating multi-month gap between cash receipt and goods dispatch — with GST time-of-supply rules under Section 13 of the CGST Act (Notification 66/2017 exempting advance on goods from GST at receipt but services chargeable at receipt), advance receipt voucher under Rule 50, refund mechanism under Section 54 on cancellation, and Ind AS 115 revenue-recognition only on transfer of control at dispatch.
- **Logic:** Book each advance as customer-advance current liability on receipt, evaluate goods-vs-services classification per order line under Section 13 time-of-supply, issue advance receipt voucher under Rule 50 with proper detail, age customer-advance liability by customer and pre-order date, defer revenue recognition until transfer of control at dispatch under Ind AS 115, reconcile bank credit against the order's expected advance schedule, manage cancellation refunds against the original ARV with Section 54 refund claim on any service-portion GST collected and reversed.
- **Config:** Customer master with deposit schedule by order, order master with goods/services line split for GST classification, advance receipt voucher format compliant with Rule 50, bank-credit matching against expected advance amount and order reference, ageing buckets on customer-advance liability (0-30/31-90/91-180/180+ days), cancellation workflow with refund voucher and Section 54 refund tracking on any service-portion GST.
- **Output:** A monthly customer-advance reconciliation dashboard showing total deposit liability by customer and order, age buckets, advance receipt voucher register reconciled to bank credits, deferred revenue under Ind AS 115 ready for dispatch trigger, cancellation refund queue, Section 54 GST refund register for service-portion reversals, and dispatch-ready orders against held advances.

### Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits

Source: https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india/

- **Problem:** Indian drone manufacturers reconcile against a layered stack: PLI Drones incentive claims with a ₹120 crore base scheme, DGCA Drone Rules 2021 type-certification cost amortisation across R3/R4/R5 categories, pre-order customer deposits under GST time-of-supply rules, marketplace sales attracting Section 393(1) Sl. 8(v) e-commerce TDS code 1035, and foreign-supplier withholding for high-value components under Section 393(2) Sl. 17 code 1057.
- **Logic:** Reconcile PLI claim per audited eligible value-add against MoCA implementation-agency sanction and bank credit; amortise type-certification cost per model over expected commercial life under Ind AS 38 with R3/R4/R5 category-wise cost base; track customer deposits as a balance-sheet liability per customer and apply against invoice at dispatch with GST reckoned on invoice value; tie marketplace TDS deductions under code 1035 to gross sale value and Form 26AS; apply Section 393(2) Sl. 17 code 1057 withholding to service-component foreign payments only after Form 15CA/15CB and TRC checks.
- **Config:** Vendor master with PAN, GSTIN and TRC flag for foreign suppliers; customer master with deposit ledger by customer; type-certification asset register per drone model with R3/R4/R5 category tag and amortisation schedule; PLI eligible value-add calculation worksheet per financial year; marketplace settlement file format mapping for each e-commerce participant; Section 393(2) Sl. 17 DTAA rate matrix by country of supplier.
- **Output:** A monthly reconciled view of PLI claim status by quarter, type-certification amortisation booked per model, customer deposit liability aged by customer and pre-order date, marketplace TDS code 1035 deductions tied to gross sales and Form 26AS, and foreign-supplier Section 393(2) Sl. 17 withholding tied to Form 15CA/15CB filings.

### DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers

Source: https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india/

- **Problem:** Indian drone OEMs incur ₹10-50 lakh+ per model on DGCA Drone Rules 2021 type-certification across R3/R4/R5 categories, with the cost requiring Ind AS 38 capitalisation, useful-life amortisation over 3-7 years or units-of-production against committed run, impairment testing on failed attempts, and recertification cost capitalisation on Major design changes — all reconciled against unit sales of the certified model and any GST input credit on test fees paid to designated testing agencies.
- **Logic:** Capitalise direct certification cost per model under Ind AS 38 with attempt-level audit trail, amortise over expected commercial life (3-7 years) or units-of-production against committed run, write down failed-attempt cost to recoverable amount with impairment loss in P&L, classify design changes as Minor (capitalise as addition) or Major (new intangible asset + impairment test on original), claim GST input credit on certification-agency fees where eligible, reconcile per-unit amortisation against actual shipped units of the certified model.
- **Config:** Drone model master with TCDS reference, R3/R4/R5 category tag, capitalisation start date, attempt-level cost ledger (current attempt + any failed attempts written off), useful-life assumption, amortisation method (straight-line or units-of-production), committed unit run, design-change register with Minor/Major classification, GST input credit eligibility flag on each cost line.
- **Output:** A monthly intangible-asset reconciliation dashboard per drone model showing capitalised cost, attempt-level audit trail, accumulated amortisation, carrying amount, amortisation method, committed-vs-shipped units for units-of-production models, design-change register, impairment-test status, and GST input credit booked on certification-agency invoices.

### DSIR Form 3CL / 3CLA: Approval Trail and Year-End Reconciliation

Source: https://www.terra-insight.com/insights/dsir-form-3cl-3cla-r-and-d-approval-reconciliation-pharma/

- **Problem:** A DSIR-approved pharma R&D centre — for the reconciliation persona in this article, an illustrative Tier-2 speciality formulator's Aurangabad R&D centre approved by DSIR via Form 3CM issued October 2022 with three-year validity till October 2025 (renewed November 2025 for a further three-year cycle) — must, at year-end for FY 2026-27, run a complete reconciliation cascade from its R&D cost-centre general ledger through the DSIR-listed items eligibility filter to the Form 3CL quantum certification issued by the DSIR-empanelled Chartered Accountant, to the Form 3CLA return-of-income schedule, and into the ITR-6 tax computation for the audit-case Return of Income filing due 31 October 2027. The FY 2026-27 R&D cost-centre trial balance shows Rs 178 crore of revenue expenditure and Rs 68 crore of capital expenditure at the facility. The revenue expenditure must decompose into DSIR-eligible categories (scientific staff, consumables, clinical trial in-house costs, patent filing costs, publication costs, DSIR-listed items) and non-eligible categories (civil engineering, market research, testing outside the DSIR facility, general-purpose IT). The Form 3CM validity window must be verified to have covered the full financial year with no lapse gap. The book-tax gap between Ind AS 38 development-phase capitalisation and Section 35(2AB) revenue-expensed treatment must feed Ind AS 12 deferred tax computation.
- **Logic:** Extract the R&D cost-centre general ledger for the financial year from the accounting system, keyed to the DSIR-approved facility's cost-centre code. Decompose the aggregate revenue expenditure by cost-line category — scientific staff, consumables, clinical trial internal costs, patent filing and prosecution, cost of publications, DSIR-listed items, and non-DSIR categories (civil engineering, market research, external third-party testing, general-purpose IT and administrative allocation). Apply the DSIR-listed items eligibility filter to each category, flagging any line item that does not map cleanly to the DSIR Guidelines DSIR/Sec35(2AB)/1/2021 catalogue as a Form 3CL exclusion candidate. Verify Form 3CM validity for every day of the financial year and flag any lapse gap. Present the eligible-expenditure schedule to the DSIR-empanelled Chartered Accountant for Form 3CL certification. On receipt of Form 3CL, prepare the Form 3CLA return schedule showing the Form 3CM approval reference, the certified eligible quantum, the category-wise breakdown, and the 100 percent weighted-deduction computation. Reconcile the Section 35(2AB) tax deduction against the Ind AS 38 book treatment (research-phase expensed; development-phase capitalised subject to six-condition test) and compute the temporary-difference-driven deferred tax liability under Ind AS 12. Carry the Form 3CLA claim into the ITR-6 tax computation and file the Return of Income by the 31 October audit-case deadline.
- **Config:** R&D cost-centre master with DSIR-approved facility name, address, Form 3CM approval reference and validity period; general-ledger cost-centre code map from the accounting system to the DSIR facility; DSIR-listed items eligibility catalogue reference (Guidelines DSIR/Sec35(2AB)/1/2021) with per-category eligibility flag; scientific staff master with employee-level facility attribution (facility-dedicated vs corporate-shared); consumables purchase register with DSIR-eligibility tag per line item; clinical trial cost register with in-house-versus-CRO split and CRO-under-3CL-facility-scope flag; patent filing docket with attorney invoice register; DSIR-empanelled Chartered Accountant appointment record and audit engagement letter; Form 3CL certification workflow with pre-audit reconciliation pack; Form 3CLA return schedule template; Ind AS 38 research-phase vs development-phase treatment log with six-condition-test evidence; Ind AS 12 deferred-tax computation with temporary-difference tracking against the intangible carrying amount and tax base; Form 3CM renewal reminder trigger 90 to 120 days before expiry.
- **Output:** A year-end DSIR Form 3CL / 3CLA reconciliation pack for the R&D-approved pharma facility: the full R&D cost-centre general-ledger extract for the financial year decomposed by DSIR-listed items eligibility category with per-line-item eligibility flag; the eligible-versus-non-eligible summary schedule for CA pre-audit review; the Form 3CL certification memorandum from the DSIR-empanelled Chartered Accountant with certified eligible quantum; the Form 3CLA return schedule ready to attach to the ITR-6 Return of Income filing; the Section 35(2AB) weighted-deduction computation carried into the ITR-6 tax working; the Ind AS 38 research-vs-development treatment log with capitalised-intangible carrying amount and expensed-research charge; and the Ind AS 12 deferred tax liability computation with temporary-difference workings and unwind schedule against the intangible amortisation profile. A Form 3CM validity monitor surfaces the facility-approval expiry against the renewal-application trigger threshold.

### Genuine vs False Duplicate Loan Payment: Detection Logic for Gold-Loan NBFCs

Source: https://www.terra-insight.com/insights/duplicate-loan-payment-detection-genuine-vs-false-nbfc-india/

- **Problem:** A gold-loan borrower who holds two live pledges frequently pays both instalments on the same day, minutes apart, through the same UPI app or mobile banking channel. Naive duplicate-detection rules keyed on customer identifier plus amount plus value date flag the second payment as a duplicate and suspend it, starving one of the two loans of its EMI while showing the borrower's bank account debited twice.
- **Logic:** Key duplicate detection on customer identifier plus loan account number plus instalment number plus amount plus value date. Read UPI Retrieval Reference Number and NACH mandate reference for disambiguation — same reference across two credits is a switch retry, different references are two economic events. Route the exception to a review queue only when the strong key genuinely matches; auto-post when any of the key fields differ.
- **Config:** Duplicate rule parameter set — the fields that form the strong key, the source instruments in scope, the tolerance windows for timestamp and value date. Borrower-to-loan-account map so a UPI credit against a single VPA can be split across the borrower's active loan accounts. Reference-number capture at the switch-to-ledger boundary so RRN and mandate reference are not lost during file ingestion.
- **Output:** Duplicate exceptions raised only on true collisions, genuine same-day repeats posted straight through, loan-account-level ledgers that reflect exactly what the borrower paid, and an audit trail satisfying the Fair Practices Code's acknowledgement obligation.

### Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review

Source: https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement/

- **Problem:** Duplicate transactions in bank statement forensics require distinguishing between two very different causes: genuine duplicates from overlapping multi-statement uploads or bank processing anomalies, and fabrication-driven duplicates where copy-paste transaction volume inflation produces identical entries without corresponding real-world events.
- **Logic:** After period deduplication of the combined statement set, identify exact duplicate entries by matching on transaction date, normalised description, and amount. Classify each duplicate by probable cause: overlapping period (resolved by deduplication), possible bank processing double (check for reversal entry), or unexplained duplicate (no reversal, no period overlap — flag for review). Compute the duplicate rate as a percentage of total transactions.
- **Config:** Period deduplication step: before forensic analysis, identify and remove transactions appearing in multiple uploaded PDFs due to overlapping date ranges. Normalise descriptions by stripping reference codes and padding before matching. Apply a rounding tolerance of ±₹1 for amount matching to catch minor formatting variations.
- **Output:** Duplicate transaction list with: date, description, amount, occurrence count, and probable cause classification. Duplicate rate as a percentage of total transactions. A distinction between period-overlap duplicates (resolved by deduplication) and within-period unexplained duplicates (flagged for review), surfaced in the fraud signals section of the analysis report.

### Dwarikesh Sugar EBP Ethanol Blending 2025-26 Reconciliation

Source: https://www.terra-insight.com/insights/dwarikesh-sugar-ebp-ethanol-blending-2025-26-reconciliation/

- **Problem:** An integrated sugar-plus-distillery group of the scale that Dwarikesh Sugar Industries operates — a 130 KLPD distillery drawing molasses from three own sugar plants (approximately 55 percent of feedstock) supplemented by purchased molasses from unaffiliated mills (approximately 45 percent) — must reconcile a 4.1 crore-litre ethanol production target for the 2025-26 EBP supply year against a joint-tender OMC allocation split IOCL 45 percent, BPCL 30 percent, HPCL 25 percent, and a monthly tanker lifting invoice per OMC per depot at an illustrative blended realisation of Rs 61.5 per litre. Every litre must trace through five hops — distillery batch log, feedstock cost per KL, OMC allocation letter, monthly lifting invoice per OMC per depot, and OMC settlement receipt — while the upstream Sugarcane Control Order 1966 Clause 3(3A) 14-day cane payment obligation with 15 percent per annum interest on arrears cascades into the molasses cost line, Section 194Q code 1031 TDS at 0.1 percent applies to the purchased-molasses leg above the Rs 50 lakh per-seller threshold, and the Rule 89(5) inverted-duty refund cycle on 5 percent output ethanol against 18 percent input chemicals runs monthly. Manual reconciliation across five cascading hops loses per-batch yield visibility, over-states cumulative OMC lifting against the pro-rated allocation curve, and mis-classifies capital-goods ITC into the Net ITC numerator of the refund draft.
- **Logic:** Ingest the distillery batch log at intake with per-batch feedstock grade (B-heavy, C-heavy, cane juice, damaged foodgrains, maize), TRS assay, and ethanol volume yielded at the distillation column outlet, computed against the theoretical TRS-implied maximum. Build a feedstock cost register combining own-plant transfer pricing (based on the aggregated cane cost per tonne under Clause 3(3A) discipline) with purchased-molasses landed cost, transport, GST at 5 percent, and Section 194Q TDS at code 1031 (0.1 percent) on suppliers above the Rs 50 lakh aggregate threshold. Ingest the OMC allocation letter from the joint tender with per-OMC per-depot volume commitment, per-feedstock price band, and payment cycle. Track cumulative lifting progress per OMC per depot against the pro-rated allocation curve on a weekly cadence to flag under-lifting risk with three months of supply-year runway remaining. Each tanker dispatch reconciles against a lorry receipt, an ARE-1 removal, a GST tax invoice at 5 percent, an e-way bill under Rule 138, and an e-invoice IRN generated through the IRP portal; the OMC's depot warehouse acknowledgment closes the loop. Extract input GST at 18 percent and output GST at 5 percent from GSTR-1 and GSTR-3B into the Rule 89(5) refund workbook, apply the Notification 14/2022 amended formula with input services and capital goods correctly excluded from Net ITC, and generate the GST RFD-01 filing base monthly.
- **Config:** Distillery master with unit code, KLPD capacity, state excise licence number, and bonded storage capacity; feedstock master with grade (B-heavy, C-heavy, cane juice, damaged foodgrains, maize) and per-grade theoretical yield curve; molasses supplier master with own-plant vs third-party flag, GSTIN, PAN, TDS payment code (1031 for 194Q eligible), and Section 43B(h) MSME flag; OMC allocation master keyed to each joint-tender cycle with per-OMC per-depot volume commitment and per-feedstock price fixation; depot master with GSTIN, zone assignment, distance from distillery, and typical transit time; state excise submission calendar for ARE-1 removals under alcohol control supervision; upstream cane grower master feeding into the Clause 3(3A) 14-day payment tracker with FRP-plus-SAP rate schedule per season and interest accrual rule at 15 percent per annum; GSTR-1 and GSTR-3B feed for the Rule 89(5) refund workbook; capital-goods and input-services register segregated at source so Net ITC in the refund formula draws only from the eligible base.
- **Output:** A month-end EBP-cycle reconciliation pack: opening feedstock inventory by grade at each unit, per-batch feedstock-to-ethanol yield tally with variance-band exceptions, weighted-average feedstock cost per KL of ethanol produced, OMC allocation drawdown progress per OMC per depot against the pro-rated supply-year curve, monthly tanker lifting register with tanker count, volume, invoice value, ARE-1 number, e-way bill number, and IRN cross-referenced against depot warehouse acknowledgment, OMC settlement receipt reconciliation against invoice value on the 15-day payment cycle, Section 194Q code 1031 TDS reconciliation on purchased-molasses payments keyed to each supplier PAN with Form 26AS credit trace, Rule 89(5) refund draft with the Notification 14/2022 amended formula and capital-goods plus input-services correctly excluded from Net ITC, and an upstream cane-payment tracker under Clause 3(3A) with interest accrual computed on any delayed settlement beyond the 14-day window and cascaded into the molasses cost line.

### Dyeing & Printing Job-Work TDS — Section 393(1) Code 1023 for Textile

Source: https://www.terra-insight.com/insights/dyeing-printing-job-work-textile-tds-code-1023/

- **Problem:** A Surat, Bhilwara, or Tiruppur textile principal deducting TDS on wet-processing conversion charges paid to partner dyers must apply the correct Income-tax Act 2025 Section 393(1) Sl. 4 code — 1023 where the principal supplies the material (the standard textile case) or 1024 where the dyer supplies the material — apply the correct rate (1 percent Individual or HUF, 2 percent other resident), track the ₹30,000 single-payment or ₹1,00,000 aggregate-per-FY threshold per PAN, file Form 26Q quarterly, generate Form 16A within 15 days of the return due date, and reconcile the credit against the dyer's Form 26AS. A code misclassification (1024 or 1002 in place of 1023) or a PAN spelling error in Form 26Q lands the credit at the wrong deductee, the dyer's Form 26AS falls short, and the dyer files a reconciliation query that the principal must trace back through the Form 26Q correction cycle. A missed deduction on an invoice below the ₹30,000 single-payment mark but above the ₹1,00,000 cumulative mark exposes the principal to interest under Section 201(1A) and disallowance under Section 40(a)(ia).
- **Logic:** Build a per-dyer master keyed by PAN carrying the dyer's status (Individual, HUF, partnership, LLP, private limited, other), the applicable TDS rate (1 or 2 percent), the payment code (1023 for principal-supplied material, standard case; 1024 for dyer-supplied material, the exception), and the running-FY cumulative for the ₹1,00,000 aggregate test. Ingest every dyer invoice with an explicit material-supplied flag (does the invoice reference the Rule 55 delivery challan that dispatched the fabric, or does it reference a purchase order for finished material sourced by the dyer?). Route each invoice into the correct code (1023 versus 1024). Compute TDS at the applicable rate. Cross-check the single-payment threshold on the current invoice and the cumulative-payment threshold on the running FY total per PAN. Generate the Form 26Q line item with deductee PAN, gross amount, TDS, payment code, and challan reference. Cross-check the dyer's Form 26AS after the quarterly filing cycle to confirm the credit landed at the correct PAN with the correct code.
- **Config:** Dyer master with PAN, status, TDS rate slab (1 or 2 percent), and default payment code (1023 for standard textile chain; 1024 as exception); Rule 55 delivery challan cross-reference on every dyer invoice — the challan reference proves the material-supplied test and locks the code as 1023; invoice-level threshold tracker with single-payment ₹30,000 and aggregate ₹1,00,000 per PAN per FY; Form 26Q generation configuration with deductor TAN, address, responsible person; Form 16A generation queue with 15-day post-return-due-date SLA; Form 26AS reconciliation feed from the dyer's PAN with quarterly tie-out to the principal's deduction register; alert on code 1024 or 1002 usage against a PAN that historically transacted under 1023 (probable code misclassification).
- **Output:** A per-dyer per-quarter TDS pack: dyer name, PAN, running FY cumulative, invoices in period, TDS deducted per invoice under code 1023, quarterly total deducted, quarterly total deposited, Form 26Q line items ready for filing, Form 16A generation queue, and Form 26AS variance report. Threshold-crossing report flags dyers approaching ₹90,000 cumulative — the trigger for imminent aggregate-threshold TDS deduction. Code-boundary exception report surfaces any invoice tagged 1024 where the dyer's historic pattern is 1023 — flagging probable material-supplied test error. Form 26Q draft populates with the correct payment code, rate, and challan reference for every deduction. The audit-ready pack ties every deduction to a Rule 55 delivery challan, a dyer invoice, and a TDS deposit challan.

### Microsoft Dynamics 365 India Localisation for Auto-Component Manufacturers: What's Missing

Source: https://www.terra-insight.com/insights/dynamics-365-india-localisation-auto-component-gaps/

- **Problem:** Indian auto-component Tier-1 manufacturers evaluating Microsoft Dynamics 365 F&O get strong India localisation (GST, TDS Income Tax Act 2025 codes 1001-1092 from FY 25-26 patch, e-invoice, e-way bill), competitive total cost of ownership versus SAP / Oracle at the ₹100-300 crore band, and the Microsoft ecosystem integration advantage. They still face seven recurring gaps versus SAP-grade scheduling-agreement supply — no SA equivalent at LP / LPA grade, no native OEM EDI 830 / 862 / 856 inbound mapping, no cum-quantity drift exception engine, single-hop-only ITC-04, no supplier-side free-issue Rule 55 tracking, no RMPV index-linked pricing, no native OEM portal extract parser. The thin Indian auto-component D365 ISV ecosystem leaves the gap-closing burden on internal customisation and companion-product integration.
- **Logic:** Map D365 F&O's procurement, supply-chain and India-localisation modules against the 10 auto-component reconciliation streams, identify the seven recurring gaps that fall outside native scope, document the D365-specific workaround pattern per gap (Logic Apps for OEM portal inbound, custom data entities + Power Automate flow for cum-drift, Data Entities export + companion product for RMPV / multi-hop / free-issue / Section 143), and frame the hybrid D365 + companion-product architecture for a mid-Tier-1.
- **Config:** Dynamics 365 F&O install with Procurement and Sourcing, Supply Chain Management, Cost Management, Inventory Management, India Localisation enabled, Blanket Purchase Agreement document type configured for SA-equivalent inbound supply, Sales and Purchase order processing for outbound and inbound, India Localisation withholding tax configured for Income Tax Act 2025 codes 1001-1092, e-invoice through IRP, e-way bill module, Data Entities scheduled export through Logic Apps to a staging area, Logic Apps integrations per OEM portal (e-Nagare, TML SRM, M&M Supplier Portal, SupplyOn) for ASN and call-off inbound.
- **Output:** A D365 + companion-product hybrid operating model with D365 as books-of-account and procurement / supply-chain system of record, the companion product consuming Data Entities exports plus OEM portal exports and running the seven gap streams externally as continuous reconciliation, total cost of ownership lower than the SAP S/4HANA equivalent at the ₹100-300 crore revenue band, and the Microsoft ecosystem integration advantage retained.

### E-Axle Supplier Reconciliation for Indian EV OEMs: Modular vs Integrated Supply

Source: https://www.terra-insight.com/insights/e-axle-supplier-reconciliation-india/

- **Problem:** An Indian e-axle Tier-1 supplier to EV OEMs like Mahindra Electric, Tata Motors EV and Pininfarina operates in a commercial structure materially different from ICE Tier-1 patterns — high content density per unit (₹6-9 lakh), low part-count, OEM-specific tooling amortised over committed platform-life volume, RMPV exposure on rare-earth magnets and power semiconductors, PLI-Auto Component eligibility with 50 percent component-level DVA threshold, and warranty exposure measured in years. The reconciliation must hold standard goods-supply revenue, tooling-amortisation ledger, RMPV claim register, warranty accrual, three-sub-system BoM with domestic-vs-imported tagging and Section 393 code 1031 TDS receivable on the same data thread.
- **Logic:** Maintain an e-axle SKU master with three-sub-system bill-of-materials (motor / gearbox / inverter+ECU) each line tagged domestic or imported referenced to supplier GSTIN invoice or Bill of Entry. Compute per-batch component-level DVA aggregated across the three sub-systems. Run RMPV claim register tied to published rare-earth and semiconductor reference indices with quarterly OEM claim files. Maintain tooling-amortisation ledger per platform per OEM with per-unit recovery rate; classify as goods-supply or service-supply per commercial arrangement. Accrue warranty provision per Ind AS 37 at platform-specific failure-rate assumption. Recognise revenue at Ind AS 115 control transfer with separate PO for tooling-recovery where applicable. Deduct Section 393(1) Sl. 8(ii) code 1031 TDS at 0.1 percent on purchases above ₹50 lakh FY threshold.
- **Config:** E-axle SKU master with platform-OEM mapping; three-sub-system BoM with domestic-or-imported flagging per line; supplier master and Bill-of-Entry register; rare-earth-magnet RMPV reference-index tracker with trigger band per OEM contract; tooling-amortisation ledger per OEM platform with committed volume and per-unit recovery; warranty-provision computation per platform per quarter; PLI-Auto Component registration with base-year and incremental-sales calculator; Ind AS 115 multi-PO transaction-price allocation; Section 393 code 1031 TDS receivable ledger; Form 26AS quarterly reconciliation by OEM TAN.
- **Output:** A per-batch component-level DVA reconciliation pack with three-sub-system BoM evidence; per-platform RMPV claim file with reference-index history and OEM filing status; tooling-amortisation recovery report tied to platform-life volume against actual draw; Ind AS 37 warranty accrual per platform; quarterly PLI-Auto Component claim file with PMA-IFCI methodology; Section 393 code 1031 TDS chase against Form 26AS by OEM TAN; clawback-resistant audit trail per unit sold tying revenue, RMPV recovery, tooling recovery and warranty accrual to the same SKU-batch.

### e-BRC (Electronic Bank Realisation Certificate) Textile Export Reconciliation

Source: https://www.terra-insight.com/insights/e-brc-electronic-bank-realisation-certificate-textile-export/

- **Problem:** A Karur home-textile exporter shipping bed linen to US retail must reconcile the shipping bill FOB value in USD at the CBIC-notified customs exchange rate, the buyer's SWIFT remittance in USD (typically short-realised by small deductions for freight, commission, or quality claims), the AD bank's INR credit at the bank's declared conversion rate on realisation date, and the DGFT-issued e-BRC — all inside the FEMA 9-month realisation window. Manual reconciliation loses the linkage between shipping bill, SWIFT MT-103 message, EDPMS IRM tag, and e-BRC upload; short-realisation events are not routed to buyer AR for reconciliation, and RoDTEP/RoSCTL/EPCG EO credits stall in the DGFT queue while the exporter cannot explain the gap between claimed and disbursed scrip value.
- **Logic:** Build a shipping bill register keyed by SB number and IEC that carries FOB in foreign currency, customs exchange rate for the fortnight, FOB in INR, scheme flag (RoDTEP 4R vs 4RE; RoSCTL yes/no; EPCG authorisation reference if any), and expected realisation date at 9 months from shipping date. Ingest the AD bank's SWIFT MT-103 credit advice and match to the shipping bill by IEC, buyer, invoice reference, and value tolerance. Ingest the EDPMS export ledger and confirm IRM-to-SB linkage. Ingest the e-BRC download from the DGFT portal and confirm realised value in foreign currency, INR credit at bank rate, and realisation date match SWIFT + EDPMS. Compute short-realisation as (invoice foreign currency − realised foreign currency) and route to buyer AR. Run FEMA aging at 180, 240, and 270 days from shipping bill date. Feed RoDTEP/RoSCTL claim engine only with SB-e-BRC pairs that are complete and inside the window; feed EPCG EO tracker with EPCG-flagged SB-e-BRC pairs summed against the 6-year block-year EO.
- **Config:** Shipping bill master with SB number, IEC, port of loading, FOB in foreign currency, customs exchange rate, FOB in INR, scheme flag (RoDTEP 4R/4RE, RoSCTL, EPCG authorisation number), FEMA realisation clock start date; SWIFT MT-103 feed from the AD bank with sender BIC, beneficiary IEC, foreign currency amount, USD value date, and buyer reference; EDPMS export ledger extract with SB-to-IRM linkage; e-BRC download from DGFT with SB reference, realised foreign currency, INR credited, bank rate, realisation date; FEMA Master Direction 9-month realisation window with alert thresholds at 180, 240, and 270 days; RoDTEP Appendix flag (4R for DTA; 4RE for AA/EOU/SEZ) per SKU; EPCG authorisation register with 6-year EO block calendar; short-realisation write-off policy against FEMA self-write-off and AD-approved-write-off limits.
- **Output:** A month-end export realisation pack: shipping bills exported in the period, SWIFT credits received in the period linked to SB, EDPMS reconciliation status per SB, e-BRC status per SB (issued, pending, mismatched), short-realisation gap per SB with buyer AR routing, FEMA aging bucket per SB (0-180, 181-240, 241-270, 271+), RoDTEP/RoSCTL claim readiness per SB (SB-eBRC pair complete inside window), and EPCG EO fulfilment per authorisation summed year-on-year against the 6-year block obligation. The pack also produces the XOS pre-flight — shipping bills approaching 270 days without a linked IRM — so the exporter can chase the buyer and the AD bank before the RBI reporting cycle picks them up.

### E-Invoice and E-Way Bill for Auto-Component JIT Delivery: High-Frequency Despatch Compliance

Source: https://www.terra-insight.com/insights/e-invoice-e-way-bill-auto-component-jit-india/

- **Problem:** Auto-component Tier-1 suppliers run high-frequency JIT despatch to OEMs — dozens of part-specific consignments per day matched to the OEM line schedule under EDI 862 / 866 calls — and every single despatch crosses two parallel statutory gates: the e-invoice IRN under the IRP for any taxable supply by a registered person above the ₹5 crore turnover threshold, and the e-way bill under Rule 138 for any consignment whose value (single or aggregated by conveyance) exceeds ₹50,000; the two systems run independent 24-hour cancellation clocks, demand IRN-to-invoice-to-ASN-to-e-way-bill quantity tie-out, distinguish taxable supply from returnable-bin gate-pass movement under Rule 55, and apply different threshold logic when cross-state movements aggregate multiple sub-₹50,000 ASNs onto one truck.
- **Logic:** Generate IRN on the IRP before truck departure; classify the despatch as taxable supply or returnable-bin Rule 55 movement; for taxable supply, generate single e-way bill if consignment value exceeds ₹50,000 or queue for consolidated e-way bill if multiple sub-threshold ASNs aggregate onto the same conveyance; tie IRN to ASN (EDI 856) on quantity and PO release; track the 24-hour cancellation clocks per IRN and per e-way bill independently; for returnable bin movement, issue Rule 55 delivery challan and e-way bill if value exceeds ₹50,000, no IRN; reconcile end-of-day to ASN dispatched, IRN generated, e-way bill issued and consolidated bills referenced; surface gaps to the OEM gate pass before the truck rolls.
- **Config:** Tier-1 GSTIN per plant; OEM GSTIN per ship-to; transporter master with GSTIN, transporter ID and conveyance plate; PO and PO-release master from EDI 830/862/866; ASN template (EDI 856) per OEM; IRN generation route per OEM and per invoice type; e-way bill template with Part-A (consignor/consignee/HSN/value) and Part-B (vehicle); consolidated e-way bill rule per conveyance; Rule 55 delivery challan series for returnable bins; cancellation watch on the 24-hour clock per IRN and per e-way bill.
- **Output:** An end-of-day despatch register tying every ASN to its IRN, e-way bill (single or consolidated), Rule 55 challan (if applicable), OEM gate-pass acknowledgement and EDI 856 transmit log; a 24-hour cancellation tracker for any IRN or e-way bill not yet matched to a moved truck; a returnable-bin float register integrated with the same conveyance reconciliation; and a pre-GSTR-1 register of IRNs that ties back to the same despatch volumes by the 10th of the following month.

### e-Invoice IRN Reconciliation: Books vs IRP Repository for Indian Businesses

Source: https://www.terra-insight.com/insights/e-invoice-irn-reconciliation-india/

- **Problem:** ERP issues invoices and the IRP holds the authoritative IRN repository, but the two registers drift apart through missed IRN generation, expired cancellation windows, schema rejections, and amount truncation, leading to GSTR-1 mismatches and ITC denial for recipients.
- **Logic:** Pull the ERP invoice register and the IRP IRN repository for the same period, match on invoice document number and date, then classify exceptions into ERP-without-IRN (compliance gap), IRP-without-ERP (cancelled or missed posting), and matched-but-amount-mismatch (rounding, truncation, GST recompute).
- **Config:** Set the reconciliation period to one GST return month, include all six IRPs the entity uses, freeze the ERP register at GSTR-1 filing cutoff, and apply a one-rupee tolerance for GST rounding under Section 170 while flagging anything above that for review.
- **Output:** A four-bucket exception report: missing IRNs requiring urgent IRP push within the 30-day window, stale cancellations needing credit-note reversal in books, amount mismatches with the variance and root cause, and a clean-matched register ready for GSTR-1 auto-flow verification.

### E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment

Source: https://www.terra-insight.com/insights/e-invoice-reconciliation-india/

- **Problem:** E-invoicing auto-populates GSTR-1 and GSTR-2B but introduces its own mismatches: cancelled IRNs still appearing in 2B, invoices scattered across six private IRPs plus the government portal, and post-24-hour amendments that must be handled through credit or debit notes since the original IRN is locked.
- **Logic:** Reconciliation unifies IRN feeds from every IRP used by the supplier base, matches each IRN against the purchase register using invoice number plus supplier GSTIN plus IRN plus tax period, then cross-checks the same IRN against GSTR-2B. Cancelled-within-24-hours IRNs are suppressed; post-cancellation entries are routed to the next 2B cycle via credit-note reconciliation.
- **Config:** Multi-IRP ingestion for Cygnet, Clear, IRIS, EY, Deloitte, Masters India, and the government IRP; IRN status tracker (active, cancelled, amended-via-CDN); and threshold mapping for the ₹5 Crore e-invoice mandate plus B2C carve-outs.
- **Output:** A single IRN ledger per tax period, purchase-register-to-IRN-to-GSTR-2B three-way reconciliation, cancelled-IRN exception list, and evidence pack for every credit or debit note that corrected a locked IRN.

### E-Invoicing for FMCG below ₹5 crore — IRN Generation and Reconciliation

Source: https://www.terra-insight.com/insights/e-invoicing-fmcg-5-crore-threshold-reconciliation/

- **Problem:** Mid-market Indian FMCG manufacturers whose aggregate turnover crosses ₹5 crore fall into e-invoicing scope under Rule 48(4) of the CGST Rules 2017 read with CBIC Notification 10/2023-CT effective 1 August 2023, and must generate an Invoice Reference Number on the NIC Invoice Registration Portal for every B2B tax invoice. The reconciliation problem sits in three surfaces: distributor GSTIN drift causes silent IRN generation failures that hold up dispatches; the 24-hour cancellation window closes without night-shift authorisation; and the auto-populated GSTR-1 diverges from the internal IRN register when late-shift invoices, in-window cancellations, and post-window credit notes are not tracked as separate flows. Mid-market FMCG operations with 200 to 500 distributors typically see two to five GSTIN drift events per quarter and 3 to 8 percent of B2B invoice value at risk of GSTR-1 divergence at any month-end.
- **Logic:** Build a distributor master keyed by GSTIN, PAN, state, and registration status, and reverse-match it daily against a GSTN status pull on the top-100 distributors by dispatch volume. Route every B2B invoice through the IRP integration; capture the IRN, acknowledgement number, acknowledgement date, and QR-code payload; write the tuple to the e-invoice register. Enforce a 24-hour cancellation clock at the register level, with night-shift authorisation for late-cutoff dispatches. At month-end, run a three-pass reconciliation: IRN population against auto-populated GSTR-1 (count and rupee value), in-window cancellations against GSTR-1 reversal, and Section 34 credit notes for post-window corrections against the credit-note table. Route mismatches to a resolution queue by distributor GSTIN and invoice number for closure before GSTR-1 commit.
- **Config:** Distributor master with GSTIN, PAN, state, registration status, and last-verified date; SKU master with HSN, tax rate at time of supply (with pre-22-September 2025 versus post-22-September 2025 flag for GST 2.0 rationalised categories), and unit of measure; IRP integration credentials (GSP or direct API access to einvoice1.gst.gov.in via the NIC-published integration path); daily GSTN status pull on top-100 distributors; e-invoice register schema (invoice number, IRN, ack no., ack date, QR payload, cancellation status, cancellation date); night-shift IRP-cancellation authorisation roster; month-end three-pass reconciliation configuration with tolerance thresholds.
- **Output:** A month-end e-invoicing reconciliation pack: IRN generation register cross-footed to dispatch invoices raised; in-window cancellation register with reason codes; post-window credit-note register with Section 34 linkage; GSTN auto-population comparison with count and rupee gaps; distributor GSTIN drift alerts with resolution status; and a pre-filing GSTR-1 sign-off certificate. The pack feeds the monthly GSTR-1 filing (due 11th of the following month for taxpayers with aggregate turnover above ₹5 crore) and the year-end GSTR-9 reconciliation, and surfaces IRP integration health metrics — generation success rate, average generation latency, cancellation rate, and daily rejection register.

### E-Invoicing for Textile under ₹5 Crore Threshold — IRN Reconciliation

Source: https://www.terra-insight.com/insights/e-invoicing-textile-5-crore-threshold-irn-reconciliation/

- **Problem:** A mid-tier Ludhiana hosiery manufacturer with FY 2024-25 aggregate turnover of ₹18 crore is above the ₹5 crore e-invoicing threshold (Notification 10/2023-Central Tax) and must generate an IRN for every B2B tax invoice, export invoice, credit note, and debit note before issuing the document. Monthly B2B invoice volume runs 400 to 500 documents through the IRP portal. Reconciliation gaps arise on four fronts: IRN generation lag against the physical dispatch clock (dispatches held up because the IRP is slow to respond); missed 24-hour cancellations for data-entry errors caught late; GSTR-1 e-invoice section drift against the internal IRN register (typically from over-edits during return preparation); and IRP-reported turnover drift against GSTIN turnover reported on GSTR-1 and GSTR-3B. Missed IRNs on B2B invoices render the invoice invalid under Rule 48(5) — the counterparty cannot claim ITC, and the seller is exposed to a Section 122 penalty for defective invoicing.
- **Logic:** Build an IRN register keyed by internal invoice number, with the IRP-issued IRN, IRP acknowledgement number, IRP acknowledgement date, e-way bill number (if any), and cancellation flag. Ingest the IRP portal's daily download and cross-verify against the ERP invoice register — every ERP invoice above the B2B threshold must have a matched IRN row, and every IRP-portal row must have a matched ERP invoice. Track IRN generation lag as the time between ERP invoice creation and IRN issuance — flag lags above a defined SLA (typically 15 seconds for API integration, 5 minutes for offline utility). Track the 24-hour cancellation clock for every IRN — flag defective invoices caught between 12 and 24 hours from IRN generation as urgent cancellation candidates. At return-filing cycle-end, reconcile the IRN register against the GSTR-1 auto-populated e-invoice section (Tables 4A, 4B, 6A, 6B, 6C, 9A, 9B) invoice-by-invoice; reconcile IRP-reported turnover against GSTR-1 outward supplies; and reconcile GSTR-1 outward supplies against GSTR-3B.
- **Config:** Aggregate turnover threshold set at ₹5 crore aggregate (Notification 10/2023-Central Tax) with a cascade fallback for prior thresholds (₹10 crore, ₹20 crore) for historical audits; IRN generation channel per seller GSTIN (API integration, offline utility, GSP intermediary); IRN generation SLA thresholds (15 seconds for API, 5 minutes for offline utility) — dispatch gate blocks physical movement if IRN is not received; 24-hour cancellation clock with alerts at 12 and 20 hours from IRN generation; document-type coverage (B2B tax invoice, export invoice, B2B credit note, B2B debit note) — B2C excluded from IRP; GSTR-1 e-invoice section table mapping (4A for B2B, 4B for reverse-charge B2B, 6A for exports with payment, 6B for exports without payment, 6C for supplies to SEZ, 9A for amendments, 9B for credit/debit notes); Rule 46(r) B2C QR code flag (applies only above ₹500 crore turnover — off for mid-tier textile units); TDS payment code 1023 tagging on job-work conversion invoices where the seller is a textile principal supplying material.
- **Output:** A month-end IRN reconciliation pack: total B2B invoices issued in the period, total IRNs generated, IRN generation lag distribution (median, p95), 24-hour cancellation compliance rate (cancelled within 24 hours vs credit-noted after 24 hours), IRN register versus GSTR-1 e-invoice section line-by-line variance list, IRP-reported turnover versus GSTR-1 outward supplies variance, and GSTR-1 versus GSTR-3B outward supplies variance. Per-invoice defective-IRN list with root cause (incorrect GSTIN, incorrect HSN, incorrect tax rate, missing e-way bill link). Return-filing draft populates the GSTR-1 e-invoice section from the IRN register, matching the IRP auto-populated data, so the filing preparer reviews only the variances rather than re-keying the invoice detail.

### ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching

Source: https://www.terra-insight.com/insights/echs-reconciliation-india/

- **Problem:** ECHS settlements take 60-120 days through Station HQ, with package rate disputes and polyclinic referral chain compliance adding reconciliation layers that hospitals must track per beneficiary.
- **Logic:** Validate polyclinic referral and smart card, match claim to ECHS package rate, track settlement through Station HQ and Regional Centre, reconcile against bank credit.
- **Config:** ECHS package rates (different from CGHS), polyclinic referral mandatory, smart card validation, ~55 lakh beneficiaries, settlement cycle 60-120 days.
- **Output:** ECHS claim status tracker, package rate dispute register, referral compliance report, and settlement aging analysis by Station HQ.

### E-commerce Operator vs Participant Under Section 194O / §393(1) Sl. 8(v): Who Deducts What

Source: https://www.terra-insight.com/insights/ecommerce-operator-vs-participant-194o-india/

- **Problem:** A multi-channel D2C brand pulls revenue through its own website, two marketplace operators and a direct B2B billing flow, each with a different TDS posture under Section 194O / §393(1) Sl. 8(v). The own-website flow attracts no 194O at all because the gateway is not an operator. The marketplaces deduct 0.1% on gross credited or paid to the brand, but the brand books revenue net of GST and commission and sees a structural gap when comparing the deduction to its ledger. The direct B2B flow runs under buyer-side 194Q at 0.1% above the ₹50 lakh threshold, which is a different mechanism on the buyer's side entirely. Form 26AS arrives with entries split by deductor TAN and the team treats them as one undifferentiated stream, missing per-channel mismatches until the ITR window closes.
- **Logic:** Classify every channel as operator-deducts, gateway-only or B2B-buyer-deducts before any reconciliation begins. Split Form 26AS entries by deductor TAN and route each to the matching channel bucket. Recompute the expected 0.1% from the operator's settlement statement on the gross amount credited or paid, applying the rate calendar across the 1 October 2024 cut and the 1 April 2026 code transition. Validate that the own-website channel has no 194O credit at all and treat any entry there as an exception. Track 194Q entries flowing in from B2B buyers separately, keyed to the buyer's TAN and the ₹50 lakh threshold. Maintain a standing variance register at the operator-TAN grain for the audit file.
- **Config:** Per-channel TDS posture map covering own-website, marketplace operator, direct B2B and aggregator 9(5) flows. Operator TAN dictionary with deductor identifiers for Amazon, Flipkart, Meesho, Ajio, Zomato, Swiggy and any other live platform. Rate calendar with the 1 October 2024 rate cut (1.0% to 0.1%) and the 1 April 2026 code migration (194O to §393(1) Sl. 8(v) payment code 1035). Gross-amount calculator that adds GST on marketplace commission and fees back to the net-of-GST ledger figure for like-for-like comparison.
- **Output:** A per-channel TDS reconciliation statement contrasting operator deductions in Form 26AS against operator settlement files, with the own-website and direct B2B channels evidenced as 194O-clean. A 194Q register for buyer-side deductions matched against B2B invoices. A standing variance log routed into the quarterly tax close, ready for the auditor and the ITR claim against Form 26AS.

### ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer

Source: https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation/

- **Problem:** During ECS-to-NACH migration, legacy ECS uses MICR+account as match key while NACH uses UMRN. With 50,000+ mandates running in parallel, the same borrower can appear as both an ECS and a NACH mandate for the same due date, creating double-debit risk and orphan bank credits with no channel attribution.
- **Logic:** Tag every bank credit to its originating channel (ECS or NACH) from the transaction reference format at ingestion. Maintain parallel mandate registers keyed on MICR+account for ECS and UMRN for NACH. Run a pre-batch deduplication so no borrower has both an ECS and a NACH mandate active for the same EMI cycle.
- **Config:** Dual mandate registers, channel-tagging rule at bank ingestion, deduplication key linking MICR+account to UMRN, and ECS cancellation workflow triggered by successful NACH activation.
- **Output:** Zero double debits, clean single-channel credits per borrower per cycle, a complete migration audit log, and a safe cutover to NACH as the sole active rail.

### EDI 830, 862, and 856 for Indian Auto-Component Suppliers: A Finance Team Primer

Source: https://www.terra-insight.com/insights/edi-830-862-856-india-auto-component-finance-primer/

- **Problem:** Indian auto-component finance teams build receivables and invoicing logic off EDI documents they rarely see directly. Treating 830 forecasts as commitments creates phantom receivables; billing against raw 856 ASN quantity instead of OEM-confirmed received quantity creates over-invoiced positions, broken GSTR-2B reconciliation, and mismatched Section 393(1) Sl. 8(ii) TDS deductions in Form 26AS.
- **Logic:** Map each EDI transaction set to its correct financial event: 830 = planning context only (no revenue, no receivable); 862 = firm authorised dispatch quantity (CUM-required); 856 = dispatch trigger and ASN-to-GRN match base; OEM GRN = control-transfer event under Ind AS 115; periodic GST e-invoice = many ASNs to one IRN, billed against confirmed-received quantity for the window. Land all transports (X12, IDoc, portal JSON, API) into one structured reconciliation stream per part per scheduling-agreement number.
- **Config:** EDI map per OEM covering 830 (forecast horizon, planning lines), 862 (firm-from date, CUM-required, schedule lines), 856 (CUM-shipped, pack/handling-unit structure, SNP), IDoc DELFOR/DELJIT segment mapping for SAP environments, portal-to-X12 logical equivalence map for Maruti e-Nagare, Tata SRM, Bosch SupplyOn, Hyundai HMI Vaatika and Bajaj BAL Connect; part master keyed by OEM plant code, ship-to point and scheduling-agreement number with delivery tolerance and reset markers.
- **Output:** A per-part per-agreement reconciliation pack tying 830 forecast vs 862 firm vs 856 ASN vs GRN vs periodic tax invoice, transport-neutral across X12/IDoc/portal feeds; an audit-grade trace from each financial event back to its originating transaction set; and an exception queue for forecast-vs-firm gaps, dispatch-vs-receipt drift and many-ASN-to-one-invoice consolidation breaks.

### Edible Oil Chapter 15 IDS Refund Blocked — Notification 09/2022 India

Source: https://www.terra-insight.com/insights/edible-oil-chapter-15-idr-refund-blocked-notification-09-2022-india/

- **Problem:** An Indian edible oil refiner operating on the Chapter 15 lines — refined palmolein, refined soyabean oil, refined sunflower oil, refined mustard oil, refined rice bran oil — pays 5 percent output GST on refined oil and accumulates unutilised input tax credit on the higher-rate input GST charged on packaging materials, warehousing and logistics services, refinery consumables, and capital-goods amortisation. Under Section 54(3) of the CGST Act 2017, this accumulation was refundable under the inverted-duty structure limb until 17 July 2022. CBIC Notification 09/2022-Central Tax (Rate) dated 13 July 2022, effective 18 July 2022, invokes clause (ii) of the first proviso to Section 54(3) to bar refund of unutilised ITC on Chapter 15 supplies. Post-18-July-2022 IDS is a permanent working-capital lock-up that runs an illustrative Rs 75 to 100 crore per year for a major national refiner. The reconciliation problem is to bifurcate ITC accumulation into a pre-18-July-2022 refundable pool (with a further sub-bifurcation for the Notification 14/2022 Rule 89(5) formula change effective 5 July 2022) and a post-18-July-2022 permanent-cost pool, and to maintain audit-defensible documentation for both.
- **Logic:** Build an input GST register keyed by tax period of the underlying supply (not the ITC availment date), HSN of the input, applicable GST rate, and Chapter 15 versus non-Chapter-15 output attribution. Split every invoice into three temporal buckets — pre-18-July-2022 with refund application filed before 5 July 2022 (pre-Notification 14/2022 Rule 89(5) formula, Net ITC includes input services and capital goods); pre-18-July-2022 with refund application filed on or after 5 July 2022 (amended formula, Net ITC excludes input services and capital goods); post-18-July-2022 (no refund admissible for Chapter 15). Run a monthly IDS accumulation tracker that decomposes the closing unutilised ITC balance into these three buckets so that the refund-claim pipeline and the permanent-cost accrual are traceable. For a refiner with a mixed output — Chapter 15 refined oil plus non-Chapter-15 specialty chemical or industrial derivatives — split the output register by HSN Chapter to preserve the eligible-refund quantum on the non-Chapter-15 leg. Cross-foot to the GST RFD-01 filings and to the electronic credit ledger every month.
- **Config:** Refinery master with GSTIN, principal place of business (Kandla, JNPT, Kakinada, Krishnapatnam), and HSN masters for Chapter 15 lines (1507 soyabean, 1508 groundnut, 1511 palm, 1512 sunflower and safflower, 1514 rapeseed and mustard, 1515 other fixed vegetable oils including rice bran) and any non-Chapter-15 by-product lines (specialty chemical intermediates, fatty acids, glycerine derivatives); input GST register with tax-period key, HSN, rate, and Chapter 15 versus non-Chapter-15 attribution; refund-application register with filing date, RFD-01 reference, tax period covered, formula version (pre-Notification 14/2022 or amended), and sanction status; permanent-cost ledger with post-18-July-2022 unutilised ITC identified separately; Rule 89(5) formula computation with Turnover of inverted-rated supply, Net ITC (excluding input services and capital goods for the amended formula), Adjusted Total Turnover, and Tax payable on inverted-rated supply captured per RFD-01 filing; audit-defence pack that ties every input invoice to a temporal bucket.
- **Output:** A monthly Chapter 15 IDS reconciliation pack: unutilised ITC opening balance split by temporal bucket, monthly additions split by tax period and Chapter 15 versus non-Chapter-15 attribution, refund claims filed during the period with formula version and RFD-01 reference, refund sanctions received, permanent-cost accrual for the month, and closing balance split by bucket. The pack ties into the working-capital forecast for the finance business partner, the statutory auditor's inverted-duty note, the Section 65 GST audit response pack, and the year-end financial reporting disclosure on the permanent-cost accrual for the Chapter 15 supplies. Integrated with the GST RFD-01 filing pipeline for non-Chapter-15 residual claims and with the electronic credit ledger reconciliation.

### Edible Oil FMCG Reconciliation — Refining, Bottling, Distribution

Source: https://www.terra-insight.com/insights/edible-oil-fmcg-reconciliation-adani-wilmar-patanjali/

- **Problem:** Indian edible oil FMCG brands run a five-stage reconciliation chain — crude import at Kandla/JNPT with BCD at 20% and AIDC at 5% and GST 5% at the finished-goods stage; refining recovery from crude to refined; Schedule I deemed-supply stock transfer from refinery GSTIN to bottling GSTIN with a valuation-and-ITC leg; contract bottling job-work under Section 393(1) Sl. 4 TDS; and distributor secondary sales into general trade under Section 15(2) scheme treatment. Adjacent to all five is the periodic government MRP intervention — a directive that caps or freezes MRP on notified pack sizes during a defined window and creates a per-batch trade-margin absorption problem across FG in the pipeline. Any one of the five stages, or the MRP overlay, mis-recorded leaves the year-end books off by a material margin.
- **Logic:** Build a landed-cost register per bill of entry with CIF, BCD, AIDC, port and transport, and refinery receipt weight; reconcile refinery yield to refined output against the bulk-oil master. Book the Schedule I stock-transfer invoice per SKU per receiving GSTIN at fair market value with 5% GST; cross-foot to the bottling plant's GSTR-2B. Log every contract-bottling job-work invoice with the job-work fee split from the customer-supplied bulk oil and deduct TDS at 1% or 2% per Section 393(1) Sl. 4; reconcile to Form 26AS and to the ITC-04 return for the physical bulk-oil movement. Book distributor secondary-sales schemes upfront with a Section 15(2) treatment flag per scheme; classify each credit-note leg as invoice-recorded, post-supply qualifying, or post-supply non-qualifying. Maintain a per-batch MRP register — batch code, pack size, printed MRP, current MRP, location — and pull it at the moment any MRP directive lands to compute the trade-margin absorption per SKU per pack per location.
- **Config:** Landed-cost register keyed by bill of entry, HSN, tariff notification, and CIF; refinery bulk-oil master by tank and batch; Schedule I stock-transfer scheme with per-GSTIN receiver, fair-market-value basis, and HSN 1512/1514/1508/1511 for refined variants; contract-bottling master with bottler PAN, Section 393(1) Sl. 4 TDS rate (1% Ind/HUF or 2% other), job-work fee schedule, and ITC-04 linkage; distributor master with GSTIN, PAN, Section 15(2) treatment flag on scheme master; per-batch MRP register with pack size, printed MRP, and location; MRP-directive log with directive date, notified pack sizes, revised MRP, and applicability window.
- **Output:** A monthly edible-oil reconciliation pack: landed-cost per tonne per consignment with duty breakdown, refinery yield reconciliation, refined-oil bulk balance, Schedule I stock-transfer invoice log with GSTR-1-to-2B match, contract-bottling job-work register with TDS deducted and ITC-04 movement, distributor secondary-sales scheme register with Section 15(2) treatment flag per scheme, MRP-directive absorption calculation per SKU per location, and a customs-audit-ready duty ledger. Ties into the trade-spend liability accrual and the GST credit-note cycle downstream.

### EID Parry Integrated Sugar Reconciliation — Cargill JV Refined Sugar

Source: https://www.terra-insight.com/insights/eid-parry-integrated-sugar-recon-cargill-jv/

- **Problem:** An integrated Tamil Nadu sugar producer operating two mill complexes at 42,000 TCD aggregate crushing capacity, with a downstream refined sugar operation supplying FMCG-grade ICUMSA 45 sugar to consumer product companies and bulk food service aggregators, must reconcile the mill production log against the refining plant transfer register against the FMCG channel dispatch note against the tax invoice with GST 5 percent under HSN 1701 and any packaging component at 18 percent, against the MSAF cess accrual on molasses production, against the Sugarcane (Control) Order 1966 Clause 3(3A) 14-day cane payment aging bucket with 15 percent per annum interest exposure, and against the Section 8 Sl. 8 code 1031 TDS deducted by FMCG buyers under the Rs 50 lakh purchase-goods threshold. Manual reconciliation across a two-stage integrated chain with five reconciliation surfaces loses per-batch grade attribution, mis-attributes packaging ITC to the wrong tax period, and misses the 14-day cane payment window on a small percentage of the farmer base every crushing season.
- **Logic:** Ingest the mill production log with daily cane crushed in TCD, pol recovery percentage, sugar produced by grade, and by-product yield (bagasse, press mud, molasses). Ingest the refining plant transfer register with batch number, grade code (ICUMSA 45 or lower for FMCG, higher grades for industrial), produced quantity, and dispatch destination. Match the FMCG channel dispatch note to the buyer purchase order by SKU pack size, quantity, and delivery date. Feed the tax invoice with GST 5 percent under HSN 1701 (the sugar line) plus 18 percent under HSN 3923 or 4819 or 6305 (the packaging line) into the Rule 89(5) inverted-duty workbook. Compute the daily MSAF cess accrual on the molasses production log and reconcile against the state molasses control board remittance challan and the state-mandated molasses storage register opening plus production minus dispatch equals closing tally. Group the cane payment register by delivery date and farmer code, compute the days-outstanding bucket, and accrue 15 percent per annum interest on any bucket beyond the 14-day Clause 3(3A) window. Ingest the buyer TDS confirmation for code 1031 and match against Form 26AS at the seller PAN.
- **Config:** Farmer master with farmer code, PAN (where filed), village and taluk, bank account for direct settlement, and cane variety plus season contract; mill master with mill code, TCD capacity, state cess registration, and molasses storage register reference; refinery master with refinery code, ICUMSA grade output mix, and packaging line assignment; FMCG buyer master with buyer PAN, GSTIN, code 1031 threshold flag, and aggregate purchase running total for the financial year; state master with state-notified SAP per season (where SAP applies), MSAF cess rate per tonne of molasses, and molasses control order registration reference; two-tier price schedule (central FRP notified by CACP plus any state SAP notified per season) versioned by delivery date; GSTR-1 and GSTR-3B feed for the Rule 89(5) refund workbook with the packaging-line invoice register carved out from the sugar-line invoice register; Section 43B(h) MSME flag on packaging suppliers (HDPE sack, laminate pouch, and corrugated carton converters are frequently MSME-registered).
- **Output:** A month-end integrated sugar reconciliation pack: mill production log summary by mill by day with cane crushed in TCD and pol recovery, refining plant transfer register summary by grade by batch, FMCG channel dispatch register by buyer by SKU by delivery date, tax invoice register split into the sugar line (5 percent HSN 1701) and the packaging line (18 percent) with the Rule 89(5) refund draft under the Notification 14/2022 amended formula, MSAF cess accrual and remittance reconciliation with the state molasses storage register variance, cane payment aging by delivery date by farmer code with 15 percent per annum interest accrual on any bucket beyond the 14-day Clause 3(3A) window, and Section 8 Sl. 8 code 1031 TDS reconciliation between the FMCG buyer confirmation and the seller's Form 26AS credit.

### Electricity Duty and State Cesses Reconciliation for Indian C&I Consumers

Source: https://www.terra-insight.com/insights/electricity-duty-cesses-state-wise-india/

- **Problem:** Indian C&I consumers running multi-state operations face a structural electricity duty reconciliation gap — each state legislates its own duty under Entry 53 List II with no uniform rate or exemption framework, DISCOM bills layer energy charge plus fixed charge plus wheeling plus duty plus green cess plus infrastructure cess plus GST on services, captive and SEZ exemption certificates must stay live with annualised compliance, and mid-cycle tariff revisions create split-rate billing slabs that distort the monthly consumption walk if not unbundled.
- **Logic:** Maintain a state-wise duty rate table keyed by consumer category (HT industrial, LT commercial, captive, open-access drawal) and effective date, decompose each DISCOM bill into its component lines (energy, fixed, wheeling, duty, green cess, infrastructure cess, GST on services) and re-derive each line from metered units and the gazette rate, tie captive and SEZ exemptions to a live certificate register with annualised compliance status, split mid-cycle tariff-change cycles into pre-effective and post-effective slabs from the daily kWh series, and reconcile open-access drawal between exchange settlement and consumer-end metering with the duty applied by the consuming state on matched units.
- **Config:** Plant master keyed by service connection number with state, DISCOM, consumer category and tariff class, state duty rate table by category and effective date, exemption certificate register (captive ownership and consumption ratios, SEZ unit notification, deemed-export evidence) with annualised compliance dates, DISCOM bill ingest schema with line-wise decomposition (energy charge, fixed/demand, wheeling, duty, green cess, infrastructure cess, GST on services), daily kWh series from smart meters or feeder telemetry for mid-cycle split, open-access settlement bridge (exchange MIS, transmission losses, DSM) with consumer-state duty overlay, and arrears bill cross-reference table tying retrospective revisions to the original consumption period.
- **Output:** A state-by-state monthly duty walk per plant showing energy units, applicable rate, duty computed, cess computed, exemption units, and net duty payable tied to the DISCOM bill, an exemption compliance dashboard showing certificate validity and the annualised captive 26/51 test or SEZ unit status, a mid-cycle tariff-change reconciliation breaking the cycle's consumption into pre- and post-effective slabs with the derived duty per slab, an arrears bill register linking each retrospective revision back to the original month and feeding restated month-on-month analytics, and a GST-on-services line feeding the GSTR-2B ITC reconciliation for wheeling, transmission and open-access surcharge components where input credit is admissible.

### Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty

Source: https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india/

- **Problem:** EMS companies in India run three incentive-scheme rails (PLI Large-Scale Electronics, SPECS, residual MSIPS), a customs-heavy import stream, contract-manufacturing free-issue material flows, IGST inverted-duty refund claims, and Section 393 TDS on purchases and foreign royalty — each with its own claim file, statutory window, and ledger trail, producing reconciliation drift that compounds across quarters.
- **Logic:** Tag every transaction to its incentive scheme at booking time, reconcile customs bills of entry against import invoices and GSTR-2B IGST entries, separate free-issue material receipts from purchased inventory in a parallel no-value ledger, run inverted-duty ITC accumulation against output GST monthly to drive the Section 54(3) refund file, and track Section 393(1) Sl. 8(ii) ₹50 lakh per-PAN purchase counters with Section 393(2) Sl. 17 foreign-payment codes per royalty stream.
- **Config:** EMS configuration with scheme tags (PLI-LSE, SPECS, MSIPS-legacy), BOM-to-HSN map for incentive eligibility, customs bill-of-entry capture per import shipment, free-issue material ledger separate from inventory master, GSTR-2B IGST reconciler, inverted-duty accumulation tracker, Section 393(1) Sl. 8(ii) per-PAN year-to-date purchase counter, Section 393(2) Sl. 17 royalty stream per foreign licensor.
- **Output:** A monthly EMS close where PLI/SPECS claim files reconcile to invoice and capex ledgers, customs bills of entry tie to IGST in GSTR-2B, free-issue material receipts close against BOM consumption or return challan, accumulated inverted-duty ITC drives a quarterly Section 54(3) refund claim, Section 393(1) Sl. 8(ii) deductions trigger automatically when per-vendor purchases cross ₹50 lakh, and Section 393(2) Sl. 17 challans tie to each royalty stream.

### Emerging Markets Africa + LatAm: Generic Export Reconciliation

Source: https://www.terra-insight.com/insights/emerging-markets-africa-latam-generic-pharma-export-reconciliation/

- **Problem:** An Indian Tier-1 generics exporter running a Sub-Saharan Africa distributor-model channel at an illustrative annual volume of the order of Rs 850 crore across 22 African countries and a Latin America regulator-registered channel at Rs 620 crore across Brazil, Mexico, Colombia and Chile must reconcile a bifurcated payment book. The WHO Prequalification and institutional-tender leg (Global Fund, PEPFAR, UNICEF, UNAIDS) is structured at 100 percent Letter of Credit or Standby Letter of Credit advance backing; the private-market distributor leg is structured at approximately 60 percent open-account and 40 percent LC, with the open-account share increasing as the distributor relationship matures. The reconciliation must hold country-specific marketing-authorisation registrations current (NAFDAC Nigeria, SAHPRA South Africa, NDA Uganda, FDA Ghana, TFDA Tanzania, ANVISA Brazil, COFEPRIS Mexico, INVIMA Colombia, ISP Chile), reconcile per-currency Ind AS 21 forex translation across USD, EUR, ZAR and BRL, run DGFT drawback and RoDTEP claims on the shipping-bill trail, file Section 54(3) LUT zero-rated refund monthly against the parallel domestic ITC block, and post an Ind AS 109 expected credit loss provision that runs materially higher on the open-account private-market book than on the LC-backed institutional book.
- **Logic:** Build a per-country per-channel shipment register keyed on shipping-bill number, invoice date, invoice currency, payment mechanism (LC or Standby LC or open-account), and destination regulator registration reference. Extract the LC-backed institutional-tender shipments into a clean shipment-to-LC-to-e-BRC chain that runs against the twelve-month Rule 96A realisation window. Extract the open-account private-market shipments into a shipment-to-invoice-to-receivable chain with a per-distributor aging bucket. Translate each foreign-currency invoice at the invoice-date spot rate under Ind AS 21 paragraph 21; translate each open receivable at the monthly closing rate under Ind AS 21 paragraph 23(a); post the exchange difference to the P&L under Ind AS 21 paragraph 28 monthly. Compute the Ind AS 109 expected credit loss provision per distributor per country using the simplified approach with country-tier and relationship-maturity adjustments. File Form GST RFD-11 LUT annually and Form GST RFD-01 with Statement 3 monthly for the Section 54(3) zero-rated refund. File the DGFT drawback and RoDTEP claims per shipping bill. Hold the country registration renewal calendar as a standing per-product per-country register with a renewal-due-date monitor.
- **Config:** Country master (22 African countries, 8-12 LatAm countries) with the destination regulator, registration reference number per product, renewal-due date, and local representative name; product master with the WHO Prequalification status flag and the tender-eligibility flag per institutional-buyer programme; shipment register keyed on shipping-bill number, invoice date, invoice currency, channel (institutional versus private-market), payment mechanism (LC, Standby LC, or open-account), and destination country; LC register with confirming bank, LC number, expiry, negotiation date, and realisation date; open-account receivable register with distributor, country, invoice date, invoice currency, credit terms, and aging bucket; per-currency Ind AS 21 forex translation register with the daily treasury rate source, invoice-date spot, monthly closing rate, and realisation-date rate; Ind AS 109 expected credit loss provision register per distributor per country; DGFT drawback and RoDTEP claim register per shipping bill; e-BRC realisation register per shipping bill; Form GST RFD-11 LUT annual filing tracker; Form GST RFD-01 Statement 3 zero-rated refund monthly filing register; country registration renewal calendar with due-date monitor.
- **Output:** A month-end emerging-markets export reconciliation pack: per-country per-channel shipment register with shipping-bill, LC or open-account payment mechanism, and destination registration reference; LC-backed institutional-tender realisation position mapped against the twelve-month Rule 96A window with e-BRC status; open-account private-market receivable aging with per-distributor per-country balances and Ind AS 109 expected credit loss provision; per-currency Ind AS 21 forex translation ledger with invoice-date, closing, and realisation rates and the P&L exchange-difference impact for the tax period; DGFT drawback and RoDTEP claim register with per-shipping-bill status; Section 54(3) LUT zero-rated Form GST RFD-01 with Statement 3 draft ready for portal submission; country registration renewal calendar with the next-90-day renewal-due queue and the treasury schedule for outbound registration-renewal remittance. At year-end the pack reconciles the aggregate export book by country and channel against the audited financial-statement export-revenue disclosure and closes the aggregate Ind AS 109 provision movement to the loss-allowance ledger.

### EMI MDR: Debit-EMI vs Credit-EMI vs Cardless EMI vs Pay Later Breakdown

Source: https://www.terra-insight.com/insights/emi-mdr-debit-credit-cardless-paylater-india/

- **Problem:** EMI is not one rate but four distinct rails — debit-card EMI, credit-card EMI, cardless EMI, and Pay Later — with materially different economics that one gateway prices per rail and two gateways collapse into a single 3 percent slab. A D2C consumer-electronics merchant running 22 percent of GMV through EMI is exposed to whichever pricing model the gateway publishes, and a flat 3 percent EMI slab on Razorpay or PayU silently absorbs the per-rail differential that a per-rail rate card like Cashfree's would expose and let the merchant optimise against.
- **Logic:** Decompose every EMI transaction in the gateway settlement export into rail (debit-EMI, credit-EMI, cardless, Pay Later), lending-partner identifier, tenure, gross order value, and net-of-MDR settlement amount. Compute the actual per-rail effective rate as fee divided by gross per rail per month. Compare against the published rate card for the gateway in contract. On Cashfree this means four distinct expected rates and four variance lines. On Razorpay or PayU this means one expected 3 percent against four observed effective rates, with the audit move being to model what the same volume would cost on a per-rail rate card and surface the difference as a renegotiation or migration exposure number.
- **Config:** Per-rail EMI parser keyed on instrument flag and lending-partner identifier in the settlement file. Published rate card per gateway covering debit-card EMI, credit-card EMI base plus uplift, cardless EMI, and Pay Later. Per-rail expected-fee calculator with GST on MDR as a separate line. Method-mix-weighted effective rate tracker for the EMI sub-portfolio. Cross-gateway comparison engine that models the same rail mix on an alternative gateway's rate card. Per-rail conversion-rate join from the checkout funnel to weight any rail-bias decision by combined conversion and MDR economics.
- **Output:** A monthly EMI scorecard with per-rail GMV, per-rail effective rate, per-rail expected rate, and per-rail variance in rupees. A cross-gateway exposure number showing what the same rail mix would cost on the next-best alternative. A rail-bias recommendation gated by checkout conversion. A reconciled GST-on-MDR claim line for the EMI sub-portfolio ready for GSTR-2B. An annual EMI cost gap the controller can take to the renegotiation or gateway-migration decision.

### EMI Scheme Revenue Recognition for Jewellery: Ind AS 115 Point-in-Time vs Over-Time

Source: https://www.terra-insight.com/insights/emi-scheme-jewellery-instalment-plan-revenue-recognition-india/

- **Problem:** Indian jewellery retailers routinely offer 12 to 24-month EMI schemes on high-value pieces (wedding sets, diamond-studded jewellery, gold-coin bundles), but the accounting and tax treatment of the EMI structure is often handled informally. Revenue is sometimes recorded at the EMI-inclusive amount at booking, sometimes spread across the EMI period, and sometimes reconciled only at year-end. Ind AS 115 requires revenue to be recognised at the cash-equivalent price at the point control transfers, with the financing-component delta separated and unwound as finance income over the EMI tenure. GST is due in full at the booking date on the full invoice value per Section 12 of the CGST Act — no deferral is permitted even though the cash comes in over 24 months, creating a working-capital drag on the retailer's electronic cash ledger. The reconciliation between the customer instalment ledger, the GSTR-1 filing at booking, the trial-balance revenue line at the cash-equivalent price, and the deferred finance income unwinding schedule is the single largest close-cycle exposure in EMI-active jewellery retail.
- **Logic:** Separate the goods-revenue leg from the financing leg at contract inception. Determine the cash-equivalent price of the piece as the price at which it would sell to a full-cash customer on the same day. Book customer receivable at the EMI-inclusive amount, revenue at the cash-equivalent price, and deferred finance income liability at the delta. Compute the effective interest rate that discounts the future EMI cash flows to the cash-equivalent price — this becomes the unwinding rate. At each month-end, unwind the deferred liability into finance income at the effective rate applied to the outstanding receivable, and post the monthly EMI collection against the receivable when received. File GST at booking on the full invoice value per Section 12 and issue a compliant tax invoice showing the tax-rate split (3% gold, 5% making, 0.25% diamond, 18% packaging). If the interest component is disclosed separately on the invoice, classify it as either a taxable financing service at 18% or exempt under Notification 12/2017-CTR based on genuine time-value-of-money character. Reconcile GSTR-1 revenue (EMI-inclusive) to trial-balance revenue (cash-equivalent) via the deferred finance income liability reconciliation each month.
- **Config:** Customer master with PAN, KYC status, EMI-scheme flag, and lender-linked or self-funded indicator; scheme master with tenure (6/12/18/24 months), effective interest rate for Ind AS 115 discounting, and interest-disclosure flag on invoice; item master with cash-equivalent price and MRP separated from EMI-inclusive amount; receivable subledger tagged by customer, scheme, and booking-month with ageing buckets; deferred finance income liability subledger with unwinding schedule per contract at contract inception; GST posting rule that recognises full output tax at booking date on the full invoice value regardless of EMI structure; commission-to-scheme-promoter subledger with Section 393(1) Sl. 18 (code 1015) TDS flag at 5%; bad-debt provisioning per Ind AS 109 with default trigger and expected-credit-loss factor by scheme cohort.
- **Output:** A monthly reconciliation pack: customer instalment ledger by scheme and cohort with ageing; deferred finance income liability roll-forward showing opening balance, additions from new bookings, unwinding to P&L, and reversals from defaults; trial-balance revenue reconciliation between GSTR-1 EMI-inclusive value, cash-equivalent revenue recognised at delivery, and the deferred liability delta; GST filing pack showing full output tax remitted at booking with working-capital drag on outstanding EMI receivables; bad-debt provisioning working under Ind AS 109 by scheme cohort; commission payout to scheme-promoter partners with Section 393(1) Sl. 18 TDS at 5% reconciled against Form 26AS; per-contract audit trail linking the customer invoice, the EMI schedule, the effective interest rate, and the monthly unwinding entries.

### eNACH Mandate-Rejection Fee Tracking for Indian Subscription Merchants

Source: https://www.terra-insight.com/insights/enach-mandate-rejection-fee-tracking-india/

- **Problem:** Indian subscription merchants and NBFC EMI books quietly absorb the cost of eNACH mandate rejections at approximately fifteen rupees plus eighteen percent GST per failed debit, compounded across two-cycle retry policies, and on a 38,000-mandate book at a 12 percent rejection rate the annual cost reaches roughly forty-one and a half lakh once delay-cost on the receivable is added. The headline rejection fee appears as a single consolidated line on the aggregator's monthly invoice with no per-batch, per-sponsor-bank, or per-return-code breakdown, so finance controllers cannot tune retry policy, identify rejection-trap sponsor banks, or hold the aggregator to the contracted fee schedule. The leakage is invisible because the four-layer cost stack — mandate-creation, first-attempt rejection, retry-rejection, successful-debit — is never assembled in one place.
- **Logic:** Build a per-mandate registry keyed by mandate identifier with sponsor bank, destination bank, mandate creation date, status, and current attempt count. For every settlement batch, pull the eNACH return file and attribute every failed debit to its mandate and attempt number. Look up the NPCI return reason code and total the rejection fee plus GST per code, per sponsor bank, and per batch. Compute the first-attempt rejection rate and retry-cycle rejection rate by sponsor bank and rank against the cluster mean to surface rejection-trap candidates. Compute the days-past-due carry-cost on the receivable per failed first-attempt debit using marginal cost of funds and average ticket size. Reconcile the per-batch fee totals across the month against the aggregator's monthly fee invoice within a small rounding tolerance.
- **Config:** Per-mandate registry with sponsor and destination bank metadata. Aggregator settlement and return file ingestion pipeline. NPCI return reason code dictionary covering insufficient balance, account closed, signature mismatch, mandate inactive, technical reject. Per-debit rejection fee schedule by aggregator with GST eighteen percent overlay. Retry policy engine with code-aware first-cycle and T+3 retry rules. Marginal cost of funds parameter and average EMI ticket parameter for delay-cost computation. Monthly aggregator tax invoice reconciliation rules. Variance register feeding the four-layer eNACH cost dashboard.
- **Output:** A four-layer eNACH cost dashboard showing mandate-creation, first-attempt rejection, retry-rejection, and successful-debit costs with GST overlays, totalled per sponsor bank and per return reason code. A rejection-trap report ranking sponsor banks against the cluster mean with thirty-day rolling first-attempt rejection rates. A code-aware retry policy recommendation engine surfacing return codes where retry economics are negative. A monthly delay-cost computation showing carry-cost on the receivable book attributable to rejected first-attempt debits. A monthly fee reconciliation between per-batch totals and the aggregator tax invoice for ITC alignment under Rule 36(4).

### Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts

Source: https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india/

- **Problem:** Engineering and capital goods EPC companies in India bill across multiple milestones tied to order phases (advance, design freeze, procurement, dispatch, commissioning, retention), hold retention money 12-18 months against warranty, post Performance Bank Guarantees separate from retention, trigger GST liability under Section 13 time-of-supply on advance receipts, navigate works-contract vs supply classification with Section 17(5) blocked-ITC implications for own-property works, and apply Section 393 contractor and professional TDS — each requiring its own reconciliation rail with statutory anchor and customer payment trail.
- **Logic:** Track every milestone against contract evidence, invoice, GST liability, customer payment and warranty clock; maintain a retention ledger per contract with warranty start / end and any deduction credit-note treatment under Section 34; track every active PBG by bank instrument number, beneficiary, expiry and renewal; treat advance receipts under Section 13 time-of-supply with receipt voucher and adjustment at milestone invoice; classify works-contract vs supply at PO stage with Section 17(5) implication for own-property; map Section 393(1) Sl. 6(i) and Sl. 6(iii) TDS codes by contract type.
- **Config:** Engineering / EPC configuration with milestone phase map per contract, retention ledger with warranty start / end and Section 34 credit-note hook, PBG register with bank / expiry / renewal tracker, Section 13 time-of-supply trigger on advance receipt vouchers, works-contract classification flag with Section 17(5) own-property blocked-ITC marker, Section 393(1) Sl. 6(i)/(iii) TDS code map per vendor type, vendor master with separate codes for civil contractor, fabrication contractor, design consultant, installation subcontractor.
- **Output:** A monthly engineering close where every milestone invoice ties to its phase evidence and customer payment; retention is aged to warranty-release date with any deduction credit-noted; PBGs are tracked by expiry with renewal alerts; advance receipts have matching receipt vouchers with GST adjusted at milestone invoice; works-contract for own-property is correctly held in Section 17(5) blocked ITC; Section 393(1) Sl. 6(i) and Sl. 6(iii) deductions tie to monthly challans by payment code.

### Enterprise MPLS Circuit Billing Reconciliation: SLA Credit and Recovery

Source: https://www.terra-insight.com/insights/enterprise-mpls-circuit-billing-reconciliation-india/

- **Problem:** Indian enterprises run MPLS WAN across multiple telecom vendors (BSNL, Airtel, Tata Communications, Reliance Jio) with hundreds of circuits, hub-vs-spoke pricing, uptime SLAs and tiered penalty credits, and contractual one-time install charges. The reconciliation must tie circuit inventory against vendor invoices, compute SLA penalty credits from downtime evidence, validate hub-vs-spoke rate application, apply 18 percent GST and Section 393(1) Sl. 6(i) contractor code 1024 (2% for company deductees) TDS, and recover SLA credits through Section 34 CGST credit notes within the 30 September following-FY deadline.
- **Logic:** Maintain a circuit master with site, vendor, bandwidth, contract rate, hub-vs-spoke tier, install date and SLA threshold; ingest vendor invoices and validate each circuit-line against the master; ingest downtime evidence from NOC ticket logs and monitoring data; compute SLA penalty credits against the contractual tier table; flag misbilled circuits (decommissioned but still billed, wrong bandwidth, wrong tier); apply Section 393(1) Sl. 6(i).D(b) code 1024 TDS at 2 percent on the service value net of GST; track Section 34 CGST credit notes for SLA credits within the 30 September window and reverse Rule 42 ITC.
- **Config:** Multi-vendor circuit master with contract terms; SLA tier table per contract with downtime thresholds and credit percentages; NOC downtime ingestion; install-charge amortisation schedule per Ind AS 116 where applicable; GST 18 percent service classification; Section 393(1) Sl. 6(i).D(b) code 1024 withholding rule; Section 34 CGST credit note tracker with 30 September deadline; Rule 42 ITC reversal logic.
- **Output:** A reconciled MPLS billing dashboard showing circuit-by-circuit invoice tie against the master, SLA-credit-eligible downtime per circuit, applied vs contractual rate validation per hub/spoke tier, decommissioned-but-billed flags, Section 393(1) Sl. 6(i).D(b) code 1024 TDS withheld, and Section 34 CGST credit notes claimed with Rule 42 ITC reversal — feeding the WAN cost-of-operations close and the GST 3B.

### EPCG Capital Goods Reconciliation for Textile Manufacturers

Source: https://www.terra-insight.com/insights/epcg-export-promotion-capital-goods-textile-reconciliation/

- **Problem:** A textile manufacturer importing dyeing ranges, spinning frames, or knitting machinery under an EPCG authorisation carries a zero-duty exemption today in exchange for a six-times-duty-saved export obligation stretched over six years from the date of authorisation issue. Block 1 covers years 1 to 4 and requires 50 percent EO fulfilment; Block 2 covers years 5 and 6 and requires the balance 50 percent. Missing a block target, submitting the installation certificate late, mis-flagging a resultant product, or under-realising foreign exchange against a shipping bill exposes the authorisation holder to duty recovery with interest and can escalate to a Section 11(2) FTDR Act notice. Manual tracking across the DGFT license register, ICEGATE shipping bill data, installation certificate submissions, and the banker's e-BRC feed loses shipments to reconciliation error, over-states running EO fulfilment, and leaves the authorisation holder exposed at the end of Block 1 or Block 2.
- **Logic:** Build an EPCG authorisation register keyed by authorisation number, date of issue, importer name, CIF value, duty saved amount, resultant product HSN, EO amount (6× duty saved), Block 1 target (50 percent of EO), Block 2 target (balance 50 percent), and Block 1 end-date (48 months from issue). Ingest every shipping bill filed against the authorisation from ICEGATE — SB number, port, date, FOB value, resultant product HSN, and quantity. Match against the DGFT license register to confirm the shipping bill has flowed through to accumulated EO fulfilment. Close the loop via e-BRC — mark each shipping bill FOB as realised only when the banker's e-BRC confirms convertible foreign exchange receipt. Compute running EO fulfilment: cumulative realised FOB against Block 1 target, then against total EO. Track the installation certificate submission against the six-month deadline from import completion. Alert at 300, 330, and 360 days before Block 1 end-date if fulfilment is below 40 percent; escalate at Block 2 mid-point.
- **Config:** EPCG authorisation master with authorisation number, RA office, date of issue, CIF value, duty saved (BCD + IGST components), total EO, block-wise targets, resultant product HSNs, and validity end-date. Shipping bill feed from ICEGATE with EPCG authorisation reference tagging. DGFT EPCG portal license register feed for accumulated EO fulfilment cross-check. e-BRC feed from the export banker for realised FOB reconciliation. Installation certificate submission tracker with six-month deadline from Bill of Entry date. RoDTEP appendix flag per shipment (Appendix 4R for standalone EPCG-only DTA exporter; Appendix 4RE if the same shipment also runs under Advance Authorisation). RoSCTL scheme flag for Chapters 61, 62, 63 apparel and made-ups exports. Block-wise alert thresholds at 300, 330, 360 days before Block 1 end-date and mid-point of Block 2.
- **Output:** A block-wise EPCG reconciliation pack showing per-authorisation running EO fulfilment: total EO, Block 1 target and cumulative discharge, Block 2 target and cumulative discharge, days remaining in each block, shortfall exposure, and duty-recovery liability at current run rate if the shortfall persists. Per-shipping-bill line items show SB number, date, FOB value, resultant product HSN, e-BRC realisation status, and authorisation reference — the three-way match that confirms an SB counts towards EO. The installation certificate tracker shows date of import completion, six-month deadline, and submission status per authorisation. RoDTEP appendix flag per shipment is cross-checked against authorisation type to prevent 4R/4RE mis-classification. Alerts fire at 300, 330, and 360 days before Block 1 end-date if fulfilment is below 40 percent, giving the export operations team a full quarter to accelerate order intake before the block closes.

### ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification

Source: https://www.terra-insight.com/insights/esi-contribution-reconciliation-india/

- **Problem:** ESI coverage applies to employees at or below ₹21,000/month gross but runs on six-month contribution periods. A salary revision mid-period keeps the employee covered until the period boundary, creating a moving match target between payroll and the ESIC challan and systematic headcount mismatches every April and October.
- **Logic:** Match each month's ESI challan to payroll and bank debit using the IP number as the key at employee level. Apply 4% combined contribution (3.25% employer + 0.75% employee) on gross wages, maintain coverage through the current contribution period even after salary revision, and run a dedicated reconciliation for the April and October transition months.
- **Config:** IP-number keyed matching, wage-ceiling transition rule honouring the six-month period, bi-annual transition reconciliation, and 15th-of-month deadline trigger with Section-level interest rule.
- **Output:** Clean monthly ESI reconciliation, zero late-payment interest, correct IP-level contributions at the period boundary, and a defensible ESIC portal and audit trail.

### ERP Data Extracts for Auto-Component Reconciliation: SAP IDocs, Oracle BIP, Tally CSV, D365 Data Entities

Source: https://www.terra-insight.com/insights/erp-data-extract-reconciliation-auto-component-india/

- **Problem:** Every auto-component reconciliation tool — internal Z-report, custom OTBI report, Logic Apps flow or companion product — depends on the ERP data-extract layer for its source data. Each ERP (SAP S/4HANA, Oracle Fusion, Tally Prime, D365 F&O) exposes a different extract pattern with different format conventions, refresh frequencies, error-handling and date / decimal / GSTIN normalisation challenges. A Tier-1 with a mixed-ERP landscape (e.g., SAP HANA at HQ plus Tally Prime at a satellite plant) needs to design the extract layer carefully — most reconciliation-tool implementations that fail at Tier-1 fail at the extract layer, not at the reconciliation logic.
- **Logic:** For each ERP in the landscape, document the canonical extract patterns (SAP IDocs / RFC / OData / scheduled custom report; Oracle BIP / OTBI / REST / FBDI; Tally ODBC / XML / Tally Server 9; D365 Data Entities / Logic Apps / Synapse Link), specify the source tables or message types per reconciliation stream, define the daily / weekly / quarterly cadence per extract, design the format-normalisation layer for date / decimal / GSTIN consistency across ERPs, and orchestrate the daily extract job framework with retry, dead-letter and reconciliation completeness checks.
- **Config:** Per-ERP extract architecture: SAP IDoc outbound message types ORDERS05 / DELFOR01 / DELINS01 / DESADV01 / INVOIC02 with ALE / EDI subsystem partner profiles, plus scheduled ABAP custom report exports to SFTP for the auto-component-specific reconciliation streams; Oracle Fusion BIP daily extracts for AR / AP / BPA / withholding tax, OTBI subject-area subscriptions for exception registers, REST API for on-demand queries; Tally Prime daily ODBC pull job from voucher / register / TDS / GST tables, output to CSV staging; D365 F&O Logic Apps scheduled flows pulling Data Entities to Azure Blob staging. Format normalisation: SAP date YYYYMMDD vs Oracle DD-MON-YY vs Tally DD-MM-YYYY vs D365 ISO-8601 reconciled to a single canonical format in the staging layer; decimal separator and number format normalised; GSTIN format-validated.
- **Output:** A working ERP data-extract layer feeding the auto-component reconciliation tool: daily extract job orchestration with completeness checks, format-normalised staging area, per-ERP extract artefacts (SAP IDoc port + custom report SFTP drops, Oracle BIP scheduled emails + REST endpoints, Tally daily ODBC CSV, D365 Logic Apps to Azure Blob), reconciliation tool consuming the staging area on a daily cadence with the reconciliation streams running on top.

### ESOP and RSU Accounting for IT Services Companies under Ind AS 102

Source: https://www.terra-insight.com/insights/esop-rsu-accounting-it-services-ind-as-102/

- **Problem:** Indian IT services and SaaS companies issuing ESOPs and RSUs must measure fair value at grant under Ind AS 102, recognise the expense across the vesting period (graded by tranche), deduct perquisite TDS at exercise under Section 17(2)(vi), and reconcile the equity ledger against payroll, bank receipts on allotment, and statutory disclosures.
- **Logic:** Run option-pricing valuation at grant date, recognise tranche-by-tranche expense over vesting, apply modification accounting for IPO-acceleration, compute perquisite TDS as (FMV − exercise price) at exercise, and reconcile the ESOP register against the share capital and securities premium ledgers.
- **Config:** Ind AS 102 grant-date measurement, Black-Scholes for plain vanilla options, tranche-by-tranche graded vesting, Section 17(2)(vi) perquisite TDS, Section 192(1C) start-up deferral, Rule 11UA FMV computation, MCA SH-6 disclosure.
- **Output:** ESOP register tied to grant date and vesting schedule, P&L share-based payment expense per period, perquisite TDS register at exercise, and the equity ledger reconciliation to share capital and securities premium.

### EMA + CEP: Reconciling EU Generic Export Realisation

Source: https://www.terra-insight.com/insights/european-medicines-agency-cep-eu-generic-export-reconciliation/

- **Problem:** A Tier-1 EU-market pharma formulations exporter running EU-CEP-certified formulation plants at Goa and Kurkumbh, at an illustrative annual EU-market formulation export turnover of the order of Rs 3,200 crore split approximately 35 percent United Kingdom, 25 percent Germany, 15 percent France, 15 percent Italy and the balance across the Netherlands and the Nordics, must reconcile per-shipment shipping bill and commercial invoice at FCA-Nhava Sheva valuation, per-shipment e-BRC EUR or GBP realisation against the shipping bill by BL number, per-shipment Advance Authorisation SION consumption against the finished-formulation export quantity, RoDTEP Chapter 30 scrip issuance at the Appendix 4R rate against FOB, Section 54(3) zero-rated export refund via LUT filed monthly on Form GST RFD-01 with Statement 3, Ind AS 21 forex translation at initial recognition spot, monthly closing rate and settlement rate, and the EDQM CEP annual maintenance fee at the order of EUR 1,200 to 1,500 per API with five-yearly renewal against each finished formulation's API composition. The EMA marketing authorisation renewal cycle every five years and the variation dossier fee stream sit alongside as recurring regulatory costs feeding the export-margin bridge.
- **Logic:** Build a per-shipment export reconciliation record keyed on the shipping bill number, the export invoice number and the Bill of Lading number. Extract the shipping bill from ICEGATE with the FCA-Nhava Sheva commercial invoice value, the HSN-wise Chapter 30 line breakdown, and the FOB-INR conversion. Extract the e-BRC from the AD Bank portal with per-shipment realisation amount, realisation date and settlement rate. Extract the Advance Authorisation ledger entry with the SION-computed input consumption. Extract the RoDTEP scrip issuance from ICEGATE at the Appendix 4R Chapter 30 rate on the FOB base. Extract the Section 54(3) refund attribution against the plant's Net ITC pool, computed under Rule 89(4) for zero-rated supplies made without payment of tax under LUT. Extract the Ind AS 21 forex tracker per shipment. Extract the EDQM CEP fee ledger per API by year and the EMA variation dossier fee ledger by product. Roll the aggregate to the monthly export-margin bridge and to the annual EODC filing pack.
- **Config:** Plant master with GSTIN, state, EU-CEP status and API-to-formulation product mapping; shipping bill register with ICEGATE feed and HSN Chapter 30 line breakdown; commercial invoice register with FCA-Nhava Sheva valuation and destination market; e-BRC register with AD Bank feed, per-shipment BL number match key, realisation date and EUR or GBP realisation amount; Advance Authorisation ledger with SION per-product input quantity and per-shipment consumption debit; RoDTEP scrip register with Appendix 4R rate per HSN and per-scrip issuance amount; Section 54(3) LUT refund workbook with Statement 3 invoice-to-shipping-bill map; Ind AS 21 forex tracker per shipment with initial recognition rate, monthly closing rates and settlement rate; EDQM CEP fee ledger per API with annual maintenance and five-yearly renewal schedule; EMA variation dossier fee ledger per product; monthly export-margin bridge from FOB-INR to net-of-embedded-cost realisation; annual EODC filing pack per Advance Authorisation.
- **Output:** A month-end EU-export reconciliation pack: per-shipment shipping bill matched to commercial invoice matched to e-BRC realisation by BL number, per-shipment Advance Authorisation SION consumption debited to the ledger, per-shipment RoDTEP scrip issuance at Appendix 4R rate, per-plant Section 54(3) LUT refund file with Statement 3 annexure, per-shipment Ind AS 21 forex variance rolled to the monthly forex disclosure, and the aggregate EU-market margin bridge from Rs 3,200 crore FOB-INR annual export turnover to net-of-embedded-cost realisation with EDQM CEP annual maintenance fees and EMA variation dossier fees loaded against the relevant product SKUs. At year-end the pack reconciles the aggregate shipping bill FOB-INR to the aggregate e-BRC realisation, discloses the forex variance, closes any Advance Authorisation whose export obligation is fulfilled via the EODC filing, and reconciles the aggregate RoDTEP scrip issuance to the ICEGATE ledger. The Section 54(3) LUT refund annual reconciliation ties to the monthly RFD-01 filing register at each plant GSTIN.

### EV BMS Supplier Reconciliation under FAME-II: Indian Component Manufacturer Guide

Source: https://www.terra-insight.com/insights/ev-bms-supplier-reconciliation-fame-ii-india/

- **Problem:** A BMS supplier to FAME-II compliant EV OEMs operates inside three overlapping regulatory and commercial frameworks: FAME-II Phase II demand-side subsidy with 50 percent local content for 2W and 60 percent for 3W/4W; PLI-Auto Component supply-side incentive; and Ind AS 115 five-step revenue model applied to a three-component BMS product (PCB hardware, firmware licence, cloud telemetry subscription). Holding all three intact requires component-level localisation evidence per batch, three-PO performance-obligation revenue recognition, and dual-scheme claim reconciliation each month and quarter.
- **Logic:** Maintain a BMS-SKU bill-of-materials master with each line tagged domestic or imported, referenced to supplier invoice or Bill of Entry. Run a monthly content-test report for each batch shipped to each FAME-II OEM customer. Split BMS sale value across three performance obligations (PCB, firmware, telemetry) using stand-alone selling prices, with PCB and firmware recognised on control transfer and telemetry recognised over subscription period. Build FAME-II monthly OEM-input file with batch-level content evidence; build PLI-Auto Component quarterly claim file with incremental-sales calculation against base-year. Reconcile both schemes' content evidence to the same underlying bill-of-materials.
- **Config:** BMS-SKU master with three-component sale structure; bill-of-materials with domestic-or-imported tagging per line; supplier master and Bill-of-Entry register; FAME-II OEM customer master with model-code mapping; PLI-Auto Component registration data with base-year and incremental-sales calculator; Ind AS 115 transaction-price allocation policy with stand-alone selling prices; monthly content-test report template; quarterly PLI claim builder.
- **Output:** A per-batch FAME-II content-test report for OEM consumption files; per-batch Ind AS 115 revenue recognition across three performance obligations with deferred-revenue ageing for telemetry; quarterly PLI-Auto Component claim file with incremental-sales calculation; reconciliation of both regulatory schemes' content evidence to the same bill-of-materials; clawback-resistant audit trail for FAME-II subsidy and PLI disbursement.

### EV Battery Cell Supplier Reconciliation under PLI-ACC: Indian Manufacturer Guide

Source: https://www.terra-insight.com/insights/ev-battery-cell-supplier-reconciliation-india-pli-acc/

- **Problem:** PLI-ACC beneficiaries (Reliance New Energy, Ola Electric, Rajesh Exports) must hit a Year-1-to-Year-5 Domestic Value Addition ramp from 25 to 60 percent to claim ₹18,100 Cr in cumulative incentives across 50 GWh of cell production. The DVA computation requires per-cell or per-batch bill-of-materials reconciliation tying domestic supplier invoices, imported-content customs Bills of Entry (net of MOOWR/EPCG refunds) and sale invoices into a single auditable thread. Without a structured reconciliation discipline, the year-end DVA aggregate cannot be defended at PMA audit and prior PLI disbursements face clawback risk.
- **Logic:** Maintain a cell-SKU bill-of-materials master with domestic versus imported tagging at material level. For each imported input, link to customs Bill of Entry with CIF value plus duty plus clearance charges as landed cost, net of MOOWR or EPCG refund where applicable. For each domestic input, link to supplier tax invoice. Per quarter, aggregate sale-value of ACC cells (gross output) minus aggregate landed cost of imported content to derive DVA. Reconcile capacity-utilisation evidence at plant level. Build the quarterly PLI claim file with cross-references to cell sale invoices (IRN), domestic supplier invoices, Bills of Entry and capacity-utilisation log. Roll up to annual milestone for clawback-resistant audit.
- **Config:** Cell-SKU master with kWh rating, chemistry (NMC/NCA/LFP), bill-of-materials per cell with each material tagged domestic or imported; supplier master with domestic supplier GSTIN or import port-of-origin; Bill-of-Entry register with CIF, duty, clearance, MOOWR/EPCG refund status; cell sale ledger with IRN, buyer GSTIN, kWh; quarterly PLI claim builder; PMA disbursement reconciliation; DVA annual roll-up with audit-trail.
- **Output:** A per-quarter DVA reconciliation pack with computation backed by bill-of-materials, supplier invoices and Bills of Entry; quarterly PLI claim file in PMA-prescribed format; annual milestone reconciliation against capacity-utilisation commitment; clawback-resistant audit trail tying every claimed kWh to its underlying domestic and imported content.

### EV Charging Infrastructure Revenue Recognition and GST Treatment in India

Source: https://www.terra-insight.com/insights/ev-charging-infrastructure-revenue-recognition-gst-india/

- **Problem:** An Indian Charge Point Operator running a public EV charging network across multiple states faces a contested GST classification (electricity supply exempt under Schedule III vs charging service taxable at 18 percent SAC 998599 per Circular 177/09/2022), a three-party revenue split between CPO, site host and network aggregator, a CESL tariff guideline requiring transparent energy-plus-service-charge display, Section 393 codes 1006/1009/1035 TDS on payments to site hosts and aggregators, and Ind AS 115 multi-party transaction-price determination. The reconciliation must hold the commercial-structure tagging, the GST split, and the principal-vs-agent determination consistent across every charging event.
- **Logic:** Build a charging-station master tagged by commercial structure (energy reseller / site host arrangement / pure CPO) and by CESL participation flag. Maintain a charging-event ledger with end-user gross charge, energy component (cost-in for the CPO), service-charge component, GST output at 18 percent on the gross service charge, and site-host revenue-share accrual. For each end-user transaction, recognise CPO revenue at gross under Ind AS 115 step 3 principal determination; flow site-host rental or commission through cost lines, not netted from revenue. Deduct Section 393 codes 1006 (commission), 1009 (rent) and 1035 (e-commerce aggregator) TDS at applicable rates on outbound payments. Reconcile aggregator-platform settlement files to CPO ledger weekly.
- **Config:** Charging-station master keyed by station code with commercial structure (CPO / site host arrangement / energy reseller), CESL participation flag, applicable state tariff, and connected-to-aggregator flag; charging-event ledger with end-user receipt, energy component, service-charge component, GST output, and site-host accrual; site-host master with rental-or-commission flag and Section 393 code (1006 or 1009); aggregator master with Section 393 code 1035 and Section 52 CGST TCS flag; Ind AS 115 principal-vs-agent determination by commercial structure; Form 26AS quarterly chase by aggregator TAN.
- **Output:** A per-station daily reconciliation with end-user gross receipts split into energy + service-charge components, 18 percent GST output on the composite service supply (or zero if energy reseller structure), Ind AS 115 principal-position revenue at gross, site-host rental or commission accrual, aggregator-platform settlement against booking file with platform-fee variance flagging, Section 393 codes 1006/1009/1035 TDS deducted at outbound payment with quarterly TDS challan reconciliation, and a Form 26AS receipt-side reconciliation for aggregator-collected funds.

### EV Motor Controller Supplier Reconciliation under PLI-Auto Champion Scheme

Source: https://www.terra-insight.com/insights/ev-motor-controller-pli-auto-supplier-india/

- **Problem:** An Indian EV motor controller Tier-1 supplier to OEMs like Ather Energy operates inside two regulatory frameworks (PLI-Auto Component for the supplier, PLI-Auto Champion for the OEM) and three commercial structures (hardware sale, firmware licence, calibration/OTA subscription) on the same SKU. Holding 50 percent component-level DVA evidence per batch, three-PO Ind AS 115 transaction-price allocation, base-year incremental-sales calculation against PMA-IFCI methodology, and Section 393 code 1031 TDS reconciliation against Form 26AS each quarter requires a single auditable thread tying each motor-controller unit sold to its underlying bill-of-materials and domestic-vs-imported content.
- **Logic:** Maintain a motor-controller SKU bill-of-materials master with each line tagged domestic or imported referenced to supplier GSTIN invoice or Bill of Entry. Compute per-batch DVA as (sale value minus imported-content landed cost) divided by sale value; aggregate quarterly for PLI-Auto Component claim. Split each unit sale across three Ind AS 115 performance obligations (hardware, firmware, calibration/OTA) at stand-alone selling prices; recognise hardware and firmware on control transfer and calibration/OTA over service period. Build base-year incremental-sales calculation against PMA-IFCI methodology with quarterly claim file. Reconcile Section 393 code 1031 (legacy 194Q) TDS at 0.1 percent deducted by OEM buyer against Form 26AS by deductor TAN by quarter.
- **Config:** Motor-controller SKU master with three-component sale structure and stand-alone selling prices; bill-of-materials master with each line domestic-or-imported flagged and supplier/BoE reference; supplier master with domestic GSTIN; Bill-of-Entry register with CIF, duty, clearance and MOOWR/EPCG refund status; PLI-Auto Component registration with base-year sales and incremental-sales calculator; FAME-II content-test report template feeding OEM DVA submission; Section 393 code 1031 TDS receivable ledger; Form 26AS quarterly reconciliation by OEM TAN.
- **Output:** A per-batch DVA reconciliation pack with domestic-vs-imported bill-of-materials evidence; Ind AS 115 three-PO revenue recognition with deferred-revenue ageing for calibration/OTA subscription; quarterly PLI-Auto Component claim file in PMA-IFCI prescribed format with incremental-sales calculation against base-year; OEM content-test report feeding vehicle-level DVA submission; Section 393 code 1031 TDS reconciliation against Form 26AS with chase-list for missing credits; clawback-resistant audit trail per unit sold.

### Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When

Source: https://www.terra-insight.com/insights/excel-python-reconciliation-software-india/

- **Problem:** Finance Managers choosing between Excel, in-house Python, and purpose-built reconciliation software often optimise for short-term cost and miss the audit-trail and compliance-coverage gaps — Excel has no tamper-evident log, Python scripts break each quarter when TDS sections or GSTR-2B rules change, and both create material exposure above 2,000 transactions per month.
- **Logic:** Apply a three-axis test — monthly transaction volume, compliance complexity (TDS, GSTR-2B, NACH, multi-entity), and audit trail requirement. Excel is defensible below 500 transactions with no statutory matching. Python is viable only for stable structured data with in-house engineering ownership. Above 2,000 transactions or any India statutory matching requirement, move to a config-only platform with ingestion adapters for TRACES, GST portal, NPCI, and bank MT940 feeds.
- **Config:** Decision worksheet with thresholds (500 / 2,000 monthly transactions), compliance complexity checklist (TDS section coverage, GSTR-2B Rule 36(4), NACH NPCI codes, MSME 43B(h) tracker), audit-trail test (tamper-evident log, user attribution, timestamp immutability), and a 3-year cost-of-ownership model.
- **Output:** A documented tool-selection decision with volume threshold, compliance coverage map, audit-trail posture, and a build-vs-buy economic analysis — all survivable under ICAI audit, income tax assessment, and GST review.

### How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs

Source: https://www.terra-insight.com/insights/evaluate-reconciliation-software-india/

- **Problem:** Standard SaaS evaluation scorecards score reconciliation platforms on generic UX and integration dimensions but omit three India-specific filters — statutory compliance coverage, Indian payment rail support, and config-only deployment — that determine whether the finance team will spend the first six months of go-live rebuilding TDS, GSTR-2B, NACH, and MT940 logic themselves.
- **Logic:** Apply a 10-point framework with three binary filters first: native TDS net-of-gross and section-code matching, GSTR-2B JSON ingestion with Rule 36(4) cap, and NACH NPCI XML plus SWIFT MT940 parsing. Then score seven differentiators: matching engine depth, ERP connectors, audit trail immutability, exception taxonomy, security certifications, pricing, and POC outcome on the buyer's own data.
- **Config:** Evaluation scorecard with weighted scoring for each of the 10 criteria, demo question bank, and a contractual match-rate floor clause (70–85% first-pass) to be inserted in the MSA. Vendor responses are recorded against an evidence trail that survives procurement handover.
- **Output:** A defensible 10-point vendor comparison matrix, a signed MSA with a 2–4 week go-live commitment, a contracted match-rate floor, ISO 27001:2022 and AWS Mumbai residency verified, and a POC report showing live-data performance before contract signature.

### Exception Management in Reconciliation: From Detection to Resolution

Source: https://www.terra-insight.com/insights/exception-management-reconciliation-india/

- **Problem:** Exceptions that are detected but not classified, routed, and resolved within SLA accumulate into the reconciliation backlog. A queue growing 100 items per month without resolution is a process failure, not a matching failure.
- **Logic:** Classify every unmatched item into a named variance type (TAX_DEDUCTION, FEE_DEDUCTION, TIMING_DIFFERENCE, AMOUNT_MISMATCH, MISSING_CREDIT), route to the correct resolver, and enforce type-specific SLAs. Feed recurring patterns (same deductor, same gateway MDR drift, duplicate UTRs) into a prevention layer so new exceptions shrink over time.
- **Config:** Variance taxonomy, resolution SLAs per type (1–5 business days), role-based routing, CFO-visibility threshold above ₹1 lakh, and counterparty watch lists for chronic offenders.
- **Output:** A finite, ageing-tracked exception queue that clears within the current cycle, an RCA report highlighting the 3–5 systemic causes of 70–80% of exceptions, and a shrinking backlog trajectory.

### Jewellery Export Partial Realisation and EEFC Account Reconciliation

Source: https://www.terra-insight.com/insights/export-jewellery-partial-70-percent-realisation-eefc-account-fema-india/

- **Problem:** Indian jewellery exporters routinely receive only partial realisation on high-value export shipments — typical patterns are 60% to 80% realised within the nine-month FEMA window, with the balance stretched to month ten to fifteen due to buyer cash-flow, currency-hedge timing, or slow-payment terms in specific markets. Each partially realised shipment requires a four-way reconciliation between the shipping bill (filed with customs on the export date), the commercial invoice (issued to the foreign buyer), the FIRC (issued by the AD Category-I bank on each inward remittance), and the BRC (issued after full realisation as the closure certificate). The reconciliation drives the AD bank extension request under the RBI Master Direction, the EEFC account credit for the realised portion, the IGST refund claw-back exposure under Rule 96B of the CGST Rules if realisation is delayed, and the MEIS / RoDTEP scrip closure for the shipping bill. Exporters running this reconciliation manually across 300-500 shipping bills a year miss the AD bank extension window on 5% to 15% of shipments, triggering FEMA contravention exposure and Rule 96B claw-back on refunded IGST.
- **Logic:** Anchor the reconciliation on shipping bill number as the primary key. For each shipping bill, capture shipping bill date, port, HS code, quantity, invoice value, currency, buyer name, and buyer country. Match the commercial invoice on shipping bill number and reconcile invoice value against shipping bill value with tolerance for known negotiated adjustments. Match FIRCs on shipping bill number (or on commercial invoice reference where the AD bank tags the FIRC accordingly), aggregate FIRC value in foreign currency, and reconcile against shipping bill invoice value. Compute the realisation ratio and days-to-realisation from shipping bill date. Flag shipping bills approaching the nine-month window with unrealised balance for AD bank extension request triggering. Flag shipping bills past the nine-month window without extension for Rule 96B exposure calculation. Match BRC issuance on shipping bill number as the closure state. Cross-reference EEFC account credits against realised FIRC values by currency and month for the EEFC holding-period discipline.
- **Config:** Shipping bill master with shipping bill number, date, port, HS code (7113 jewellery / 7108 gold / 7102 diamond / 7103 stones), quantity, FOB value, currency, buyer name, buyer country, and consignment declaration reference (EDF / SDF); commercial invoice master with shipping bill link, invoice value, currency, adjustment reasons; FIRC master with FIRC number, date, remitter, amount, currency, shipping bill link (via EDPMS tagging); BRC master with BRC number, date, shipping bill link, realised value, write-off notation; EEFC account master with currency, balance, credit dates, holding-period expiry dates; AD bank extension request master with shipping bill link, request date, approval status, extension expiry date; Rule 96B claw-back working with shipping bill link, unrealised value, refunded IGST attributable, interest computation; MEIS / RoDTEP scrip status per shipping bill; hedging contract master where applicable, cross-referenced by shipping bill and currency.
- **Output:** A rolling shipping-bill closure dashboard: open shipping bills with days-to-nine-month-window remaining; shipping bills approaching the AD bank extension trigger point with recommended action; shipping bills past the window without extension flagged for Rule 96B exposure calculation; shipping bills fully realised and eligible for BRC issuance; shipping bills BRC-closed and eligible for MEIS / RoDTEP scrip drawdown. EEFC account movement report showing credits by currency and month, holding-period expiry, and mandatory conversion at month-end. FIRC-to-shipping-bill reconciliation report showing matched, partial-matched, and unmatched FIRCs with EDPMS status. IGST refund status per shipping bill showing refunded amount, Rule 96B exposure if applicable, and claw-back deposit computation with interest.

### Fabric-to-Garment Inverted-Duty Refund Reconciliation for Textile

Source: https://www.terra-insight.com/insights/fabric-garment-inverted-duty-refund-textile/

- **Problem:** Garment manufacturers assume that GST rate harmonisation between fabric (12%) and apparel (12%) closed the inverted-duty refund window, so they stop filing RFD-01 for the DTA leg and leave 15 to 30 percent of the eligible ITC accumulation stranded in the electronic credit ledger. The residual accumulation arises from the composite input mix — dyes and chemicals at 18%, trims and packaging at 18%, and third-party cotton yarn purchased at 5% still create net ITC above the 12% output tax burden. The two-year statutory window under Section 54 runs from the relevant date; without a monthly reconciliation the eligible amount silently expires.
- **Logic:** Build a Net ITC register per month that excludes input services and capital goods per the Notification 14/2022 amendment. Aggregate input-only ITC across the composite mix — cotton yarn at 5%, dyes and chemicals at 18%, trims and packaging at 18%, other physical goods. Compute Adjusted Total Turnover per the Rule 89(5) definition (turnover excluding zero-rated supplies made under LUT and turnover on which refund is being claimed under sub-rule 4A/4B). Compute Turnover of Inverted-Rated Supply — the domestic garment output at 12%. Apply the formula: Max Refund = (Turnover of inverted-rated supply × Net ITC / Adjusted total turnover) − Tax payable on inverted-rated supply. File RFD-01 with statement 1A and invoice-level input detail before the two-year window closes.
- **Config:** Input master with GST rate per HSN — cotton yarn HSN 5205/5206 at 5%, dyes and chemicals HSN 3204 at 18%, trims and labels HSN 5807 at 18% or 12%, packaging materials HSN 4819 at 18%; output master with garment HSN 61 or 62 at 12%; ITC ledger split by input goods versus input services versus capital goods per the Notification 14/2022 exclusion; monthly turnover feed split by inverted-rated DTA versus zero-rated export versus other; RFD-01 statement 1A template with invoice-level input aggregation; two-year window monitor per month per financial year end date.
- **Output:** A month-end inverted-duty refund pack: Net ITC per Rule 89(5) definition, Adjusted Total Turnover, Turnover of Inverted-Rated Supply, Tax payable on inverted-rated supply, Maximum Refund per the formula, and the RFD-01 statement 1A payload ready to file. A two-year ageing view highlights months approaching the Section 54 deadline. A reconciliation to the electronic credit ledger movement ties the claimed refund to the ledger debit and blocks double-claim against the zero-rated export refund or the general ITC utilisation.

### FASTag Toll Reconciliation for Indian Fleet Operators and Logistics Companies

Source: https://www.terra-insight.com/insights/fastag-toll-reconciliation-india/

- **Problem:** Indian fleet operators running 50 to 500 trucks face a structural FASTag reconciliation gap — NETC daily MIS files arrive per issuer bank with 0.1-0.4% double-deduction incidence, blacklisted-tag deductions at 2x, wallet topups split across UPI/IB/auto-topup channels, plaza-vs-route exceptions on unplanned diversions, and a GST split (toll exempt under Notification 12/2017 entry 23 vs NETC switching fee taxable at 18% SAC 998599) that breaks single-line journal entries.
- **Logic:** Reconcile vehicle ID and tag ID against trip sheet route per day with each MIS deduction tied to a planned plaza, flag same-tag-same-plaza events inside the re-read tolerance as double-deduction disputes, separate the wallet topup ledger (UPI/IB/auto-topup) from the toll deduction ledger and tie both to bank statement debits, split each deduction into exempt toll plus taxable switching fee for GSTR-3B classification, and maintain the Section 393(1) Sl. 6(i) codes 1023/1024 transporter TDS ledger with PAN-based nil-deduction declarations under the legacy 194C(6) framework refreshed at every FY boundary.
- **Config:** Vehicle master keyed by registration number with tag ID, vehicle class and issuer bank, plaza master with plaza code, location and acquirer bank, route master with planned plaza sequence per origin-destination pair, MIS ingest from each issuer bank's daily file, dispute register with NETC dispute reference and ageing, wallet topup channel mapping (UPI VPA, IB beneficiary, auto-topup mandate), GST line tax-treatment table (toll exempt, switching fee SAC 998599 18%), and transporter vendor master with PAN, 393/1002 default rate and 194C(6) declaration flag.
- **Output:** A daily reconciled view per vehicle showing planned plazas vs deducted plazas with double-deduction exceptions coded by reason, monthly tag-wise toll spend tied to bank statement debits, GST split between exempt toll and taxable switching fee feeding GSTR-3B 3.1(d) and 4(A)(5) respectively, a transporter payment ageing showing TDS deducted at 1%/2% under codes 1023/1024 or 194C(6) nil-deduction flag, and a wallet float position by issuer-bank by truck class with low-balance alerts.

### FCI Custom Milling Rice (CMR) Outturn Reconciliation for Millers

Source: https://www.terra-insight.com/insights/fci-custom-milling-rice-cmr-outturn-reconciliation/

- **Problem:** A mid-tier UP or AP rice miller receiving 10,000 MT of paddy from a state procurement agency (SFC UP, PCF Punjab, Markfed Haryana, TDCCOL Telangana, or equivalent) under an FCI Custom Milling Rice contract must reconcile paddy inward by Delivery Order and lot, milling operations by shift and paddy variety, CMR delivery to FCI by Acceptance Note and depot, the mandated 67 percent raw / 68 percent parboiled outturn ratio, FCI acceptance test results (broken, damaged, foreign matter, moisture) with any value cut applied, milling-charge invoicing to the state agency with Section 194C code 1023 job-work TDS at 2 percent, by-product retention (husk, bran, broken rice) reconciled to paddy inward for weight-closure discipline, and the Section 43B(h) 45-day MSMED payment window on the state agency's remittance schedule. Manual reconciliation across paddy inward, CMR delivery, outturn calculation, quality-test result, and milling-charge realisation exposes the miller to security-deposit recovery on outturn shortfall, Rice-Milling Industry Act permit-cancellation risk, Form 26AS mismatches on the 194C code 1023 TDS credit, and undiscovered value-cut leakage on rejected or partly-accepted consignments.
- **Logic:** Ingest the paddy inward register from the state procurement agency by Delivery Order number, lot number, paddy variety (Common Grade or Grade A), and net weight after moisture normalisation. Carry the paddy inward weight into the mill's shift-level milling register, capturing shift start and end, milling variety, paddy consumed, rice produced (raw or parboiled), by-product weights (husk, bran, broken rice), and processing loss. Aggregate to a CMR-agreement running balance keyed to the Delivery Order and the state agency, computing the outturn ratio as (rice delivered plus rice in transit to FCI depot) divided by (paddy consumed on the CMR account), and flagging any Delivery Order tracking below the 67 or 68 percent floor within the mandated delivery window. Match every FCI Acceptance Note against the mill's dispatch note by consignment number, capturing the FCI acceptance-test result — broken, damaged, foreign matter, moisture — and any value cut or rejection. Generate the milling-charge invoice to the state agency by month against the paddy handed over, apply Section 194C code 1023 TDS at 2 percent (or 1 percent for Individual/HUF miller) as the deduction the state agency will make at remittance, and reconcile the TDS credit against Form 26AS at the miller's PAN in the following quarterly cycle. Track by-product sales by counterparty (biomass plant, solvent-extraction plant, distillery, starch mill) and reconcile aggregate by-product weight against paddy inward within the 100-percent weight-closure tolerance.
- **Config:** State procurement agency master by state (SFC UP, PCF Punjab, Markfed Haryana, MARKFED Punjab, TDCCOL Telangana, HAFED Haryana, and equivalent), each with TAN, GSTIN, PAN, and Section 194C code 1023 TDS mapping; paddy master by variety (Common Grade, Grade A) with MSP for the KMS by state and any state bonus; Delivery Order register by DO number, lot number, DO date, variety, net weight, moisture at DO; mill shift-level milling register by shift start/end, milling stream (raw or parboiled), paddy consumed, rice produced, by-product weights; CMR agreement master by KMS and state agency with contracted volume, delivery window, outturn ratio (67 raw / 68 parboiled), and security-deposit position; FCI depot master with Acceptance Note format, Quality Control Officer contact, and value-cut schedule per the Uniform Specifications; by-product counterparty master (biomass plant, solvent-extraction plant, distillery); Section 43B(h) MSME flag at the state-agency-payer side (miller may hold MSME registration below the small-enterprise threshold); e-invoicing threshold check for the milling-charge invoice; FSSAI licence at the mill for open-market rice and by-product sale.
- **Output:** A month-end CMR reconciliation pack: paddy inward register by Delivery Order and lot with aggregate paddy consumed; shift-level milling register with rice produced, by-product weights, and processing loss; CMR delivery register to FCI by Acceptance Note with FCI acceptance-test result and any value cut applied; outturn ratio calculation by Delivery Order tracking against the 67/68 percent floor with early-warning alerts on tracking shortfall; milling-charge invoice register to the state agency with Section 194C code 1023 TDS at 2 percent computed at the invoice raise; Form 26AS reconciliation at the miller's PAN against the state agency's TAN and code 1023 remittance schedule; by-product weight closure against paddy inward within tolerance; Section 43B(h) MSMED interest tracker on state-agency remittance delays past the 45-day window. The pack supports the miller's own end-of-season CMR agreement closure, the security-deposit release from the state agency, the annual statutory audit on 194C code 1023 TDS, and the Rice-Milling Industry Act compliance filing with the state Directorate of Food and Civil Supplies.

### Fertilizer DBT: NBS vs Urea Cost-Plus Reconciliation India Cornerstone

Source: https://www.terra-insight.com/insights/fertilizer-dbt-nbs-vs-urea-cost-plus-reconciliation-india/

- **Problem:** A cooperative fertilizer manufacturer such as IFFCO that runs both a Urea plant and a DAP/NPK complex plant, or a private player such as Coromandel International with the same dual footprint, must reconcile two structurally different subsidy regimes — NBS on 28 phosphatic and potassic grades at fixed Rs per kg nutrient, and Urea Cost-Plus on the statutory Rs 242 per 45-kg bag MRP unchanged since 01 March 2018 — through a single Fertilizer DBT post-sale claim mechanism that depends on retailer-wise PoS sale-out captured on 2.60 lakh Aadhaar-biometric devices and settled weekly through the e-Urvarak portal. The dispatch register at the manufacturer's plant, the stock-at-retailer register on the portal, the PoS sale-out record at each retailer, and the claim register at the Department of Fertilizers are four different data surfaces that must reconcile line-by-line every week; a mismatch at any link — dispatch versus retailer receipt, opening stock versus prior-week closing, PoS sale versus buyer authentication, claim submission versus portal acknowledgment — defers subsidy realisation by at least one full weekly cycle and creates working-capital exposure that at a Rs 500 crore monthly claim scale is material. Manual reconciliation across dual regimes typically loses per-grade nutrient-weight consistency for NBS, misreads unit-wise Cost of Production allocation for Urea, and over-claims against retailers whose PoS upload has lagged the sales calendar.
- **Logic:** Configure two parallel claim streams on the reconciliation platform — one for Urea Cost-Plus keyed to the notified unit-wise energy-normalised Cost of Production and the statutory MRP, and one for NBS keyed to the current-quarter per-kg nutrient rates for N, P, K, and S and the fixed nutrient content per grade (for example 46 per cent Phosphate in DAP, 60 per cent Potash in MOP, and the 21 NPKS complex grade formulations). Ingest the dispatch register from the plant SAP or ERP, the retailer receipt confirmations from the e-Urvarak portal, the PoS sale-out feed from the portal (retailer-wise, buyer-authentication-flag-wise), and the claim acknowledgment feed from the Department of Fertilizers. Chain every PoS sale record back to the parent dispatch and the retailer's opening stock; produce a per-grade per-retailer sale-out summary that becomes the weekly claim pack; flag exceptions where dispatch minus opening stock does not equal closing stock plus sales, where biometric authentication fell back to Voter ID or KCC above a threshold, or where PoS upload lag exceeded 72 hours. Reconcile bank credit of released subsidy against the claim submitted, per grade, per week, per plant.
- **Config:** Retailer master with iFMS ID, PoS device ID, cooperative or private status, geography, and PoS authentication-failure-rate rolling 90-day average; grade master with NBS versus Urea Cost-Plus flag, current NBS rate per kg for each nutrient (N, P, K, S) per grade, unit-wise energy-normalised Cost of Production for Urea by plant, statutory MRP Rs 242 per 45-kg bag Urea and manufacturer-set MRP by grade for NPK; dispatch register feed from SAP or ERP with dispatch reference, retailer iFMS ID, grade, quantity, bag count; PoS sale-out feed from e-Urvarak portal with retailer iFMS ID, grade, quantity, buyer Aadhaar hash or fallback identifier, biometric authentication flag, sale timestamp; opening and closing stock reconciliation cadence weekly; claim submission cadence weekly with statutory Monday cutoff; Department of Fertilizers claim acknowledgment feed; bank credit reconciliation of released subsidy against claim reference; Section 194Q code 1031 TDS configuration for high-value raw material purchase (rock phosphate imports, ammonia, muriate of potash) and Section 194H code 1015 TDS on dealer and area-distributor commission.
- **Output:** A weekly two-stream claim pack: NBS stream by grade, by retailer, with nutrient-weighted subsidy calculation; Urea Cost-Plus stream by plant, by retailer, with unit-cost-delta calculation; consolidated by plant, by state, by claim week. A dispatch-to-PoS-sale-out reconciliation view per retailer per week with exception flagging on PoS upload lag, biometric authentication fall-back rate, opening stock mismatch, and dispatch versus receipt variance. Bank credit reconciliation of released subsidy against submitted claim reference at grade level. Consolidated Form 26AS reconciliation feed for Section 194Q payment code 1031 on high-value raw material purchase and Section 194H payment code 1015 on dealer commission. Audit-ready pack for statutory audit and Department of Fertilizers verification: dispatch, receipt, opening stock, sales, closing stock, claim submitted, claim acknowledged, subsidy credited, exceptions and their resolution.

### Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators

Source: https://www.terra-insight.com/insights/financial-distress-signals-bank-statements/

- **Problem:** A bank statement can show adequate balances at the statement date while concealing multiple months of payment failure — NACH bounces, cheque returns, overdraft usage, and minimum balance penalties each leave specific narration patterns that manual review misses at scale.
- **Logic:** Match transaction descriptions against known narration patterns for NACH bounce charges, cheque return charges, overdraft interest debits, minimum balance penalties, and NPA-related bank entries. Record count, total value, and frequency by month. Identify months where multiple distress signals co-occur.
- **Config:** Enable for all credit underwriting workflows. Configure distress signal count threshold based on lender policy (typical: flag if 3+ NACH bounces in 12 months). Cross-reference with over-leverage signals to assess whether distress is driven by over-obligation.
- **Output:** Financial distress section in the credit report listing each distress signal type, count, total charge value, and distribution across the statement period, with months containing multiple co-occurring signals highlighted.

### NBFC Fixed Deposit Early Closure: Penalty Netting and Reconciliation

Source: https://www.terra-insight.com/insights/fixed-deposit-early-closure-penalty-netting-nbfc-india/

- **Problem:** An NBFC-D depositor closes a fixed deposit before maturity. Interest that was booked at the contractual term rate now needs to be recomputed at the bucket rate for the actual run tenure at the original booking date, less a premature-closure penalty. The final payout — principal plus revised interest less penalty less TDS — must tie to the depositor certificate, the LMS entry, the bank payout, and the TDS return under a single audit trail.
- **Logic:** At the closure event, fetch the historical rate card for the original booking date. Identify the applicable bucket for the actual run tenure and read the revised rate. Compute pro-rata interest at that revised rate over the run tenure. Deduct the penalty percentage (0.5% to 1%) from the revised interest. Compute TDS under Section 393(1) Sl. 12 code 1002 on the net interest at 10% with valid PAN. Reverse any interim TDS that was deducted on quarterly-accrued interest at the term rate. Net all components into the payout amount and route through NACH credit or RTGS to the depositor's registered bank account.
- **Config:** Historical rate card by booking date and tenure bucket. Penalty rate slabs by depositor category (regular, senior citizen, staff). NACH mandate register for depositor payout. TDS parameter set — threshold, rate, exemption where 15G/15H is on file. Ind AS 109 EIR schedule per deposit for interest-expense reversal on early closure.
- **Output:** Depositor closure statement showing term-rate interest, revised-rate interest, penalty, net interest, TDS deducted, and net payout. LMS entry marking the deposit closed on settlement date. TDS ledger entry flowing into Form 26Q under the NBFC's TAN. Ind AS 109 interest-expense adjustment routed through the P&L in the closure period.

### Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification

Source: https://www.terra-insight.com/insights/fixed-asset-reconciliation-india/

- **Problem:** Fixed asset reconciliation in India combines three matches: FA register to GL book value, depreciation schedule to Companies Act Schedule II useful-life rates, and physical verification to the register. GST ITC on capital goods adds a fourth — matching GSTR-2B and respecting Section 17(5) and Rule 43 reversals.
- **Logic:** Match each asset line against GL by asset code, against the depreciation schedule by class and useful life, and against the physical verification sheet by asset tag. Run Rule 43 proportional reversal for mixed-use assets and flag Section 17(5) blocked ITC. Treat additions and disposals as a separate sub-ledger reconciled to capex approvals and disposal memos.
- **Config:** Asset-class-to-useful-life mapping, WDV and SLM method flags per class, capex approval linkage, and blocked-ITC categories per Section 17(5).
- **Output:** Reconciled FA register tying to GL, a depreciation schedule compliant with Schedule II, a physical verification variance report, and an auditor-ready capital-goods ITC working paper.

### Flat-Rate MDR Concealing Per-Network Cost: Method-Mix-Weighted Reconciliation

Source: https://www.terra-insight.com/insights/flat-rate-mdr-concealing-network-cost-india/

- **Problem:** A single flat headline MDR percentage on a payment-gateway plan conceals an order-of-magnitude variance across instruments and networks — bank-account UPI is zero, RuPay debit is zero, non-RuPay debit is capped under 1%, credit cards run 1.4% to 2.5%, and Amex/Diners sit at 2.95% to 3.5%. For a UPI-heavy OTT or subscription merchant the flat rate is a multiple of the method-mix-weighted true cost; the apparent over-recovery is a mix of platform-fee renegotiation opportunity and Pattern #1 network-MDR leakage on zero-MDR cells.
- **Logic:** Build a method-mix-weighted expected-cost model from the gateway's settlement file: split volume by instrument and network, multiply each cell's share of total volume by its contracted or regulated rate, sum to a weighted expected percentage, and compare to the flat rate actually billed. The gap times monthly volume is the apparent over-recovery. Parse the gap between the platform-fee portion (renegotiable to a sub-cell rate card) and the network-MDR portion that is legally zero on UPI bank-account and RuPay debit.
- **Config:** Per-gateway, per-network MDR rule set with the regulated zero-MDR cells (bank-account UPI, RuPay debit) hard-coded; method-mix decomposition by instrument and network with RuPay-credit-on-UPI and PPI-on-UPI separated from bank-account UPI; contracted-rate table per network separate from published-rate baseline; flat-rate-vs-weighted comparator that flags any gap above 0.15 percentage points; GST line isolator at 18% on the fee only.
- **Output:** A method-mix-weighted expected-cost report (per-network shares, per-cell rates, weighted expected percentage) reconciled to the flat rate billed, with the apparent over-recovery quantified in rupees and parsed between renegotiation opportunity and Pattern #1 leakage. The output is the dispute pack and the rate-card renegotiation brief the CFO or controller takes to the gateway's relationship leadership.

### Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns

Source: https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation/

- **Problem:** A Flipkart weekly T+7 bank credit bundles four deductions — category commission (5-20%), 1% Section 52 TCS, return adjustments, and logistics charges — each with distinct ledger and compliance treatments. Without per-order unpacking, commission ITC is missed and TCS in GSTR-2B cannot be reconciled.
- **Logic:** Matching joins the Flipkart Seller Hub settlement report against the weekly bank credit using net amount plus date, then resolves each order by order_id into gross selling price, commission, TCS, return adjustment, and shipping. TCS lines are cross-matched with GSTR-2B Part II and Form 26AS Part F; returns are linked back to original forward-sale order IDs for revenue reversal.
- **Config:** Category-wise commission rate table, Section 52 TCS matcher (0.5% CGST plus 0.5% SGST intra-state or 1% IGST inter-state), and return-to-forward-sale linkage for revenue reversal.
- **Output:** Disaggregated revenue ledger per order, commission ITC claim aligned to GSTR-2B, reconciled TCS credit in GSTR-3B, and return-adjustment journal with TCS reversal where applicable.

### FOMP Warranty Back-Charge Accounting for Indian Auto Component Tier-1 Suppliers

Source: https://www.terra-insight.com/insights/fomp-warranty-back-charge-accounting-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers face FOMP (Field Operating Manufacturing Plant) warranty back-charges at 1-3% of monthly OEM billing raised 6-18 months after vehicle sale. Each back-charge has a claim ID traceable to a specific dispatch batch and demands an 8D root-cause response within 14-30 days. Ind AS 37 constructive-obligation provisioning at 4-6% of trailing revenue, Section 34 GST credit-note timing on returned parts with a 30 November cutoff, and Tier-2 passthrough recovery on supplier-attributable root cause all overlay the cycle.
- **Logic:** Receive each FOMP claim ID from the OEM warranty system, link to the source dispatch invoice through batch traceability, route to the engineering 8D workflow with a 14-30 day response timer, classify as accepted or contested based on 8D outcome, raise Section 34 GST credit note within the 30 November window for accepted claims with physical return, age open FOMP exposure by claim-ID under the Ind AS 37 provision model, and trigger Tier-2 back-charge passthrough where root cause is sub-vendor attributable.
- **Config:** FOMP running account per OEM keyed by claim ID and warranty period, batch traceability map from claim ID to source dispatch invoice, 8D response workflow with 14/21/30-day reminders, Ind AS 37 provision model by OEM and part family with quarterly refresh, Section 34 GST credit-note workflow with 30 November calendar trigger, Tier-2 passthrough register linking OEM claim ID to Tier-2 supplier batch.
- **Output:** A FOMP exposure register by OEM and claim ID aged by claim age band, 8D response queue with overdue flags, Ind AS 37 provision roll-forward by quarter, Section 34 GST credit-note action queue keyed by approaching cutoff, Tier-2 passthrough debit candidates with root-cause evidence trail, and a monthly FOMP run-rate trend by part family for the provision refresh.

### Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate

Source: https://www.terra-insight.com/insights/food-processing-reconciliation-india/

- **Problem:** Indian food processors reconcile across a multi-rate GST output structure (0% to 28% across categories), mandi/APMC procurement with state-specific cess variations, MSP-linked farmer payments for select commodities, FSSAI batch-level traceability on FoSCoS, MEGA Food Park common-facility usage charges, cold-chain freight reconciliation with temperature documentation, and Section 393(1) Sl. 6(i) contract-farming TDS — six overlapping rails that no generic ERP handles.
- **Logic:** Reconcile each invoice line to its HS code and GST rate band (0/5/12/18/28%); split mandi invoices into commodity value, aarthiya commission and state-specific mandi cess; route MSP-linked payments via DBT and reconcile per-quintal against declared MSP per season; maintain FSSAI batch register tied to FoSCoS returns; split MEGA Food Park common-facility charges into the GST-applicable and exempt components with Section 393(1) Sl. 6(i) codes 1023 / 1024 on the contractor share; deduct Section 393(1) Sl. 6(i) codes 1023 / 1024 on contract-farming payments above thresholds.
- **Config:** SKU master with HS code and GST rate tag per item; vendor master with mandi-vendor flag, state-cess applicability and aarthiya commission rate; farmer master with Aadhaar, bank account, land record and contract-vs-open-market flag; FSSAI batch register keyed by FoSCoS licence; cold-chain freight register with temperature-log requirement; Section 393(1) Sl. 6(i) deduction matrix with codes 1023 (individual/HUF) and 1024 (other) default for contractors and contract-farming FPOs.
- **Output:** A monthly food-processing close showing GSTR-1 outward supply by rate slab tied to dispatch ledger, mandi procurement reconciled by state with cess split, MSP-linked farmer payments DBT-confirmed per quintal against season MSP, FSSAI batch register tied to FoSCoS quarterly returns, MEGA Food Park common-facility usage reconciled per tenant, and Section 393(1) Sl. 6(i) TDS challan tied to contract-farming and contractor payments by codes 1023 / 1024.

### Forensic Audit in India under Section 148 and Section 211: Special Investigation Framework

Source: https://www.terra-insight.com/insights/forensic-audit-india-section-148-211-companies-act/

- **Problem:** Forensic audit in India is invoked under three different regimes — SFIO investigation under Companies Act Sections 210/211/213, SEBI investigation under SEBI Act Sections 11(2)(i) and 11C, and RBI fraud audit under the Master Directions on Fraud Risk Management. Each has distinct triggers, timelines, evidence standards and reporting endpoints. The engagement letter and scope must be drafted to the regime, not to a generic forensic template.
- **Logic:** The forensic auditor maps every procedure to one of three evidence standards: admissibility under the Bharatiya Sakshya Adhiniyam for SEBI/SFIO referrals; lender recovery and CRILC reporting for RBI cases; or internal board discipline for company-commissioned engagements. Reconciliation work — bank, related-party, statutory dues, vendor — anchors the evidence chain. Every transaction in the period under review is reconciled bank-to-ledger-to-counterparty to isolate diversion, round-tripping or false invoicing.
- **Config:** Engagement letter template per regime (SEBI, RBI, SFIO co-opted, company-commissioned), evidence-vault with chain-of-custody logs, reconciliation pack covering bank, related-party, statutory dues and vendor balances for the period under review, and a reporting framework aligned to FAIS 330.
- **Output:** Forensic audit report with admissible-evidence chain, transaction-level diversion or round-tripping map, recovery quantum estimate for lender consortium, and adjudication-ready exhibits for SEBI, RBI or NCLT proceedings.

### Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions

Source: https://www.terra-insight.com/insights/forex-reconciliation-india/

- **Problem:** Foreign currency transactions create three matching layers: invoice rate versus settlement rate (driving Ind AS 21 exchange differences), NOSTRO account balance versus bank foreign-currency statement, and forward-contract rate versus actual settlement. FEMA adds Form 15CA/CB compliance for outward remittances.
- **Logic:** Book each invoice at the invoice-date rate, match the settlement at the actual conversion rate, and post the difference to the exchange gain/loss account. Reconcile NOSTRO in foreign currency, then revalue to INR at the RBI reference rate at period end. For outward payments, match each remittance to its Form 15CA filing.
- **Config:** Dual-currency ledger, RBI reference rate feed, forward-contract hedge mapping, Form 15CA/CB linkage per outward remittance, and Section 195 TDS rules on payments to non-residents.
- **Output:** Reconciled forex receivables and payables, Ind AS 21 exchange differences posted correctly, FEMA-compliant outward remittance register, and a period-end revaluation pack for the statutory auditor.

### Forging Process Reconciliation: Die Wear, Flash Loss and Auto-Component Tax Treatment

Source: https://www.terra-insight.com/insights/forging-die-wear-flash-loss-reconciliation-auto-india/

- **Problem:** An Indian forging supplier producing crankshafts, connecting rods or axle shafts for OEM truck programs must reconcile billet weight inbound to finished-forging weight outbound across five process stages (heating, die-forging, trimming, heat-treatment, machining), with flash loss at 20-35 percent of input billet, die life of 5,000 to 30,000 cycles per cavity capitalised under Ind AS 16, free-issue billet on Rule 55 challan under Section 143 with one-year return and no inbound GST, conversion-service GST at 18 percent under HSN 9988 on the converted weight, and Section 394 TCS at 1 percent under payment code 1071 on flash and trim scrap sold externally — against a backdrop of high single-source debit-note exposure on drivetrain components that requires a separate quality-cost reserve under Ind AS 37.
- **Logic:** Maintain per-part-number master data of theoretical forging weight, contracted yield norm, contracted process-loss tolerance per process stage. Per heat lot, log inbound billet weight (Rule 55 challan), heating scale loss, die-forging output weight, flash and trim weighbridge, heat-treatment descale, machining envelope and machining swarf weighbridge. Close the billet-to-finished identity per heat lot and per part. Amortise the die capital cost over expected forging-cycle life under Ind AS 16 with cycle-counter trigger for next rebuild. Bill the conversion invoice at the contracted tonnage-class rate with 18 percent GST under HSN 9988. Net flash and trim scrap-credit on retain-and-sell at contracted scrap price and collect Section 394 TCS code 1071 from the external scrap dealer. Book OEM debit notes against the original heat lot and against the quality-cost reserve.
- **Config:** Per-part master with theoretical forging weight, yield norm and process-loss tolerance per stage; furnace-and-press master with energy and tonnage data; die-set register with cycle counter, refurbishment trigger and rebuild log; coil/billet-heat-traceable memorandum FI ledger per OEM per grade per heat under Rule 55; conversion-rate matrix per part and per process; scrap-category master (flash, trim, descale, swarf) with per-category price; Section 394 TCS code 1071 buyer master for external scrap dealers; OEM debit-note master keyed to original-delivery heat lot with quality-cost reserve under Ind AS 37.
- **Output:** A monthly forging reconciliation statement closing the billet-to-finished identity per heat lot, per part number and per process stage; die-cycle dashboard with refurbishment-trigger alerts; conversion invoice at contracted per-stage rates with 18 percent GST under HSN 9988 and Rule 55 challan cross-reference; flash and trim scrap-credit netting record at agreed per-category prices; Section 394 TCS code 1071 register on external scrap sales reconciled to Form 27EQ; debit-note register with quality-cost reserve roll-forward; and an audit-ready memorandum FI ledger that ties to physical billet, WIP and forging stock at any OEM-initiated count.

### Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025

Source: https://www.terra-insight.com/insights/form-131-tds-certificate-india/

- **Problem:** Form 131 replaces Form 16A as the quarterly TDS certificate from April 1, 2026. It includes payment codes and requires updated issuance and deductee reconciliation workflows, with cross-validation against Form 168.
- **Logic:** Deductor files the quarterly TDS return with deductee PAN, payment code, and amount; generates Form 131 from the e-filing portal; and issues it within 15 days of the quarterly return due date. Deductee matches Form 131 line items against the TDS receivable ledger on PAN, Tax Year, payment code, and amount, then cross-validates against Form 168.
- **Config:** Issuance timeline 15 days from the quarterly return due date. Quarterly reconciliation cycle aligned to return filing. Correction path via deductor re-filing and TRACES statement.
- **Output:** Reconciled quarterly certificate register, Form 131 to Form 168 cross-validation report, and mismatch queue for correction requests.

### Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS

Source: https://www.terra-insight.com/insights/form-141-unified-challan-statement-india/

- **Problem:** Form 141 is a unified challan-cum-statement replacing separate forms 26QB (property sale), 26QC (rent above ₹50,000), 26QD (contractor), and 26QE (crypto/VDA) from April 1, 2026. Individuals and HUFs must file specified-payment TDS through a single consolidated workflow.
- **Logic:** Identify the payment code under Chapter XX of Income Tax Act 2025 (property, rent, contractor, or VDA). Calculate TDS using the applicable rate and threshold. File Form 141 on the e-filing portal within 30 days from month-end of deduction, paying the challan simultaneously. Download the corresponding Form 131A/131B/131C/131D certificate and issue it to the deductee.
- **Config:** Specified-payment payment codes under Chapter XX. 30-day filing window from month-end of deduction. Unified e-filing portal workflow covering property, rent, contractor, and VDA scenarios.
- **Output:** Filed Form 141 register, certificate-to-Form 168 match for the deductee, and income tax return-ready TDS credits.

### Form 16 vs Form 26AS: What to Do When They Don't Match

Source: https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation/

- **Problem:** Form 16 reflects what the employer has calculated and certified, while Form 26AS reflects what TRACES has actually credited. Discrepancies arise from late return filing, PAN errors, challan mismatches, or amount differences, and the Income Tax Department treats Form 26AS as authoritative — claiming only Form 16 amounts creates Section 143(1) demand notices.
- **Logic:** Classify each Form 16 entry against Form 26AS Part A on four dimensions — employer TAN, Section 192, quarter, and amount — and route each discrepancy to its cause: late filing, PAN error (C1 correction), challan mismatch (C2 correction), or amount difference. Do not claim in ITR what Form 26AS does not show; trigger employer correction first.
- **Config:** Reconciliation rule mapping Form 16 Part A to Form 26AS Part A by employer TAN and quarter. Typed exception codes for late filing, PAN error, challan mismatch, and amount variance. Correction-return routing to C1 or C2 on TRACES.
- **Output:** ITR claims that match Form 26AS exactly, no Section 143(1) demand notices, and a closed correction loop with employer payroll for every pre-filing discrepancy.

### Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025

Source: https://www.terra-insight.com/insights/form-168-new-tds-statement-india/

- **Problem:** Form 168 replaces Form 26AS from April 1, 2026 as the unified annual tax credit statement. Its entries use payment codes and Tax Year instead of sections and Assessment Year, requiring updated reconciliation workflows and mapping tables.
- **Logic:** Download Form 168 for the relevant Tax Year from the Income Tax e-filing portal. Map each payment code to the corresponding legacy section code for cross-year comparison with FY 2025-26 records. Reconcile TDS receivable ledger entries to Form 168 by PAN, payment code, Tax Year, and amount.
- **Config:** Payment code mapping table covering sections 392 to 394. Tax Year conversion (AY 2026-27 becomes Tax Year 2025-26). Correction statement routing via the updated TRACES portal.
- **Output:** Reconciled Form 168 credits, classified variances by PAN error, payment code mismatch, not-yet-deposited, or timing gap, and correction request register for deductor follow-up.

### Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books

Source: https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation/

- **Problem:** A service provider with 50 clients can receive up to 200 Form 16As a year — one per deductor per quarter. Each must be TRACES-generated (manual certificates are invalid), carry the correct PAN and section code, and reconcile to Form 26AS before ITR filing. Under the Income Tax Act 2025, Form 16A is renamed Form 131 from April 1, 2026.
- **Logic:** Match each Form 16A to its Form 26AS entry on four keys — TRACES certificate number, deductor TAN, section code, and quarter — and to the TDS receivable ledger on invoice reference. Route wrong-section certificates to a deductor correction return, PAN mismatches to a C1 correction, and unfiled returns to a deductor follow-up before the correction window closes.
- **Config:** Certificate register storing TRACES number, TAN, section, PAN, and amount. Typed variance classifier for section mismatch, PAN mismatch, and unfiled return. Quarterly follow-up queue aligned to 15 August, 15 November, 15 February, and 15 June issuance deadlines.
- **Output:** Every Form 16A certificate reconciled to Form 26AS and the TDS receivable ledger before ITR filing, wrong-section and PAN errors corrected in time, and full TDS credit claimed in the ITR.

### Form 26AS / Form 168 Reconciliation for Auto-Component Suppliers: OEM TDS Mismatch Resolution

Source: https://www.terra-insight.com/insights/form-26as-reconciliation-auto-component-supplier-india/

- **Problem:** An Indian Tier-1 auto-component supplier billing ₹500 crore annually across 4 to 8 OEM TANs faces ₹25 to ₹50 lakh of annual TDS receivable from OEM deductions — under Section 393(1) Sl. 6(i).D(b) code 1024 for contractor TDS on tooling and conversion charges, Section 393(1) Sl. 8(ii) code 1031 for purchase TDS on net component sales above ₹50 lakh per OEM per FY, and selectively Section 393(1) Sl. 6(iii).D(b) and other codes. The deductions appear in Form 168 (FY 2026-27 onwards) and legacy Form 26AS (FY 2025-26 and earlier). Mismatches between OEM-side deductions and supplier-side books arise from deductor error, wrong PAN/TAN, late deductor filing, code mismatch and value mismatch — leaking TDS credit if not caught monthly, especially during the cross-era window where legacy 194x and new 1001-1092 codes coexist.
- **Logic:** Maintain a multi-OEM TAN-keyed TDS receivable register synchronised with monthly Form 168 / Form 26AS downloads from TRACES. For each OEM TAN, segregate Form 168 entries by payment code (1024 / 1031 / 1057 / others), match each entry against the supplier's invoice ledger using gross-value-and-deduction-percentage logic, route unmatched entries to a dispute register with deductor-correction-required flag, and track each dispute through TRACES correction lifecycle. Maintain a parallel cross-era reconciliation against legacy Form 26AS for any FY 2025-26 deduction still in correction cycle, ensuring legacy code 194C / 194Q / 195 / 206C entries do not net against new code 1024 / 1031 / 1057 / 1071 entries.
- **Config:** OEM customer master keyed by TAN with payment-code applicability flags, supplier invoice ledger with gross-value / GST-split / pre-GST-value, monthly Form 168 download calendar with TRACES login automation, mismatch classification taxonomy (wrong-PAN / wrong-TAN / wrong-code / wrong-value / missing-deduction / late-filing), dispute register with deductor-correction-action flag and TRACES correction-statement tracking, cross-era reconciliation rule routing pre-2026-04-01 deductions to legacy Form 26AS / 194x lineage and post-2026-04-01 deductions to Form 168 / 1001-1092 lineage.
- **Output:** A monthly Form 168 reconciliation dashboard segmented by OEM TAN and payment code, a TDS mismatch dispute register ranked by deductor-action-required status, a quarterly Form 168 vs books variance summary for controller-level review, a cross-era Form 26AS / Form 168 register flagging any deduction with code-mismatch during the FY 2026-27 transition, and an audit-defensible trail linking every Form 168 entry to its source invoice, payment code, and TRACES correction history.

### Jewellery Franchise Royalty and Brand-Use Fee Reconciliation

Source: https://www.terra-insight.com/insights/franchise-jewellery-store-royalty-reconciliation-section-194j-india/

- **Problem:** A jewellery franchisee running a regional store under a national brand receives a monthly royalty or brand-use fee invoice from the franchisor. The invoice must be routed through five distinct reconciliation surfaces — the master franchise agreement schedule (source of truth for the fee amount and any turnover-linked royalty layer), the franchisor's monthly tax invoice (SAC 9973 or 9997 at 18% GST), the franchisee's TDS deduction at Sl. 15 code 1005 (10% under legacy Section 194J), the franchisor's Form 26AS credit (deductee-side verification), and the franchisee's GSTR-2B ITC availability (with the 180-day Rule 37 payment rule). Franchisees running the reconciliation manually miss the 180-day ITC reversal at least once a year, use the wrong TDS section code (2% Sl. 4 code 1023 instead of 10% Sl. 15 code 1005), and generate Form 26Q filings that do not match the franchisor's records.
- **Logic:** Build a monthly franchise-fee reconciliation cycle anchored on the master franchise agreement schedule. On invoice receipt, classify the SAC (9973 for pure trademark licensing, 9997 for bundled brand-plus-support), verify the GST rate (18%) and the pre-GST value against the agreement schedule, and route to accounts payable. On payment approval, deduct TDS at 10% under Sl. 15 code 1005 on the pre-GST value, deposit within seven days of the following month, and record the deduction against the franchisor's PAN in the TDS ledger. Match the invoice to the GSTR-2B inward supply for the tax period; take ITC on the 18% GST subject to the invoice being reflected. Run a 180-day ageing report at day 165 as a payment-reminder trigger to prevent Rule 37 reversal. At quarter-end, file Form 26Q with the franchisor's PAN and section code, verify the credit appears in the franchisor's Form 26AS via AIS, and reconcile the deducted-and-deposited amount to the Form 26Q ledger.
- **Config:** Master franchise agreement register with agreement number, franchisor GSTIN and PAN, fee schedule (fixed monthly plus turnover-linked layer), escalation clause, and payment terms; SAC code master with 9973 (trademark licensing) and 9997 (bundled franchise) both at 18% GST; TDS payment-code master with Sl. 15 code 1005 (royalty and professional/technical services, 10%) as the default classification for franchise fees; invoice register with franchise-fee flag, SAC code, pre-GST value, GST value, TDS-deducted flag; ageing register with 180-day Rule 37 breach flag at day 165; Form 26Q filing register with quarter-end AIS verification checkpoint; GSTR-2B reconciliation register with franchisor-invoice-to-2B-match status and ITC-availed indicator.
- **Output:** A monthly franchise-fee reconciliation pack: agreement-schedule-to-invoice-value variance report with tolerance flags; SAC classification audit trail (9973 versus 9997) with GST rate verification; TDS deduction ledger at Sl. 15 code 1005 with Form 26Q filing status; Form 26AS credit verification (quarterly, at AIS refresh) showing franchisor-side deductee credit; GSTR-2B inward supply reconciliation with ITC-availability status; 180-day ageing report with Rule 37 breach flag and payment-escalation queue; year-end variance analysis showing total franchise fees paid, total TDS deducted-and-deposited, total ITC availed, and Rule 37 reversal-and-re-availment events for the audit trail.

### Free-Issue Material Accounting for Indian Auto Stamping Suppliers

Source: https://www.terra-insight.com/insights/free-issue-material-accounting-auto-stamping-india/

- **Problem:** Auto stamping suppliers receive free-issue steel coil from OEMs (or nominated steel majors) and press it into parts billing only a conversion service; the steel is OEM-owned throughout, held memorandum-only in a quantity ledger in metric tonnes, and the yield equation (FI in = finished parts + skeleton scrap + process loss) must close per coil within a contracted per-grade tolerance band — any unexplained shortfall is recovered from the supplier; on the disposal side, skeleton scrap is either returned to the OEM on a Rule 55 challan (no TCS) or retained-and-sold externally with Section 394 TCS code 1071 at 1%, with the scrap-credit value netted against the conversion-charge invoice.
- **Logic:** Maintain a memorandum FI quantity ledger in metric tonnes per OEM principal per grade per coil; receive FI on Rule 55 / Section 143 challan with the one-year return clock owned by the OEM; bill GST only on conversion service under Schedule II at 18% HSN 9988; close the yield identity opening + received − (parts dispatched at theoretical part weight × quantity + skeleton scrap weighbridge + process loss) within per-grade tolerance band; on scrap retain-and-sell, collect Section 394 TCS at 1% code 1071 from the external scrap dealer and remit; value retained skeleton scrap at the agreed scrap price and net the scrap credit into the conversion-charge invoice.
- **Config:** Per-OEM per-grade FI material master in MT (IS 513 CR, IS 1079 HR, dual-phase / AHSS grades, stainless, aluminium); contracted yield norm and process-loss tolerance per part per grade; Rule 55 inbound challan series; weighbridge integration for inbound coil and outbound scrap; scrap-credit rate per tonne per scrap category; Section 394 TCS code 1071 buyer master for external scrap dealers; FI audit-reconciliation statement format and monthly / quarterly / annual cadence.
- **Output:** A monthly FI reconciliation statement per OEM principal closing the tonnes-in-equals-parts-plus-scrap-plus-loss identity per grade, yield-variance flagging beyond contracted tolerance as an OEM recoverable, skeleton-scrap weighbridge tonnage tied to scrap-credit value and netted into the conversion invoice, Section 394 TCS register on external scrap sales reconciled to the buyer-wise TCS challan, and an audit-ready FI memorandum ledger that ties to physical stock at any OEM-initiated count.

### Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS

Source: https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india/

- **Problem:** EMS companies receiving free-issue material from brand customers (chipsets, display modules, batteries, branded packaging) must reconcile every FI receipt against the inbound Section 143 CGST delivery challan, BOM consumption per finished unit, return of unconsumed material or scrap, and the 1-year input return window — without entering the FI value in EMS books — while bearing shortage risk above contractual tolerance and insurance cover within the EMS gate.
- **Logic:** Maintain a parallel no-value FI inventory ledger keyed by brand customer GSTIN and FI part number; tie every FI receipt to a Section 143 inbound delivery challan; consume FI per BOM at production order completion; reconcile finished-goods FI content against brand outbound dispatch records; track the 1-year clock on each FI receipt with proactive return scheduling; reconcile shortage and excess against contractual tolerance and trigger charge-back accounting above tolerance.
- **Config:** FI configuration with brand customer master tagged for Section 143 principal, FI part number register separate from purchase inventory master, no-value inbound delivery challan ingestion, BOM linkage from FI part to finished good SKU, 1-year return clock per FI receipt, shortage tolerance per brand contract, insurance cover boundary flag (gate-in vs gate-out).
- **Output:** A monthly EMS close where every FI receipt ties to a Section 143 delivery challan, FI consumption rolls up against BOM and production order completion, finished-goods FI content matches brand outbound records, the 1-year clock dashboard surfaces any FI line approaching the return window, shortage above tolerance triggers a charge-back at FI declared value, and FI does not enter EMS revenue / COGS / inventory at value.

### Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers

Source: https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india/

- **Problem:** Auto stamping suppliers press OEM-owned free-issue steel coil into parts; the FI steel is memorandum-only and never enters purchase books, the supplier bills only the conversion charge under the Section 143 / Schedule II job-work model, and 15-35% of every coil leaves as skeleton scrap that is also OEM-owned — so the yield equation (FI steel in = finished parts + skeleton scrap + process loss in tonnes), the scrap-credit netting against conversion charges, the Section 394 scrap TCS at 1% on external sale, and the periodic FI material audit form a control set that generic ERP does not close and where any unexplained FI shortfall is a recoverable from the supplier.
- **Logic:** Maintain a memorandum FI quantity ledger in tonnes per OEM principal and grade; receive FI steel on a Section 143 challan with the one-year return clock; bill GST only on conversion charge (Schedule II service); close the yield identity closing = opening + received - (parts dispatched + skeleton scrap + process loss) within an agreed yield tolerance; value skeleton scrap at the agreed price and net the scrap credit against conversion; on external scrap sale collect Section 394 TCS at 1% code 1071; flag yield variance beyond tolerance as an OEM recoverable.
- **Config:** FI material master in metric tonnes by OEM principal, steel grade and coil; Section 143 inbound challan series with one-year clock; per-part theoretical yield and process-loss tolerance; conversion-charge rate card; agreed scrap price per tonne and scrap-credit netting rule; Section 394 code 1071 TCS for external scrap buyers; monthly/quarterly FI reconciliation statement format and annual physical-count schedule.
- **Output:** A periodic FI reconciliation statement per OEM principal closing the tonnes-in-equals-parts-plus-scrap-plus-loss identity, yield variance against tolerance flagged as recoverable where breached, skeleton-scrap tonnage tied to scrap-credit value and netted against the conversion invoice, Section 394 TCS reconciled on external scrap sales, and a memorandum FI balance that reconciles to physical stock at the annual count.

### Free-Issue Yarn/Fabric for Job-Work Reconciliation in Textile Industry

Source: https://www.terra-insight.com/insights/free-issue-yarn-fabric-job-work-reconciliation-textile/

- **Problem:** Indian brand-to-manufacturer garment export arrangements operate on CMP — the brand supplies free-issue yarn, fabric, trims, and packaging to the manufacturer under Section 143 CGST, the manufacturer charges only conversion. The free-issue material must be tracked on a Rule 55 delivery challan register that never touches the manufacturer's purchase inventory, must be drawn down against a bill of material at the sanctioned wastage tolerance, and must be received back or supplied from the job-worker's premises within 1 year — or the challan-based non-supply retros into a deemed supply under Section 143(3) with GST and interest from the original dispatch date. Manufacturers running 30-plus concurrent styles for multiple brands routinely lose reconciliation control on the 1-year clock, the wastage tolerance, and the ITC-04 quarterly return.
- **Logic:** Build a free-issue material register keyed by delivery-challan number, brand principal, HSN, dispatch date, quantity, value, and Section 143 maturity date (dispatch + 365 days). In parallel, build a bill-of-material master per finished style linking each garment SKU to consumed material at standard consumption with a wastage tolerance. On every dispatch-to-buyer of finished goods (or return-to-brand of unused material), draw down the free-issue register by standard consumption × units × (1 + wastage), matched by challan reference. Run aging buckets — 0-90, 91-180, 181-270, 271-365 days from dispatch — and escalate any challan crossing 270 days. At quarter-end, feed the register to the ITC-04 return: Table 4 dispatches, Table 5A returns, Table 5B out-shipments from job-worker premises, Table 5C wastage. Cross-foot the register to the goods-in-transit balance sheet account before every close.
- **Config:** Brand principal master with GSTIN, sourcing-agreement reference, wastage tolerance by fabric type; free-issue material master with HSN, unit of measure, standard cost, and Section 143 category (input vs semi-finished); bill of material per finished style with consumption per garment and wastage tolerance; delivery-challan register per Rule 55 (challan number, dispatch date, HSN, quantity, value, principal-GSTIN, job-worker-GSTIN, place of supply); return-challan register with the challan-linkage; aging bucket configuration (0-90 / 91-180 / 181-270 / 271-365 days from dispatch); Section 17(5) reversal rule for wastage above tolerance without brand-approved cause; ITC-04 quarterly or half-yearly filing schedule based on aggregate turnover threshold; goods-in-transit GL account for cross-foot.
- **Output:** A quarterly free-issue reconciliation pack: opening free-issue balance, period dispatches by principal, period draw-downs against bill of material, period wastage split (within tolerance / brand-approved deviation / Section 17(5) reversal), period returns to principal, and closing balance by challan aging bucket. Every challan crossing 270 days surfaces on a red-flag exposure list with the deemed-supply retro-GST calculation. The ITC-04 return is generated directly from the register — Table 4/5A/5B/5C mapped by challan reference — for filing on the CBIC portal. Wastage reversals feed the GSTR-3B ITC reversal line and the goods-in-transit clearance journal at close.

### Freight Forwarder Multimodal Reconciliation for Indian Logistics Operators

Source: https://www.terra-insight.com/insights/freight-forwarder-multimodal-reconciliation-india/

- **Problem:** An Indian freight forwarder running 380 multimodal shipments per month operates dual roles concurrently (pure forwarder versus NVOCC) with master-vs-house bill-of-lading reconciliation per consolidated container, currency-mix invoicing in USD/EUR/INR with FEMA reference-rate settlement, Section 393(2) Sl. 17 code 1057 TDS withholding on foreign-carrier payments with DTAA-rate determination, GST classification between 12 percent multimodal composite (SAC 996719) and individual-leg per-mode rates, plus Section 393(1) Sl. 6(i) codes 1023/1024 TDS receivable on Indian-shipper payments. The reconciliation must hold role-tagging per shipment, currency variance per line, and tax classification per leg consistent across booking, BL issuance, carrier invoicing and settlement.
- **Logic:** Build a per-shipment master keyed by shipper, consignee, origin pin/port, destination pin/port, container reference, MBL number, HBL number, mode mix (ocean/air/road), and currency per leg. Tag each shipment as pure-forwarder or NVOCC role. For NVOCC consolidations, match HBLs to MBL with TEU allocation and reconcile carrier MBL invoice to booked container; flag last-minute rolls, demurrage and detention. Apply FEMA reference rate per line for foreign-currency settlement; reconcile booking-day rate to settlement-day rate as forex P&L. Determine GST classification per shipment — 12 percent SAC 996719 multimodal composite for single-bill multi-mode, or individual-leg per SAC where billed separately. Compute Section 393(2) Sl. 17 code 1057 TDS on foreign-carrier payments at DTAA-relief rate with TRC + Form 10F evidence; file Form 15CA/15CB at remittance. Chase Section 393(1) Sl. 6(i) codes 1023/1024 TDS receivable on shipper payments through Form 26AS.
- **Config:** Shipment master with role tagging (forwarder vs NVOCC), mode mix flag and currency per leg; carrier master with foreign/domestic flag, TRC status, Form 10F filed status and DTAA article reference; MBL/HBL register with consolidation allocation; FEMA reference-rate ingest per business day; forex P&L computation per shipment per leg; GST classification engine with 12 percent SAC 996719 multimodal vs individual-leg rates; Section 393(2) Sl. 17 code 1057 TDS computation with DTAA-rate matrix; Form 15CA/15CB filing tracker; Section 393(1) Sl. 6(i) codes 1023/1024 receivable ledger by Indian shipper TAN; Form 26AS quarterly reconciliation.
- **Output:** A per-shipment reconciliation pack with role-tagged revenue, MBL-to-HBL allocation, currency-per-leg invoicing and forex P&L; per-NVOCC-container settlement reconciliation against ocean-carrier MBL invoice with last-minute roll, demurrage and detention flagging; GST classification report with 12 percent SAC 996719 composite vs individual-leg split feeding GSTR-3B 3.1(a); Section 393(2) Sl. 17 code 1057 TDS withholding log per foreign carrier with DTAA-relief evidence and Form 15CA/15CB compliance trail; quarterly Form 26AS reconciliation for codes 1023/1024 receivables by Indian shipper TAN; FEMA outbound-remittance compliance log.

### Freight GST Reconciliation: RCM, GTA Election, and ITC for Indian Manufacturers

Source: https://www.terra-insight.com/insights/freight-gst-reconciliation-india/

- **Problem:** Indian manufacturers run at least five distinct freight buckets — GTA at 5% RCM, GTA at 12% forward charge, non-GTA exempt, foreign-leg ocean/air with IGST under Section 5(3), and multimodal composite supply at 12% — each booked differently in GSTR-3B (3.1(d) for RCM payable, 4(A)(3) for RCM ITC, 4(A)(5) for forward charge ITC, exempt supply for non-GTA). A misclassification at the invoice booking stage compounds into ITC leakage at the GSTR-3B preparation stage and interest exposure at the audit stage.
- **Logic:** Classify each freight invoice at booking time by GTA status (consignment note issued or not), forward-charge declaration presence, mode of transport (road / rail / sea / air / multimodal) and leg geography (domestic / inbound / outbound / fully foreign), apply the correct tax bucket (5% RCM, 12% forward, exempt, 12% multimodal, IGST under Section 5(3)), reconcile against GSTR-2B for forward-charge entries and against the self-invoice register for RCM entries, and feed the right GSTR-3B box for each bucket.
- **Config:** Freight vendor master with GTA flag, forward-charge declaration status, and SAC default per vendor, freight invoice classifier table mapping invoice attribute (LR present, declaration, mode, leg) to tax bucket, self-invoice register for RCM compliance under Rule 36, GSTR-3B line mapping (3.1(d) for RCM payable, 4(A)(3) for RCM ITC, 4(A)(5) for forward ITC, 3.1(c) for exempt inward), and a Section 5(3) IGST RCM register for inbound ocean/air freight tied to BoE and shipping invoice.
- **Output:** A monthly freight reconciliation pack showing total freight spend decomposed by tax bucket, RCM payable computed per Notification 13/2017 list-A recipient flag, RCM ITC claimable in the same period (no time lag), forward-charge ITC reconciled to GSTR-2B by GSTIN, exempt freight tagged for non-claim, foreign-freight IGST under Section 5(3) tied to BoE and freight invoice with cross-reference to the importer's bank remittance, and an audit-ready evidence file showing the classification rule applied to each invoice.

### FSSAI Licence Renewal Cost Accounting for FMCG

Source: https://www.terra-insight.com/insights/fssai-licence-renewal-cost-accounting-fmcg/

- **Problem:** FMCG manufacturers operate multi-site plant networks with a mix of State Licences (per plant, turnover up to ₹20 crore per unit), a Central Licence at the Head Office for corporate multi-state operations, and — where any single plant exceeds ₹20 crore turnover — a plant-level Central Licence upgrade. Renewals are filed on the FoSCoS portal per licence per site with a 60-day pre-expiry window; late filing attracts ₹100 per day per licence. The reconciliation surface is scattered across the FoSCoS export, the plant compliance register, the compliance overhead GL, the CARO 2020 statutory-dues workpaper, and — for contract-manufactured SKUs — the co-packer master. Missed renewals expose the brand to labelling non-compliance and a CARO-disclosable statutory-dues delay, while duplicated fees (Head Office Central plus a plant State Licence where the plant has crossed the Central threshold) inflate compliance overhead by 10 to 25 percent on the licence-fee line.
- **Logic:** Build a licence footprint register keyed by manufacturing location, licence type (basic / state / central), FSSAI licence number, issue date, expiry date, and renewal filing due date (expiry minus 60 days). Cross-reference each licence to the plant turnover in the current FY — flag any State Licence at a plant that has crossed the ₹20 crore threshold as requiring a Central Licence upgrade at the next renewal cycle. Parse the FoSCoS portal export at monthly cadence to confirm each licence status and pending application count. Compare renewal filing dates to the 60-day due date; classify overdue applications by days-late bucket (0-30 days late, 31-90 days late, 90+ days late) and compute accrued late fees at ₹100 per day per licence. Reconcile the licence-fee GL to the sum of (renewals filed in the period × notified fee schedule) plus (late fees accrued in the period × 100 × days late). For contract-manufactured SKUs, run a co-packer FSSAI licence expiry alert — any co-packer licence expiring within 90 days triggers a compliance calendar item, and no invoice from an expired-licence co-packer clears three-way match.
- **Config:** Plant master with legal entity, plant address, FSSAI licence number, licence type, licence category (basic / state / central), issue date, expiry date, renewal filing due date, and current FY turnover; licence fee schedule from the FoSCoS portal by category and duration (1 to 5 years); Central Licence turnover threshold at ₹20 crore per unit; co-packer master with entity, plant address, PAN, FSSAI licence number, expiry date, and SKU-to-plant mapping; late-fee rule (₹100 per day per licence past expiry); compliance overhead GL account with sub-ledger by plant; CARO 2020 Clause 3(vii) workpaper linkage; Ind AS 38 prepaid-amortisation schedule for multi-year licences; contract-manufacturing TDS mapping to Section 393(1) Sl. 4 (payment codes 1001 / 1023, legacy 194C).
- **Output:** A monthly FSSAI licence footprint pack: total licences in force by type, upcoming renewals in the next 60 / 90 / 180 days, licences filed in the period with fees paid, late fees accrued, licences flagged for Central upgrade at next renewal, and co-packer licence expiry alerts. A CARO 2020 workpaper listing every plant with valid-licence status, pending-renewal status, and any late-fee incurrence for the FY. A licence-fee GL reconciliation cross-footing paid renewals plus accrued late fees to the compliance overhead account. An Ind AS 38 prepaid-amortisation schedule for multi-year licences straddling FYs, and a co-packer licence-expiry watch feeding the brand's compliance calendar for third-party manufacturing partners.

### General Trade Distributor Pyramid Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/general-trade-distributor-pyramid-reconciliation-fmcg/

- **Problem:** An Indian FMCG brand running a four-layer general trade pyramid — Brand → Super-Stockist → CFA → Sub-Stockist → Retailer — operates parallel masters in every state, primary sales flows in cleanly from the brand's depot SAP, but secondary sales arrives through 200 to 1,200 distributor DMS exports per period, route-coverage discipline is uneven across geographies, and Section 393(1) Sl. 18 commission TDS at 5 percent (payment code 1015, legacy 194H) applies at every commission node — CFA service fee, Super-Stockist incentive, Sub-Stockist appointment fee — with mis-characterisation between commission and buy-sell margin triggering both TDS exposure and Form 26AS gaps for the distributor counterparty.
- **Logic:** Build a per-state distributor master keyed by GSTIN and PAN, with layer assignment (Super-Stockist / CFA / Sub-Stockist), parent-child relationship, beat assignment, and commission-versus-buy-sell margin flag per cash-flow head. Reconcile primary sales out of brand SAP to inbound inventory at each Super-Stockist or CFA; reconcile CFA outbound dispatch to Sub-Stockist inbound; reconcile Sub-Stockist secondary-sales DMS feed to retailer scan or beat-coverage proxy. Maintain a channel-inventory bridge per SKU per state per period. Classify each commission cash flow under Section 393(1) Sl. 18 (code 1015), deduct at 5 percent above the deductee threshold, file under new TRACES taxonomy, and tie back to Form 26AS at deductee PAN level. Run quarterly the primary-vs-secondary gap diagnosis (channel-stuffing or destocking signal) by geography and feed to the regional sales manager.
- **Config:** State-wise distributor master (GSTIN, PAN, layer, parent, beats, commission-treatment per cash-flow head); brand SAP depot dispatch feed (primary sales by SKU by destination GSTIN); CFA inbound and outbound feeds (where the CFA is third-party); DMS secondary-sales feed per Sub-Stockist (SKU, beat, retailer code, period); route-coverage feed (declared retailers, visited, billed); channel-inventory opening balance per SKU per state; Section 393(1) Sl. 18 TDS rate table and threshold; commission-versus-margin classification rule per scheme master; Form 26AS download per distributor PAN per quarter; GST 2.0 rate-effective-date field per HSN to handle the 22 September 2025 straddle.
- **Output:** A quarterly pyramid reconciliation pack: per-state per-SKU primary-vs-secondary bridge, channel-inventory movement, route-coverage quality flag, distributor margin gross-up reconciled to commission TDS deposited (code 1015 / Section 393(1) Sl. 18), 26AS tie-out per deductee PAN, channel-stuffing or destocking diagnosis by geography for regional sales review, and a feed into the PLISFPI incremental-sales certification for the 53 named beneficiaries where the brand qualifies. The same pack feeds Section 15(2) CGST treatment determination on retro schemes, the TPM accrual reconciliation, and the audit pack on distributor balances at year-end.

### General Trade Distributor Reconciliation for D2C Brands: Stockist Network Cost Recovery

Source: https://www.terra-insight.com/insights/general-trade-distributor-reconciliation-d2c-india/

- **Problem:** D2C brands scaling into general trade face a high-cardinality reconciliation problem — sales invoices to 200+ distributors with 8 to 12 claim categories per distributor (damage, expiry, scheme, market development, rebate), SoR returns under Section 34 credit-note timing, Section 393 buyer-TDS and Section 394 seller-TCS interaction, and 21 to 45 day credit period management, where unstructured claim management typically over-pays 5 to 12 percent of scheme spend and unstructured aging exposes 2 to 4 percent of receivables to silent slippage.
- **Logic:** Maintain a distributor ledger per GSTIN with invoice-to-payment-to-claim-to-credit-note matching at line level. Decompose every claim into category (damage, expiry, scheme, MDF, rebate) and validate against agreed scheme PO and dispatch records before approving. Track SoR returns within Section 34 credit-note window. Enforce TDS-or-TCS precedence rule — buyer TDS overrides seller TCS once distributor confirms. Generate aging report per distributor for collection escalation.
- **Config:** Distributor master per GSTIN with credit period and scheme terms, SKU master with MRP-to-distributor-price schedule, scheme PO ledger with execution evidence, damage and expiry claim taxonomy, Section 393 and Section 394 threshold tracker per distributor, SoR window calendar, and aging buckets per credit period.
- **Output:** A reconciled general trade receivable ledger per distributor with claim variance versus agreed scheme isolated per campaign, SoR return-and-credit-note timing tracked within Section 34 window, Section 394 TCS collected and Form 26AS reflected per distributor, aging exposed per distributor and per region, and a board-ready view of net realisation per distributor cluster.

### GNFC, Chambal, RCF Urea Cost-Plus Reconciliation India

Source: https://www.terra-insight.com/insights/gnfc-chambal-rcf-urea-cost-plus-reconciliation-india/

- **Problem:** A dedicated Urea manufacturer such as GNFC Bharuch (approximately 6.36 lakh MT annual capacity), Chambal Fertilisers Gadepan (a Rajasthan-based multi-train Urea complex), or the Maharashtra PSU RCF at Trombay and Thal must reconcile a single-regime Cost-Plus subsidy stream keyed to a per-unit notified Concession Rate published by the Department of Fertilizers, apply it against the statutory Rs 242 per 45-kg bag MRP unchanged since 01 March 2018, and settle the resulting per-MT subsidy claim through the Fertilizer DBT e-Urvarak portal on a weekly cycle after retail sales are recorded on 2.60 lakh Aadhaar-biometric PoS devices. Six operational surfaces must chain end-to-end line by line: the plant DCS production log, the bagging line register, the dispatch register to each retailer, the retailer PoS sale-out feed from the portal, the weekly subsidy claim register, and the DBT bank credit against Department of Fertilizers sanction. Alongside these the natural gas Cost of Production audit workpapers must reconcile to the notified feedstock price and the pre-set energy norm submitted to the Cost Accounts Branch of the Department of Fertilizers under Modified NPS-III. A mismatch at any link — production versus bagging, bagging versus dispatch, dispatch versus retailer receipt, retailer receipt versus PoS sale-out, PoS sale versus claim, claim versus bank credit — defers subsidy realisation by at least one weekly cycle. A gas-consumption drift above the pre-set energy norm compresses the concession margin at the source. At an approximately Rs 1,400 crore quarterly covering claim scale for a single mid-sized Urea unit, the working-capital consequence of chronic upload lag or a mis-projected feedstock price is material.
- **Logic:** Configure the single Urea Cost-Plus claim stream on the reconciliation platform keyed to the current-quarter notified Concession Rate per MT published by the Department of Fertilizers, the pre-set energy norm in Gcal per MT for the unit, the notified feedstock price of natural gas and re-gasified LNG, and the statutory Rs 242 per 45-kg bag MRP. Ingest the DCS production log from the plant control system, the bagging register with batch and quality-certificate cross-reference, the dispatch register from SAP or the plant ERP with retailer iFMS ID mapping, the retailer PoS sale-out feed from the e-Urvarak portal (retailer-wise, buyer-authentication-mode-wise, timestamp-wise), the claim acknowledgment feed from the Department of Fertilizers, and the bank credit reconciliation against released subsidy per claim reference. Chain every PoS sale record back to the parent dispatch and the retailer's opening stock; produce a per-retailer, per-week claim pack; flag exceptions where PoS upload lag exceeds 72 hours from the sale event, where biometric authentication fell back to Voter ID or KCC above a threshold, where dispatch minus opening stock does not equal closing stock plus sales, or where gas consumption in the DCS log has drifted above the pre-set energy norm for the quarter. Reconcile the bank credit of released subsidy against the claim submitted per plant, per week, per Concession Rate applied.
- **Config:** Retailer master with iFMS ID, PoS device ID, cooperative or private status, geography, and PoS authentication-failure-rate rolling 90-day average; unit master with plant name and location, technology vintage, Snamprogetti or MW Kellogg or later revamp classification, pre-set energy norm in Gcal per MT, current-quarter notified feedstock price for natural gas and LNG, current-quarter notified Concession Rate per MT approved by the Cost Accounts Branch; product master with 45-kg bag SKU (statutory MRP Rs 242) and 50-kg bag SKU (statutory MRP Rs 268), neem coating flag mandatory per Fertilizer Control Order 1985; DCS production feed with hourly Urea tonnage and per-hour gas consumption; bagging line register with batch number, quality-certificate reference, bag count, bagging loss; dispatch register from SAP or plant ERP with dispatch reference, retailer iFMS ID, wholesaler or area distributor intermediate, transport lot; PoS sale-out feed from the e-Urvarak portal; opening and closing stock reconciliation cadence weekly; claim submission cadence weekly with Monday statutory cutoff; Department of Fertilizers claim acknowledgment feed; bank credit reconciliation of released subsidy against claim reference; Section 8 Sl. 8 code 1031 TDS configuration for natural gas purchase from GAIL, Reliance Industries, and Petronet LNG above the Rs 50 lakh threshold; Section 8 Sl. 18 code 1015 TDS on wholesaler and area-distributor commission.
- **Output:** A weekly Cost-Plus claim pack per plant, per retailer, with per-MT concession delta calculation reconciled against the current-quarter notified Concession Rate. A DCS-to-bagging-to-dispatch-to-PoS-sale-out chain view per week with exception flagging on PoS upload lag, biometric authentication fall-back rate, opening stock mismatch, dispatch versus receipt variance, and gas consumption drift above the pre-set energy norm. Bank credit reconciliation of released subsidy against submitted claim reference at plant and week level. A gas cost-of-production reconciliation view feeding the Cost Accounts Branch submission — actual gas invoice from GAIL or Petronet LNG, notified feedstock price, energy consumption from DCS, pre-set energy norm, variance and its cost impact. Consolidated Form 26AS reconciliation feed for Section 194Q payment code 1031 on natural gas purchase and Section 194H payment code 1015 on wholesaler and dealer commission. Audit-ready pack for statutory audit, Cost Accounts Branch verification, and Department of Fertilizers subsidy verification: production, bagging, dispatch, retailer receipt, opening stock, sales, closing stock, claim submitted, claim acknowledged, subsidy credited, gas consumption versus energy norm, exceptions and resolution.

### Godrej Tyson Real Good Chicken Modern Trade Reconciliation

Source: https://www.terra-insight.com/insights/godrej-tyson-real-good-chicken-modern-trade-reconciliation/

- **Problem:** A branded frozen-chicken joint venture between two large parent groups — a 51 percent holder from a domestic agri-business group and a 49 percent holder from a global meat processor — supplies a portfolio of frozen-chicken and value-added meat SKUs to organised modern trade across DMart, Reliance Smart, More Retail, and other national and regional chains through a cold-chain 3PL. The reconciliation surface spans the JV plant's dispatch invoice, the cold-chain 3PL waybill and continuous temperature log, the modern-trade DC's GRN, the Section 34 credit-note trail for temperature deviations and weight shrink beyond the 1.5 percent tolerance band, the Section 15(2) and 15(3) treatment register for promotional and BOGO scheme discounts that qualify or do not qualify as post-supply value reductions, and the Ind AS 24 related-party disclosure required at the JV's own audited financials as well as at each parent's consolidation. Manual reconciliation across these five surfaces routinely mis-classifies a promotional discount as a Section 15(3)(b) qualifying reduction when the underlying agreement post-dates supply, over-issues credit notes on borderline shrink events, and understates the related-party transaction volume in the JV's Ind AS 24 disclosure.
- **Logic:** Build a dispatch invoice register keyed to the JV plant code, the SKU-level GST-inclusive value, the dispatch weight per SKU per pack size, and the modern-trade retailer DC address. Ingest the cold-chain 3PL waybill matched on container number and seal number, and the continuous temperature-log stream (5 to 15 minute interval readings) tagged with excursion events beyond the FSSAI minus 18 degrees C specification. Match the modern-trade DC GRN against the dispatch invoice on the container number and the dispatch invoice reference, compute the delivered-versus-dispatched weight variance per SKU, and split variances into the within-tolerance (up to 1.5 percent absorbed) and above-tolerance (Section 34 credit-note eligible) bands. For temperature-breach events on the 3PL log, generate a compound Section 34 credit-note trail combining 34(1)(a) shrink and 34(1)(c) deficiency components. Maintain a Section 15(2) treatment register that keys every promotional scheme to a Master Trade Terms agreement effective date and validates 15(3)(b) qualification before allowing a post-supply value reduction. At month-end, aggregate the JV's transactions with each parent group and with entities under common control of either parent, and generate the Ind AS 24 related-party disclosure table. Feed the credit-note trail into the JV's GSTR-1 amendment table and export the ITC-reversal document for each modern-trade retailer.
- **Config:** JV plant master with plant code, GSTIN, FSSAI licence number, and dispatch-scale calibration reference; modern-trade retailer master with retailer code, DC-level GSTIN and address, Master Trade Terms agreement effective date, and SKU-level scheme rate table; cold-chain 3PL master with 3PL vendor code, GSTIN, vehicle registration, container number range, and data-logger device serial; SKU master with brand name, HSN, GST rate, standard pack weight, dispatch temperature specification, and weight-shrink tolerance percent (default 1.5 percent, per-retailer override permitted); Master Trade Terms agreement register with effective date, scheme window, SKU coverage, and 15(3)(b) qualification flag; parent-group master with parent entity code, group entities under common control, and Ind AS 24 disclosure category; FSSAI temperature specification (minus 18 degrees C for frozen meat) and excursion-threshold-minutes parameter (typically 15 minutes of continuous excursion triggers deficiency classification).
- **Output:** A month-end four-document modern-trade reconciliation pack: dispatch invoice register by JV plant by SKU by consignment, cold-chain 3PL waybill and temperature-log stream with excursion events flagged, modern-trade DC GRN reconciliation with within-tolerance and above-tolerance weight-shrink split, Section 34 credit-note workbook grouped by 34(1)(a) shrink and 34(1)(c) deficiency and compound events, Section 15(2) and 15(3) treatment register with 15(3)(b) qualification decision keyed to Master Trade Terms agreement date, GSTR-1 credit-note amendment table for the JV, ITC-reversal document per retailer under second proviso to Section 16(2), and — at year-end — the Ind AS 24 related-party disclosure schedule for the JV's own audited financials with transaction volume and outstanding-balance breakdowns for each parent group and each entity under common control of either parent.

### Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing

Source: https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation/

- **Problem:** Goibibo (MMT-owned) and Yatra each issue distinct settlement files on different cadences with different commission ranges and dispute windows — and any property listed on multiple OTAs must reconcile each settlement to PMS folios while keeping inventory parity intact to avoid double-sold rooms and parity-SLA penalties.
- **Logic:** Per OTA, ingest the settlement file at the contract cadence (Goibibo weekly, Yatra fortnightly or monthly), match each booking to a PMS folio, derive room GST at the correct slab, claim 18% ITC on commission GST, log disputes within the contractual window, and cross-check inventory pushes against the channel manager log to identify parity breaches that may carry penalty deductions.
- **Config:** Per-OTA settlement file connectors with cadence calendars; PMS folio adapter; channel manager log connector for parity events; dispute-window timer per contract; commission rate master per OTA per inventory class.
- **Output:** A reconciled multi-OTA revenue ledger with each booking matched to its PMS folio, ITC claimed against each OTA's tax invoice, disputes raised within window, and parity breaches flagged before they become commercial penalties.

### Gold Appraisal Margin and LTV Cap: RBI 75% Ceiling and Margin Drift

Source: https://www.terra-insight.com/insights/gold-appraisal-margin-loan-to-value-nbfc-rbi-cap-india/

- **Problem:** NBFC gold-loan books are capped at 75% LTV under the RBI Master Direction on Loan Against Gold Ornaments, computed on the 30-day average IBJA closing price of 22-carat gold. The cap is measured at booking, but the price is not fixed — a drop in the gold price during the tenure pushes the loan-to-current-value above cap, triggering margin-call obligations and eventual auction under the Fair Practices Code seven-day notice procedure. Four registers — pledge, rate feed, LTV, and margin-call log — must tie daily.
- **Logic:** Compute the daily LTV per open pledge as (principal + accrued interest) divided by (net weight after stone deduction × purity-normalised rate). Apply the trigger band from the margin-call policy — early notice, formal margin call, auction — as configuration rather than code. Log every notice with delivery evidence to preserve the seven-day auction clock. On auction, set the reserve at 85% of the 30-day average IBJA basis, reconcile realisation to dues, and hold the surplus as a mandatory borrower payout under Fair Practices Code.
- **Config:** Purity-normalisation table mapping assay bands (18ct, 20ct, 22ct) to conversion factors against the 22-carat IBJA reference; margin-call trigger bands (typically 80% early, 85% formal, auction threshold) as compliance-team-editable parameters; rate-feed source contract pointing to the 30-day IBJA average, not a real-time spot terminal; notice-delivery evidence store linked to the margin-call log; auction workflow with reserve price computed at 85% of the same IBJA basis; surplus-return payout ledger for borrower obligations.
- **Output:** Daily reconciled LTV register, margin-call issuance and cure log tied to delivery evidence, auction realisation register with reserve-price adherence and surplus-return payouts, Ind AS 109 ECL provision computed with collateral-value LGD cap, and SBR-framework disclosure pack traceable to underlying pledge, rate feed, and margin-call registers without spreadsheet aggregation.

### Gold-Loan NBFC Reconciliation in India: 16 Operational Scenarios

Source: https://www.terra-insight.com/insights/gold-loan-nbfc-reconciliation-india-16-scenarios-cornerstone/

- **Problem:** A gold-loan NBFC operates a high-turnover retail book — average ticket ₹50k to ₹2L, tenure three to twelve months, secured by physical gold ornaments at up to 75% LTV under RBI rules. Sixteen distinct operational scenarios each generate a reconciliation surface: NACH bounce and representation cycles, cash collections, digital collections, LTV re-appraisal, part-payment rollovers, auction surplus refunds, FD-secured combinations, TDS on treasury interest, and priority sector classification. Any single scenario mis-handled produces a wrong DPD bucket, a wrong ECL stage, a wrong 26AS credit, or a Fair Practices Code exception.
- **Logic:** Model each of the sixteen scenarios as a bounded event pattern with its own regulatory anchor. Tag every ledger event with mandate reference, instalment number, category (principal, contractual interest, penal interest, appraisal margin call, auction proceeds, surplus refund), and scenario code. Apply deterministic linkage rules — a NACH return and its subsequent physical collection collapse into a single instalment settlement; a top-up receipt against a margin call links to the original loan; an auction realisation and its surplus refund voucher tie back to the loan closure. The engine encodes each scenario as configuration, not code.
- **Config:** Sixteen scenario-parameter sets covering: mandate return codes and representation windows (NPCI framework), LTV cap 75% and reserve price 85% (RBI Master Direction on Gold Loans), auction seven-day notice and surplus refund obligation (Fair Practices Code), Section 43D interest recognition for NBFCs, Ind AS 109 ECL staging thresholds, Income Tax Act 2025 payment codes 1002/1001/1023/1005/1015, priority sector eligibility criteria for MSME gold loans, and FD-invocation netting rules when a customer FD secures the loan.
- **Output:** Daily gold-loan reconciliation trial balance closing to zero; DPD register aligned to actual collection events; ECL provisioning tied to correctly-staged accounts; auction settlement ledger with surplus refund vouchers per closure; monthly Form 26AS reconciliation of treasury TDS credits; quarterly priority sector classification report for MSME-tagged gold loans; audit-ready evidence pack tying every scenario to its regulatory citation.

### Gold-Loan Tenure Rollover with Part Payment: Interest Recomputation

Source: https://www.terra-insight.com/insights/gold-loan-tenure-rollover-reconciliation-part-payment-nbfc-india/

- **Problem:** A gold-loan borrower pays down a material slice of principal mid-tenure and rolls the residual over to a new maturity. Interest must be recomputed on the reduced balance from the part-payment value date, the NACH mandate must be refreshed to the new EMI and end date, the RBI Fair Practices Code disclosure must be re-issued, and the Ind AS 109 stage-and-ECL treatment must reflect whether the rollover is voluntary or stress-driven. A single reconciliation cycle must tie all four.
- **Logic:** Capture the rollover as an event with a value date, a part-payment amount, a residual principal, a revised tenure, a revised EMI, and a trigger reason (voluntary vs relief). Recompute interest on the residual using the effective interest method with the sanctioned rate. Test the modification for substantial-modification under Ind AS 109 paragraph B5.4.6 to determine derecognition vs modification-with-gain/loss. Cancel the old NACH mandate and register the fresh mandate on the same value date. Emit the revised sanction letter for Fair Practices Code compliance. Move the account through the ECL engine with the trigger-reason flag.
- **Config:** Sanction terms parameter set — contractual rate, rest frequency, part-prepayment charge schedule, minimum rollover principal, maximum rollover tenure per RBI SBR asset class. NACH mandate template with dynamic maximum debit amount and end date. Ind AS 109 substantial-modification test threshold (10% cash-flow change) and stage-transition rules keyed on trigger reason. Fair Practices Code sanction-letter template with mandatory field checklist.
- **Output:** Recomputed EMI schedule and revised amortisation table on the loan account. Fresh NACH mandate accepted by NPCI with amendment cycle closed. Digitally signed revised sanction letter stored to the customer audit trail. Ind AS 109 modification gain or loss booked to P&L, ECL stage retained or transitioned with the trigger-reason flag preserved. A daily rollover-event reconciliation report tying all four sub-ledgers with zero unresolved breaks.

### Gold Scrap Purchase from Unregistered Suppliers: Reverse Charge Section 9(4)

Source: https://www.terra-insight.com/insights/gold-scrap-purchase-unregistered-supplier-rcm-section-9-4-india/

- **Problem:** A walk-in retail customer selling old gold to an Indian jeweller creates a supply from an unregistered person to a registered recipient. Section 9(3) read with Notification 07/2018-Central Tax (Rate) puts the tax liability on the jeweller under reverse charge at 3% on the scrap value. The jeweller must self-generate a tax invoice under Section 31(3)(f), record the RCM output tax in GSTR-3B Table 3.1(d), claim ITC in the same month under Section 16, and — where the transaction value exceeds ₹2 lakh — capture the customer's PAN under Rule 114B and settle through the banking channel under Section 269ST. Retailers who assume the 2018 dilution of Section 9(4) means no RCM applies to walk-in scrap under-pay GST on the entire buyback book and expose themselves to Section 74 assessment. Retailers who correctly apply RCM but mis-classify old-gold-exchange transactions as scrap purchases over-account GST and under-recognise the Section 15(3) discount treatment on the new-jewellery leg.
- **Logic:** Build a two-path classifier at the counter that bifurcates every walk-in gold-inbound event into (a) scrap purchase, no new-jewellery leg — RCM path under Notification 07/2018-CTR at 3% + self-invoice under Section 31(3)(f) + ITC in same month or (b) old-gold exchange against new jewellery — Section 15(3) discount path on the new-jewellery invoice, no RCM, no purchase invoice. On the RCM path, generate the self-invoice with HSN 7112, capture supplier identity per Rule 46, quote PAN where scrap value exceeds ₹2 lakh, and route settlement through banking channel where consideration exceeds ₹2 lakh. Aggregate self-invoices into GSTR-3B Table 3.1(d) as RCM output tax and Table 4A(3) as RCM ITC in the same return period. Reconcile the RCM output liability to the RCM cash payment on the electronic cash ledger and the ITC to the electronic credit ledger. Cross-verify against Form 26AS Part D and the annual purchase register for the audit trail.
- **Config:** Counter workflow with a two-path selector — 'scrap only' triggers RCM invoice generation, 'exchange for new' triggers Section 15(3) discount posting on the new-jewellery invoice; self-invoice series with a distinct prefix (typically RCM/SI/) maintained separately from B2C sales invoice series; walk-in customer master with government-ID capture (Aadhaar / passport / voter ID) plus PAN field with Form-61 declaration flag for above-₹2-lakh transactions without PAN; HSN 7112 for waste and scrap of precious metal with 3% rate flag and RCM-applicable indicator; banking-channel-mandatory flag on consideration above ₹2 lakh under Section 269ST / Section 269SS; assay slip capture per purity (22-carat, 18-carat, 14-carat) with weight and rate applied on the day of receipt.
- **Output:** A monthly RCM inward supply reconciliation pack: self-invoice register with HSN 7112 aggregation to GSTR-3B Table 3.1(d) RCM output tax; matching ITC claim in Table 4A(3) with per-invoice tie-back; Section 269ST / 269SS flag on all above-₹2-lakh transactions with settlement-mode verification (RTGS / NEFT / IMPS / UPI / account transfer); Rule 114B PAN-capture audit report with Form 61 exceptions listed; two-path counter reconciliation showing scrap-purchase versus exchange-discount classification per event with the customer identity and consideration; electronic cash ledger reconciliation showing RCM discharge separately from forward-supply GST discharge; year-end audit trail with self-invoice serial gap analysis and per-customer aggregate value against the ₹2 lakh cash-cap threshold.

### Gold at 3% vs Making Charges at 5%: HSN Classification and Reconciliation

Source: https://www.terra-insight.com/insights/gold-tax-3-percent-hsn-7113-vs-making-charges-5-percent-cbic-notification/

- **Problem:** Indian jewellery retailers face a rate-classification choice on every finished-piece transaction — bundle metal and making into a composite supply taxed at 3% under HSN 7113 per Section 8 CGST, or invoice metal at 3% and making at 5% as two separately-priced supplies. The invoicing choice determines the GSTR-1 rate-wise breakdown, the GSTR-3B tax liability calculation, and the audit-defensibility of the retailer's classification. Hybrid patterns across the year — some invoices bundled, some split, no consistent commercial logic — are the single most common trigger for a Section 61 GST scrutiny notice on the jewellery vertical, and mid-market retailers frequently discover the inconsistency only when the year-end GSTR-9 reconciliation surfaces a rate-mix gap between the P&L revenue split and the GSTR-1 rate-wise report.
- **Logic:** Build a rate-classification decision register keyed by invoice pattern — walk-in composite, workshop bespoke with customer-supplied metal, B2B wholesale with separate metal and making lines, repair or remodelling job-work-only. For each pattern, fix the invoice format (single line versus two lines), the HSN code applied (7113 versus 7113 + 9988), the rate applied (3% composite versus 3% + 5% split), and the GSTR-1 reporting row. Reconcile the outward GST liability at each rate to the invoice register per period. Cross-foot the GSTR-1 rate-wise report to the GSTR-3B outward supply summary and to the general-ledger sales revenue split before every return cycle. Any period-over-period drift in the composite-to-split ratio without a corresponding change in customer mix flags a control failure and is investigated invoice-by-invoice.
- **Config:** Invoice pattern master with pattern code, description, HSN code, rate, and GSTR-1 row mapping; product master with HSN 7113 and default composite treatment; job-work service master with SAC 9988 and Entry 26 rate reference; BIS HUID linkage to the invoice line where hallmarked; store-day gold rate feed for metal-line valuation on bespoke and metal-only invoices; monthly rate-mix drift alert threshold; year-end GSTR-9 reconciliation between P&L revenue split, GSTR-1 rate-wise report, GSTR-3B liability calc, and the composite-versus-split invoice register.
- **Output:** A period-end jewellery GST reconciliation pack showing outward supplies at 3% (composite + metal-only), outward supplies at 5% (making charges + repair), diamond and stone lines at 0.25% where applicable, and other lines (watches, boxes, cases at 18%) — each reconciled to the invoice register and cross-footed to GSTR-1, GSTR-3B, and the trial balance. Rate-mix drift alerts flag periods where the composite-to-split ratio moved without a corresponding customer-mix explanation. The audit trail per invoice — pattern code, HSN, rate, HUID reference where relevant, and the rationale for the composite-or-split treatment — supports Section 15 valuation defence and Section 61 scrutiny response.

### Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds

Source: https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india/

- **Problem:** GRN-side events at an Indian factory — partial deliveries, quality holds, rejections, GRN reversals — create downstream AP exceptions because vendor invoices arrive on a different timeline than the GRN closure process, leaving the three-way match in a perpetually open state.
- **Logic:** Track GRN status across the Stores → Quality → Bonded-Stores flow with five status codes (RECEIVED_PENDING_QC, ACCEPTED, REJECTED, PARTIAL, ON_HOLD); apply a documented matching window per vendor category between GRN creation and invoice receipt; release invoices into the three-way match queue only when GRN status permits; raise a reversal GRN with reference to the original when post-acceptance defects surface.
- **Config:** Per-vendor-category matching window (7-60 days), GRN status code map, quality-hold ageing buckets, GRN reversal series and debit note linkage rule, and Stores-Quality-Bonded handoff document trail.
- **Output:** A GRN register where every line carries a status, an ageing flag, and a link to its matching invoice (or to the awaiting-invoice queue); rejections produce traceable debit notes and outbound delivery challans; quality holds surface on a daily report before they age past the matching window.

### Growth-vs-Base Scheme Reconciliation for FMCG Distributors

Source: https://www.terra-insight.com/insights/growth-vs-base-scheme-fmcg-reconciliation/

- **Problem:** FMCG growth-vs-base distributor schemes pay an incremental discount on the slab of secondary sales that crosses prior-year secondary sales multiplied by a growth factor. The reconciliation has four moving parts that drift apart over the quarter — base-year baseline lock, growth multiplier, monthly cumulative actual, and the Section 15(2) post-supply credit-note treatment — and without a disciplined monthly cycle the brand only learns at quarter-end whether the accrual matches the payout.
- **Logic:** Reconcile base-year secondary sales for each distributor (prior FY, same SKU group, net of returns/damages) against the locked baseline letter, apply the announced growth multiplier to derive the target, pull current-period DMS secondary sales monthly, compute cumulative achievement against the cumulative-target trajectory with seasonality curve, accrue reward provision monthly at the expected achievement band, true up at quarter-end against actual achievement, raise Section 34 credit notes linked invoice-by-invoice for distributors clearing target, tag each credit note with the Section 15(2) post-supply-discount flag, and reconcile distributor ITC reversal acknowledgements under Rule 37.
- **Config:** Distributor master keyed by GSTIN with base-year secondary-sales baseline column, scheme master with growth multiplier and slab-percentage band, DMS feed contract for monthly secondary-sales export by distributor by SKU group, monthly cumulative-achievement reconciliation register, accrual ledger by distributor by scheme period, Section 34 credit-note register with mandatory original-invoice linkage, Section 15(2) post-supply-discount classification flag per credit note, Rule 37 ITC-reversal acknowledgement tracker by distributor by period.
- **Output:** A monthly board-ready dashboard of growth-scheme accrual by distributor cohort, cumulative-achievement-vs-cumulative-target trajectory by region and category, distributor cohort projected to achieve target at quarter-end with expected reward payout, accrual-vs-payout variance for the preceding quarter, ageing of unsettled credit notes by distributor, and a status log of distributor ITC-reversal acknowledgements under Rule 37 ready for GST audit defence.

### GST 2.0 FMCG Rate Rationalisation — Sept 2025 Reconciliation Guide

Source: https://www.terra-insight.com/insights/gst-2-0-fmcg-rate-rationalisation-reconciliation-sept-2025/

- **Problem:** CBIC Notifications 09 to 16/2025-CTR moved soaps, shampoos, toothpaste, biscuits (HSN 1905 unified), chocolates and confectionery, and metal kitchenware to the 5% slab and aerated/sweetened beverages to the 40% NSAB slab effective 22 September 2025. Indian FMCG controllers must reconcile three simultaneous breakages across the transition: (a) in-stock MRP overprint operations on pre-22-September trade pipeline, (b) Rule 42 ITC reversal under CGST Rules on tax-rate-transition stock where input GST was claimed at the old rate but output supply books at the new rate, and (c) scheme credit-note rate switch on retro flows where credit notes issued post-22-September must reconcile to the rate at the time of original supply, not the rate at credit-note issue. The straddle on 22 September — dispatches invoiced on 21 September at old rates against goods received and sold by distributors on 23 September at new rates — propagates through GSTR-2B/3B mismatches that cascade into scheme-accrual reconciliation and Section 73 notice risk.
- **Logic:** Build a per-HSN, per-batch stock register tagged by invoice date of input procurement, dispatch date of output supply, and the rate-effective-date overlay. Each batch resolves to one of three states: pre-transition stock with original MRP under transition-window grace, pre-transition stock with field-overprint sticker, or post-transition stock at new MRP. The Rule 42 apportionment table reads input ITC claimed at the old rate against the proportion of output supply realised at the new rate; the reversal is filed in the September and October 2025 GSTR-3B cycles. The scheme credit-note engine persists rate-effective-date per HSN per scheme and reads the original dispatch rate when generating credit notes, not the prevailing rate at credit-note issue. The GSTR-2B/3B reconciliation matches each invoice carrying the brand's dispatch rate against the distributor's claim at the same rate, flagging straddle invoices for Rule 42 treatment per the apportionment table.
- **Config:** HSN master with old-rate, new-rate, and rate-effective-date 22 September 2025; per-SKU MRP master with pre-transition and post-transition values; batch register with batch code, manufacturing date, dispatch date, distributor GSTIN, and MRP state flag; scheme master with code, percentage, validity dates, Section 15(2) treatment flag, and rate-effective-date overlay; secondary-sales feed from DMS tagged by SKU and batch; Rule 42 apportionment configuration (input ITC basis, output supply basis, reversal rate); GSTR-2B/3B straddle window register (17 September to 31 October 2025) flagging invoices for distributor ITC reconciliation; credit-note generator pulling original dispatch rate from invoice register rather than prevailing HSN master rate; field-overprint kit register tracking distributor-level overprint completion.
- **Output:** A monthly transition reconciliation pack: opening pre-transition stock at old MRP, period overprint completed (with distributor sign-off), period dispatches at new MRP, closing pre-transition pipeline; Rule 42 apportionment table per HSN with input ITC at old rate, output supply at new rate, and reversal amount filed in GSTR-3B; per-batch MRP compliance register surfacing pre-transition stock without overprint sticker for field-team escalation; scheme credit-note pack with rate-effective-date per credit note tied to original invoice rate; GSTR-2B/3B straddle reconciliation surfacing invoices where the brand's dispatch rate and the distributor's ITC claim diverge.

### GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings

Source: https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation/

- **Problem:** GSTR-9 consolidates 12 months of GSTR-1, GSTR-3B, and GSTR-2B data and feeds GSTR-9C three-way reconciliation with audited accounts. Without a monthly reconciliation trail, annual variances in outward supply, ITC claimed, and tax paid become an unreconstructable reconstruction exercise before the 31 December deadline.
- **Logic:** A three-layer annual match aligns outward supply (GSTR-1 tables 4-11 summed against GSTR-9 Tables 4-5), ITC (GSTR-2B annual total against GSTR-3B Table 4A and GSTR-9 Table 6), and tax payment (electronic cash and credit ledger against GSTR-9 Table 9). Matching keys include GSTIN, tax head, and financial year; every variance is tagged as amendment, period-shift, or underreported.
- **Config:** Rolling annual aggregation from Apr-1 to Mar-31, Rule 42/43 true-up using actual annual ratio, GSTR-9C three-way mapping to audited books, and November-return cut-off for last-chance ITC corrections.
- **Output:** Pre-filled GSTR-9 tables with reconciliation commentary, GSTR-9C variance schedule for CA certification (above ₹10 Crore), DRC-03 top-up list for any excess ITC, and audit-ready trail linking every annual figure to source monthly returns.

### GST Compensation Cess on Tobacco and Aerated FMCG Reconciliation

Source: https://www.terra-insight.com/insights/gst-compensation-cess-tobacco-aerated-fmcg-reconciliation/

- **Problem:** Tobacco and aerated-beverage FMCG brands operate a Cess ledger that sits walled off from CGST, SGST, and IGST — cess ITC can only offset cess liability, cess cash can only pay cess, and there is no cross-utilisation. Cigarettes at HSN 2402 attract 28% GST plus a two-part cess (specific rate per 1,000 sticks by length category in the ₹4,170 to ₹4,500 band, plus ad-valorem up to 36% of RSP) that must be computed per invoice, reported in GSTR-1 Table 12 in dedicated cess columns, and reconciled to the electronic Cess ledger. The September 2025 GST 2.0 rewrite moved aerated and sweetened non-alcoholic beverages to a 40% NSAB slab but left tobacco cess untouched, creating a straddle where pre- and post-22-September beverage flows must be reconciled under different architectures on the same GL. Captive consumption for cess-exempt purposes triggers Rule 42/43 reversal separately for the cess leg — routinely mishandled as a CGST-style reversal.
- **Logic:** Build a per-SKU cess master keyed by HSN, length category (for cigarettes), specific rate in ₹ per 1,000 sticks, ad-valorem rate percent on RSP, and effective date range. The invoice engine reads dispatch quantity in thousand sticks (TSC), resolves length category from SKU master, and computes both cess legs — the specific-rate leg (quantity × per-1,000 stick rate) and the ad-valorem leg (invoice value or RSP × ad-valorem percent). Post the combined cess amount to a Cess GL account separate from CGST/SGST/IGST. Trace each invoice line into GSTR-1 Table 12 by HSN and cross-foot the cess column to the Cess GL before filing. For the September 2025 aerated-beverage transition, maintain a pre- versus post-22-September register on the SKU master and let the invoice engine resolve the applicable architecture from the dispatch date. Rule 42/43 cess reversal for captive-exempt flows runs on a parallel ledger to the CGST/SGST reversal.
- **Config:** SKU master with HSN 2402 mapped to length category and specific-rate + ad-valorem cess pair; SKU master for aerated beverages with pre-22-Sept 2025 rate (28% GST + 12% cess) and post-22-Sept 2025 rate (40% NSAB, no separate cess); UQC code TSC (thousand sticks) for cigarette dispatch quantity; Cess GL account distinct from CGST/SGST/IGST; GSTR-1 Table 12 template with cess column populated per HSN grouping; Rule 42/43 cess reversal register for captive-exempt flows; refund route flag for exports under LUT and SEZ supplies; contract-manufacturing TDS master with Section 393(1) Sl. 4 (legacy 194C) code 1001 for Ind/HUF and 1023 for other.
- **Output:** A month-end cess reconciliation pack: opening Cess ITC balance and Cess cash balance; period cess accumulated on inputs (packaging, filter tow, essence, CO2 for aerated); period cess liability on outbound dispatches (specific + ad-valorem for cigarettes; NSAB slab for post-transition beverages); Rule 42/43 reversal for captive-exempt flows; net cess payable or refundable; closing Cess ledger balances reconciled to GSTR-3B cess cells and Table 12 of GSTR-1. Pre- versus post-22-September 2025 aerated-beverage architecture split feeds the transition register. Refund register lists exports under LUT and SEZ supplies with cess refund status.

### Consignment Stock Withdrawal and ERS Invoicing under GST: Auto-Supplier Reconciliation

Source: https://www.terra-insight.com/insights/gst-consignment-stock-withdrawal-ers-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers operating consignment stock under Evaluated Receipt Settlement (ERS) with OEM customers face four overlapping GST timing and reporting risks: the Section 31(7) time-of-supply fixed at withdrawal not at deposit, the Schedule I 6-month deemed-supply trap on un-withdrawn stock, the non-applicability of reverse-charge under Section 9(3)/(4) on registered-to-registered B2B ERS, and the consumption-month GSTR-1 alignment with the OEM's self-invoice. A typical Bajaj-Chakan fastener supplier holding ₹2.8 crore of consignment stock with daily-consumption ERS and weekly self-invoice cycles can carry ₹4.2 lakh of stale-stock Schedule I exposure within 6 months if the consignment-position reconciliation is not run monthly, and a GSTR-1 versus GSTR-2B mismatch of ₹35 to ₹50 lakh per quarter if the consumption-month alignment is not run on a live reconciliation engine.
- **Logic:** On every initial dispatch to consignment, raise a Rule 55 delivery challan only — no Section 31 tax invoice and no GST output; stamp the dispatch with consignment-position counter, OEM warehouse code and 6-month Schedule I clock; load the OEM's daily consumption file into the consignment-position ledger; on receipt of the OEM's weekly ERS self-invoice, validate that the consumption-evidenced quantity matches the self-invoice quantity within tolerance and counter-acknowledge; stage the self-invoice into GSTR-1 prep for the consumption month; reconcile cumulative consignment-position against cumulative dispatches less cumulative self-invoiced consumption at month-end; alert on any stock-line crossing 150 days (Schedule I 30-day pre-alert) and 180 days (Schedule I trigger band); force a withdrawal-or-substitution decision at the 150-day alert.
- **Config:** Consignment-position ledger by part number, OEM warehouse, deposit date and 6-month clock; Rule 55 dispatch challan series for consignment movements separate from production despatch; OEM consumption-file ingestion rule with date, part, quantity and consumption-event reference; ERS self-invoice ingestion with OEM GSTIN, self-invoice number, taxable value and GST; GSTR-1 staging rule mapping ERS self-invoice to consumption-month return; Schedule I alert bands at 150 and 180 days; substitution-or-force-withdrawal workflow for stale stock.
- **Output:** A weekly consignment-position report by OEM warehouse and part number; a monthly ERS self-invoice reconciliation file tying daily consumption to weekly self-invoice quantity; a GSTR-1 prep file for the consumption month with all ERS self-invoices loaded and tax computed; a Schedule I exposure register for un-withdrawn stock approaching the 6-month line; and a year-end audit-defence pack tying consignment dispatches under Rule 55 to consumption-month tax invoices.

### GST 2.0 for Pharma: The 56th Council Drug and Device Reset

Source: https://www.terra-insight.com/insights/gst-council-56-pharma-drugs-medical-devices-5-percent-transition/

- **Problem:** An integrated Indian pharmaceutical company with an API and formulation and medical device portfolio across HSN Chapter 29 headings 2941 and 2933, HSN Chapter 30 headings 3003 and 3004, and HSN Chapter 90 headings 9018 to 9022, plus a small life-saving oncology sub-portfolio, must reconcile the 22 September 2025 GST Council 56 rate pivot across every rate table sitewide — a straddle-invoice window on the cutover, a deepened Rule 89(5) inverted-duty refund cycle post pivot, a new Rule 42 and Rule 43 common-credit reversal exposure on the nil-rated life-saving portion, the continuing permanent block on Chapter 27 mineral-oil solvent ITC under Notification 09/2022-Central Tax (Rate), and a full rewrite of the GSTR-1 and GSTR-3B rate-line tally for every tax period from September 2025 onwards. Manual reconciliation across the cutover window loses the pre-post rate attribution on straddle invoices, over-includes input-services and capital-goods ITC in the Rule 89(5) refund workbook (rejected by Notification 14/2022 and by the Supreme Court in VKC Footsteps), and mis-computes the Rule 42/43 reversal on shared API and packaging inputs — exposing the formulator to Section 73/74 GST demand at year-end audit, to a Section 74 penalty on excess refund claims, and to interest at Section 50 rates on the reversal shortfall.
- **Logic:** Split the sales invoice register and the purchase invoice register on the 22 September 2025 cutover date and apply the pre-pivot rate grid to invoices dated on or before 21 September 2025 and the post-pivot rate grid to invoices dated on or after 22 September 2025, keyed to Section 15 time of supply for goods dispatched pre-cutover and received post-cutover. Extract packaging inputs at 18 percent (HSN 7607 aluminium foil, HSN 3919/3920/3923 polymer film, HSN 4819 corrugated cartons, HSN 4811 laminated foils) and excipient inputs at 12 percent (HSN 3808/2915/2917) from the purchase register into the Rule 89(5) refund workbook, apply the Notification 14/2022 amended formula (Net ITC excludes input services and capital goods), and generate the Form GST RFD-01 filing base monthly. Tag Chapter 27 solvent inputs (hexane, IPA, methanol, toluene, MEK under HSN 2707/2909/2914) as permanently blocked per Notification 09/2022 and exclude from the refund workbook; expense the blocked ITC to the cost of API. Tag the nil-rated life-saving formulation SKU list (oncology, HIV, TB, rare-disease) and compute the Rule 42 reversal monthly on the shared API and packaging pool as (Exempt turnover / Total turnover) × Common credit pool, with the Rule 43 reversal on capital goods over the sixty-month life. Reconcile the tax-period GSTR-3B rate-line tally against the split invoice register and against the refund workbook so the exempt-supply reversal and the inverted-duty refund draw from mutually exclusive slices of the ITC pool.
- **Config:** Product master with SKU code, HSN heading (2941 / 3003 / 3004 / 3005 / 3006 / 9018 to 9022), pre-pivot rate, post-pivot rate, nil-rate life-saving flag (with Council schedule reference), and Rule 42/43 exempt-flag; input master with HSN heading, rate, Notification 09/2022 blocked-flag (for Chapter 15 and Chapter 27), and input-service versus input-goods split for Net ITC eligibility; loan-licensee master (Section 143 CGST + Rule 45 + ITC-04) for job-work manufacturing partners, with input dispatch and finished-goods return timeline; DPCO ceiling-price register from NPPA for scheduled formulations (National List of Essential Medicines) with Para 20 recovery-mechanism trigger; PLI Pharma Rs 15,000 crore claim schedule against DoP portal (Category 1 complex generics, Category 2 APIs/KSMs/DIs, Category 3 IVDs and medical devices) with FY 2019-20 base sales; DSIR-approved R&D facility register for Section 35(2AB) weighted deduction with Form 3CM (approval), Form 3CL (quantum), Form 3CLA (return schedule); Ind AS 38 development-phase capitalisation register for R&D expenditure book-tax reconciliation; e-invoicing threshold flag at Rs 5 crore aggregate turnover; MSME 43B(h) 45-day flag on loan-licensee manufacturers and packaging converters.
- **Output:** A month-end pharmaceutical GST 2.0 reconciliation pack: straddle-window sales and purchase invoice split against the 22 September 2025 cutover with GSTR-1 and GSTR-3B rate-line reconciliation, a Rule 89(5) inverted-duty refund draft under the Notification 14/2022 amended formula with input services and capital goods correctly excluded and Chapter 27 solvent ITC correctly excluded per Notification 09/2022, a Rule 42 and Rule 43 monthly common-credit reversal on the shared API and packaging pool computed against the exempt-supply ratio, the Form GST RFD-01 refund filing base with the accumulated inverted-duty credit for the tax period, the loan-licensee (Section 143 + Rule 45) ITC-04 quarterly return reconciliation for job-work inputs sent and finished goods returned within one year (inputs) and three years (capital goods), and — at year-end — the September following-year Rule 42/43 true-up plus the DSIR Form 3CLA quantum reconciliation for the Section 35(2AB) weighted deduction claim. Cutover audit trail supports the Council FAQ Q10/Q25/Q51 posture for expedited refund processing and the officer-review response for a Section 73/74 demand on the straddle window.

### Reading the 56th Council FAQ: Q10, Q25, Q51 for Pharma Teams

Source: https://www.terra-insight.com/insights/gst-council-faq-q10-q25-q51-pharma-clarifications-reading-guide/

- **Problem:** A Tier-1 Indian pharma formulator with plant sites in Baddi, Ahmedabad-Vadodara, Halol and Bachupally must read the 56th GST Council FAQ published alongside the 3 September 2025 Council press release not as reference commentary but as three compliance instructions — Q10 on the deepened inversion for formulators, Q25 on the medical-device HSN 9018-9022 rate transition, and Q51 on the life-saving drugs nil-rate schedule and Rule 42/43 common-credit reversal exposure. Reading Q10 as a compliance instruction drives an immediate switch from a rolling-quarterly RFD-01 cycle to a strict monthly cycle. Reading Q25 mandates per-SKU MRP recalculation and physical re-labelling before the next taxable invoice under DPCO 2013 Para 20 exposure. Reading Q51 flags the nil-rate Rule 42/43 apportionment obligation on shared inputs — a taxable-versus-nil batch attribution flag on the manufacturing register that must be live before the first nil-rate invoice.
- **Logic:** For each of Q10, Q25 and Q51, prepare a Council FAQ-anchored one-pager for the board and audit committee that captures four fields — FAQ text verbatim, ERP-field change (which master, which flag, which effective date 22 September 2025), reconciliation cadence (weekly for the medical-device MRP recalculation until complete, monthly for the RFD-01 refund cycle and the Rule 42 apportionment, quarterly for the Rule 43 capital-goods amortisation), and exception-escalation path when the reconciliation breaks. Route each one-pager through the tax head, the plant tax coordinators, and the statutory auditor's engagement lead as observer for the first two cycles. Anchor Q10 to the RFD-01 monthly filing discipline under the amended Rule 89(5) formula. Anchor Q25 to the per-SKU MRP recalculation workflow driven by the price-master file with an inventory-on-hand pause during re-labelling. Anchor Q51 to a batch-level taxable-versus-nil attribution flag on the manufacturing register plus a common-input register that separates fully-attributed inputs from shared inputs plus a monthly Rule 42 apportionment run and a Rule 43 amortisation register for capital goods deployed on nil-rate lines.
- **Config:** SKU master with per-SKU HSN code, output GST rate versioned by effective date (pre-cutover rate valid to 21 September 2025 midnight, post-cutover rate from 22 September 2025 zero hour), pre-recalculated MRP and post-recalculated MRP with re-labelling status flag; input master with input HSN, input GST rate, common-versus-attributed flag, and eligible-versus-blocked ITC treatment; manufacturing register with batch number, formulation identity, taxable-versus-nil attribution flag, and shared-input consumption per batch; common-input register with month-of-consumption timestamp for the Rule 42 apportionment; capital-goods register with date of capitalisation, deployment plant, taxable-nil-common flag, and 60-month Rule 43 amortisation schedule; RFD-01 workbook keyed to a monthly filing cadence with input services and capital goods excluded from the Net ITC numerator; NPPA DPCO 2013 register linking each scheduled formulation to the ceiling price and the MRP recalculated for the post-cutover rate; Council FAQ one-pager register with Q10, Q25, Q51 text, ERP-field change, cadence and exception path.
- **Output:** A month-end pharma Council FAQ compliance pack: Q10 one-pager with the RFD-01 filing draft under the amended Rule 89(5) formula and the input-services plus capital-goods exclusion audit trail; Q25 one-pager with the per-SKU MRP recalculation completion status, the re-labelling inventory pause register, and the DPCO 2013 Para 20 exception log where any SKU invoiced at the new rate before re-labelling completed; Q51 one-pager with the Rule 42 monthly apportionment for shared inputs consumed on taxable versus nil-rate batches and the Rule 43 quarterly amortisation for capital goods deployed on nil-rate lines; a scheduled monthly review meeting minute for the first two cycles with the tax head, the plant tax coordinators, and the statutory auditor as observer, downstepped to quarterly cadence from the third cycle. The pack is the single document the board audit committee signs off against at the quarterly meeting and the single document the statutory auditor tests against at year-end.

### GST Credit Note on OEM Price Reduction: Section 34 Timeline and Compliance for Auto Suppliers

Source: https://www.terra-insight.com/insights/gst-credit-note-oem-price-reduction-section-34-auto/

- **Problem:** Indian auto-component suppliers face four recurring triggers for Section 34 credit notes — RMPV downward revisions when the JPC steel index or LME aluminium index drops between dispatch and review, OEM short-pay acceptance for quality and quantity issues, full or partial rejection returns from OEM incoming inspection, and contractual rate revisions after model-year change-over. Each trigger has its own evidence chain, time-of-supply implication, and reporting path through GSTR-1 Table 9B and GSTR-3B Table 3.1(a). Miss the 30 November cutoff of the next FY and the GST output liability stands even after the commercial value reduction has flowed — a permanent leakage of 18% to 28% of the reduction amount.
- **Logic:** Maintain a credit-note candidate queue keyed to the original tax invoice number, populated by four event types — RMPV revision triggers, OEM debit-note acceptances, return-against-rejection slips, and rate-revision letters. For each candidate compute the days-to-deadline against 30 November of the next FY, classify by reason (price reduction / quantity return / value adjustment / rate revision), validate the original invoice is still within Section 34's scope (B2B registered, not export, not blocked by the burden-passed-on proviso), generate the credit-note document and IRN-linked e-invoice credit note, and post the reduction to the supplier's books with the GSTR-1 Table 9B reporting flag.
- **Config:** OEM customer master with vehicle programme codes and GSTIN, original tax invoice ledger with IRN reference and tax breakup, credit-note trigger events from RMPV revision letters, debit-note acceptances, quality return slips and rate-revision letters, Section 34 calendar with 30 November of next FY deadline per source-invoice FY, classification taxonomy for reduction reason (RMPV / quality / quantity / rate / discount), CDNR (Credit/Debit Notes — Registered) JSON export queue for GSTR-1 Table 9B, output-tax adjustment auto-flow to GSTR-3B Table 3.1(a).
- **Output:** A daily Section 34 credit-note action queue ranked by days-to-deadline, the GSTR-1 Table 9B CDNR export file with original-invoice references and reason codes, a lapsed-deadline register flagging credit-note candidates that crossed 30 November of next FY (permanent GST leakage flag), an output-tax reduction view by OEM and reason, and an audit-defensible link from every credit note to its triggering RMPV / debit-note / return event.

### GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal

Source: https://www.terra-insight.com/insights/gst-credit-note-reconciliation/

- **Problem:** A supplier credit note under Section 34 triggers a matching ITC reversal obligation on the buyer in GSTR-3B Table 4(B). Unlinked credit notes in GSTR-2B, timing gaps between supplier GSTR-1 and buyer GSTR-3B, and the September 30 deadline cause systemic under-reversal that surfaces as Section 73 or 74 demand during GSTR-9 reconciliation.
- **Logic:** Three-way matching aligns the physical or email credit note, the negative ITC entry in buyer's GSTR-2B, and the reversal in GSTR-3B Table 4(B) on original invoice number plus supplier GSTIN plus credit note number plus tax period. Unlinked credit notes are matched to source invoices by amount, HSN, and vendor pattern; timing-lag cases are parked for the next-period reversal.
- **Config:** Supplier-side credit-note ingestion from GSTR-2B, unlinked-CN matcher using invoice register lookups, Section 34 deadline tracker (September 30 of following FY), and Table 4(B) reversal routing per tax head.
- **Output:** Reversed ITC schedule per period matching GSTR-2B credit notes, unlinked-CN exception list for supplier follow-up, audit trail ensuring every credit note is reversed within the Section 34 window, and GSTR-9 Table 7 alignment.

### GST on Education Services: Exemption under Notification 12/2017 and Boundary Cases

Source: https://www.terra-insight.com/insights/gst-education-services-exemption-notification-12-2017-india/

- **Problem:** Indian educational institutions and ed-tech platforms must apply the GST exemption under Notification 12/2017-CTR Entry 66 and Entry 67 across multi-stream operations — recognised programs (exempt), coaching (taxable), online education (mixed), hostel and mess (boundary), auxiliary services (transport, catering, examination conduct) — and run Rule 42 / Rule 43 ITC reversal on common inputs proportional to exempt-output share.
- **Logic:** Classify every supply stream under Entry 66 / Entry 67 exemption or as taxable; tag every input by direct attribution (exempt-only / taxable-only / common); for common inputs compute Rule 42 monthly apportionment based on exempt-output share of total turnover; for capital goods apply Rule 43 over 60 months; produce monthly ITC reversal in GSTR-3B and annual reconciliation in GSTR-9; hold contract structure and recognition status as audit evidence.
- **Config:** GST education configuration with supply stream classification (recognised program, coaching, online recognised, online non-recognised, hostel, mess, transport, examination, sponsored research), Entry 66 / 67 exemption rule, Rule 42 monthly apportionment engine, Rule 43 60-month capital goods reversal, GSTR-3B reversal builder, GSTR-9 annual reconciliation, recognition-status evidence vault per program.
- **Output:** A monthly GST close where every supply stream's exemption status is documented, ITC on common inputs is reversed per Rule 42 against the exempt-output share, capital goods reversal flows through Rule 43 across 60 months, GSTR-3B reversal entries are auditable, and the annual reconciliation in GSTR-9 ties to the program-stream recognition evidence file for any CGST audit.

### GST on SaaS Exports: Section 2(6) IGST Compliance and LUT Filing

Source: https://www.terra-insight.com/insights/gst-export-services-saas-india-section-2-6-foreign-exchange/

- **Problem:** Indian SaaS exporters invoicing overseas customers must satisfy all five conditions of Section 2(6) of the IGST Act, file a LUT, e-invoice export supplies, and reconcile FIRCs against invoices within the RBI nine-month window — failure on any limb converts zero-rated supplies into IGST-bearing supplies and locks refund claims for months.
- **Logic:** Verify the five Section 2(6) conditions per invoice, file Form GST RFD-11 at the start of each financial year, generate IRN for each export invoice, and reconcile FIRC realisation against invoice value within the nine-month FEMA window.
- **Config:** Section 2(6) IGST Act five-limb test, Form GST RFD-11 LUT, Section 13 place of supply rules, Rule 48(4) e-invoicing threshold ₹5 crore, FEMA nine-month realisation rule, GSTR-1 Table 6A reporting.
- **Output:** LUT-validated export invoice register, FIRC-to-invoice reconciliation matrix, GSTR-1 Table 6A reconciliation against books, and a nine-month realisation aging report flagging FEMA breaches.

### GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow

Source: https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india/

- **Problem:** Enterprises with 3 to 15+ GSTINs across Indian states face per-GSTIN IMS dashboards with no portal-side consolidation. State teams operating in isolation produce inconsistent decision discipline, miss inter-entity stock-transfer reconciliations, and create audit-trail gaps under Rule 36(4) compliance.
- **Logic:** A consolidated workflow pulls each GSTIN's IMS dashboard, normalises the data into a single decision queue keyed on supplier GSTIN plus invoice number plus buyer GSTIN, applies a common decision engine against a shared purchase master with state-to-GSTIN mapping, identifies inter-entity stock transfers as paired entries, and routes exceptions to the appropriate state or central authority before posting back to the relevant GSTIN dashboard.
- **Config:** Per-GSTIN portal credentials, state-to-GSTIN mapping in purchase master, intercompany invoice identification rules, role-based authority split (central versus state), and per-GSTIN audit-trail capture aligned to Rule 36(4).
- **Output:** Consolidated cross-GSTIN IMS decision queue, per-GSTIN exception report, intercompany stock-transfer reconciliation report, per-GSTIN post-decision GSTR-2B, and group-level audit pack with per-GSTIN breakdown for Rule 36(4) compliance.

### GST Input Tax Credit for SaaS and IT Services: Rule 42/43 and Mixed Use

Source: https://www.terra-insight.com/insights/gst-input-tax-credit-reversal-saas-india/

- **Problem:** Indian SaaS and IT services firms accumulate large ITC pools from cloud infrastructure, software tools, and professional services — but the actual claimable amount is reshaped by Rule 42 mixed-use reversal, Rule 43 capital goods amortisation, Section 17(5) blocked credits, and the GSTR-2B versus books match, often by 10 to 20 per cent of the gross pool.
- **Logic:** Verify Section 16 four-condition eligibility per invoice, segregate common credit for Rule 42 apportionment against exempt turnover, amortise capital goods ITC over 60 months under Rule 43, identify and reverse Section 17(5) blocked credits, and reconcile GSTR-2B against the books purchase register monthly.
- **Config:** Section 16 four-condition test, 180-day supplier payment rule, Rule 42 common credit formula (exempt turnover / total turnover), Rule 43 capital goods 60-month amortisation, Section 17(5) blocked credit list, GSTR-2B matching with books, GSTR-3B Table 4 line classification.
- **Output:** Eligible ITC register tied to invoice, Rule 42 / 43 reversal computation, Section 17(5) blocked credit register, GSTR-2B versus books reconciliation, and the GSTR-3B Table 4 working closing to the net claim.

### GST on Warranty Replacements for Auto Components: Buyer-Seller-OEM Three-Party Treatment

Source: https://www.terra-insight.com/insights/gst-on-warranty-replacements-auto-component-india/

- **Problem:** Indian Tier-1 auto-component suppliers honouring end-customer warranty claims through the three-party Mahindra dealer to Mahindra OEM to Tier-1 chain face a four-document GST flow that CBIC Circular 195/07/2022 governs differently at each leg: the dealer-to-customer leg sits outside GST as a B2C original-sale coverage, the OEM-to-dealer leg is a supplier-borne non-supply under circular paragraph 2, the OEM-to-Tier-1 FOMP back-charge is a non-GST financial flow, and the Tier-1-to-OEM replacement leg is again a supplier-borne non-supply. A Tier-1 processing 1,800 three-party warranty claims per month must run a six-artefact documentation discipline across the chain, tie the FOMP back-charge to the warranty claim ID, preserve input ITC on the warranty production run, and reconcile the four-document flow on every claim — with ₹6 lakh per month of reclassification exposure if any of the artefacts is missed.
- **Logic:** On every warranty claim received from the OEM warranty system, open a unique warranty-claim ID; trigger the production-run pull for the replacement part; raise the Rule 55 delivery challan to the OEM with the warranty-replacement narration and the OEM original-sale-invoice reference; tie the Rule 55 challan to the warranty-claim ID; receive the OEM's FOMP back-charge debit-note against the warranty-claim ID and post the back-charge in the Tier-1's books as either revenue reduction or warranty-cost charge per accounting policy; preserve the input ITC trace on the production run; reconcile the four-document flow at month-end against the OEM warranty system extract; build the six-artefact pack live throughout the year for audit defence.
- **Config:** Warranty-claim ID master keyed by OEM warranty system reference, dealer reference, end-customer reference, failure mode and original sale invoice; Rule 55 delivery challan series for warranty replacements separate from production despatch; FOMP back-charge ingestion rule mapping OEM debit-note to warranty-claim ID; accounting rule for back-charge treatment (revenue reduction versus warranty-cost charge); input-ITC trace rule for warranty production runs; six-artefact reconciliation rule at month-end.
- **Output:** A monthly three-party warranty reconciliation report tying every claim ID to four documents and six artefacts; a FOMP back-charge ledger keyed to warranty-claim ID with OEM debit reconciliation; a Rule 42 ITC-preservation defence file; a year-end GSTR-9 warranty replacement audit pack; and an exception queue for any claim where any of the four documents or six artefacts is missing.

### GST Rate on Auto Components in India: 28% vs 18% vs 5% — Which Rate Applies?

Source: https://www.terra-insight.com/insights/gst-rate-auto-component-india-28-vs-18-vs-5/

- **Problem:** Indian auto-component manufacturers, traders and aftermarket platforms must classify every supply against the correct HSN heading and the correct GST rate — 28% on the residual HSN 8708 parts-and-accessories heading, 18% on specific sub-headings like 8482 (bearings), 8507 (batteries), 8511 (ignition equipment), 8512 (lighting) and 9988 (job-work services), 5% on electric vehicles and EV chargers under HSN 8703 / 8704 — with multi-component invoices (e.g. a brake-system bill mixing a 28%-rated disc rotor, an 18%-rated bearing and an 18%-rated assembly service) requiring line-level classification and the GST Council's notification history (2018 / 2019 / 2021 / 2024 changes) governing which rate applied at which time.
- **Logic:** Walk the HSN heading hierarchy from most-specific to most-general per line item; default residual auto parts to HSN 8708 at 28%; classify bearings to HSN 8482 at 18%; classify electrical sub-systems to their specific headings (8507/8511/8512) at 18%; classify EV completely-built units to HSN 8703 / 8704 at 5%; classify job-work and assembly services to HSN 9988 at 18%; tag each line with the GST Council notification under which the rate flows so cross-period invoices reconcile; flag marketplace supplies for Section 52 TCS at 1% by the ECO.
- **Config:** HSN master per part number with applicable rate and Council notification reference; bill-of-material classification — disc, drum, pad, lining, bearing assembly each separately classified; service-component classification for job-work (HSN 9988); EV-specific master for HSN 8703 / 8704 5% lines; multi-component invoice template with line-level HSN; ECO supplier flag for Section 52 TCS reconciliation; GST Council notification calendar with effective dates.
- **Output:** A clean line-level GST classification on every invoice tying each part number to its HSN, its rate and its source notification; multi-component invoices with mixed rates correctly split; an HSN-wise outward-supply position for GSTR-1; a reconciliation of marketplace Section 52 TCS credit; and audit-defensible classification narratives for any line that could attract a residual versus specific-heading dispute.

### GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)

Source: https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services/

- **Problem:** An Indian hotel paying commission to foreign OTAs such as Booking.com, Agoda, and Expedia must self-discharge GST under reverse charge per Section 9(3) of the CGST Act 2017 and Notification 10/2017-Integrated Tax (Rate). Each settlement carries an OTA commission line in foreign currency, an INR equivalent that must be self-invoiced, an 18 percent IGST liability paid in cash, a GSTR-3B Table 3.1(d) entry, and an ITC claim in the next period — all of which must reconcile back to the OTA's commission invoice and the bank settlement. Manual reconciliation across the OTA invoice, the bank statement, the self-invoice register, and the GSTR-3B filing rarely produces the typed evidence statutory auditors expect.
- **Logic:** Ingest the foreign OTA commission invoice, the bank settlement record, the self-invoice register, and the GSTR-3B Table 3.1(d) line. Apply the GST self-invoice exchange rate to convert foreign-currency commission to INR. Compute 18 percent IGST on the INR value. Match the IGST cash payment against the electronic cash ledger debit. Tag the next-period ITC claim under Section 16. Decompose the OTA settlement variance into OTA_COMMISSION_GROSS, RCM_IGST, TDS_NON_RESIDENT (where applicable), and FOREX_VARIANCE codes so each line is traceable to its statutory source.
- **Config:** GST RCM applicability flag at vendor master level (foreign OTA = yes), self-invoice numbering series, exchange-rate source and rate-date convention (typically the relevant Section 14 of the Customs Act / Rule 34 GST notification), GSTR-3B Table 3.1(d) mapping, and a next-period ITC release rule that posts the ITC line in the month following RCM payment.
- **Output:** A reconciled view that shows each foreign OTA commission line with its INR self-invoice value, its 18 percent IGST cash payment, the matching electronic cash ledger debit, the GSTR-3B Table 3.1(d) entry, the next-period ITC claim, and the forex variance against the bank settlement — all classified into typed codes and ready for statutory audit.

### GST Reverse Charge Mechanism under Sections 9(3) and 9(4): Indian Buyer Playbook

Source: https://www.terra-insight.com/insights/gst-rcm-reverse-charge-section-9-3-9-4-india/

- **Problem:** Indian buyers under-account RCM on notified Section 9(3) categories like GTA, advocates, and director's fees, and real-estate developers miscompute the Section 9(4) 80 percent shortfall, leading to interest, penalty, and ITC denial.
- **Logic:** Two parallel regimes apply. Section 9(3) is a permanent recipient-pays list under Notification 13/2017-CTR. Section 9(4) currently binds real-estate promoters under Notification 7/2019-CTR with an 80 percent registered-procurement threshold and a separate 28 percent cement rule. Both require self-invoice under Rule 46(c), cash payment under Section 49(4), and ITC subject to Section 17(5).
- **Config:** Tag every vendor master with RCM applicability. Run a monthly 9(3) ledger scan across GTA, legal, security, sponsorship, director payouts, and import of services. For real-estate, maintain a project-wise inward register split between registered, unregistered non-cement, and cement, and compute the shortfall against the 80 percent threshold at financial year close.
- **Output:** Monthly RCM cash payable summary, self-invoice register reconciled to GSTR-3B Table 3.1(d), ITC claimed in Table 4(A)(3), and year-end Section 9(4) shortfall reconciliation for real-estate promoters.

### GST Refund for Pharma under Inverted Duty Structure: Rule 89(5) Application

Source: https://www.terra-insight.com/insights/gst-refund-inverted-duty-pharma-rule-89-5-india/

- **Problem:** Indian pharma formulators buy active pharmaceutical ingredients at 18% GST and sell formulations at 12% GST, accumulating unutilised ITC every tax period that must be claimed back under Rule 89(5) CGST Rules in Form GST RFD-01, subject to capital-goods exclusion in Net ITC, post-2022 input-services proportional netting, Section 54 two-year limitation, deficiency-memo RFD-03 risk, and the procurement-route segregation between domestic, import, SEZ and deemed-export APIs that determines whether a given invoice is eligible for the refund pool.
- **Logic:** Compute per tax period: Net ITC on inputs (excluding capital goods and net of proportional input-services share), Turnover of inverted-rated supply of goods at the formulation rate, Adjusted Total Turnover excluding exempt and deemed-export legs, and Tax Payable on inverted-rated supply; apply the Rule 89(5) formula to derive Maximum Refund; reconcile the figure to GSTR-2B input invoice register, GSTR-3B Table 4 ITC availed, and the books Net ITC ledger before locking the RFD-01 statement 1A line items by HSN.
- **Config:** Item master keyed to HSN with input/input-service/capital-goods classification, API GRN tagging by procurement route (domestic / import / SEZ supplier / deemed-export), formulation invoice master with HSN and GST rate, GSTR-2B reconciliation against purchase register monthly, RFD-01 statement template with turnover and Net ITC computation, deficiency-memo (RFD-03) tracker by ARN and rectification deadline, Circular 79/53/2018 and 125/44/2019 procedural checklist.
- **Output:** A per-tax-period inverted-duty refund file showing Net ITC, Adjusted Total Turnover, inverted-rated supply turnover, Maximum Refund per Rule 89(5), ARN of RFD-01 filed, sanction status (acknowledgement RFD-02 → provisional sanction RFD-04 → final order RFD-06 → payment RFD-05), running 2-year limitation runway per period, and the reconciliation between claimed and sanctioned amount with disallowance reason codes.

### GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit

Source: https://www.terra-insight.com/insights/gst-refund-reconciliation/

- **Problem:** A GST refund claim flows through four figures — RFD-01 claimed, RFD-06 sanctioned, provisional 90% released, and final bank credit — and these rarely agree. Delays beyond 60 days trigger 6% interest under Section 56, while exporters face shipping bill plus GSTR-1 plus FIRC mismatches that block automated release.
- **Logic:** Stage-by-stage matching tracks each refund claim from RFD-01 through RFD-06 to bank credit, with keys of ARN plus GSTIN plus refund period plus refund category. Exporter claims cross-check ICEGATE shipping bills against GSTR-1 invoice values and FIRC realisations; inverted-duty claims verify accumulated ITC against Rule 89(5) formula.
- **Config:** Refund-category-specific reconciliation templates (zero-rated with IGST, LUT exports, inverted duty, excess cash ledger, wrong tax head), ICEGATE integration for shipping bill matching, and Section 56 interest accrual tracker post-60 days.
- **Output:** Per-claim RFD-01-to-bank ledger, partial-sanction variance report with appeal timelines, 6% interest calculation for delayed refunds, and FIRC-matched exporter evidence pack for the department.

### GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not

Source: https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability/

- **Problem:** Section 9(5) of the CGST Act, effective for restaurant services from 1 January 2022, makes Zomato or Swiggy liable to pay GST on standalone-restaurant and cloud-kitchen supplies through their platforms — but hotel-restaurants tied to room tariff at or above ₹7,500 are carved out, and a single F&B operator running both types within one GSTIN must report Section 9(5) supplies separately from direct outward supplies without double-paying tax.
- **Logic:** Classify each outlet by Section 9(5) applicability — standalone or cloud kitchen on aggregator (yes), hotel-restaurant above ₹7,500 (no), direct dine-in or takeaway (no) — segregate aggregator supplies into Section 9(5) and non-9(5) buckets, report Section 9(5) supplies in Table 3.1.1 of GSTR-3B as operator-paid, retain ITC blocking on inputs attributable to Section 9(5) supplies, and reconcile aggregator-reported tax against the restaurant's gross revenue in the same period.
- **Config:** Outlet-to-Section-9(5)-applicability mapping; aggregator settlement file parser tagging Section 9(5) supplies vs hotel-restaurant supplies; hotel room tariff threshold flag at ₹7,500 per unit per day; ITC eligibility filter blocking input credit on Section 9(5)-attributable inputs; GSTR-3B Table 3.1.1 population for operator-paid supplies.
- **Output:** A monthly GSTR-3B that correctly reports Section 9(5) supplies as operator-paid in Table 3.1.1, retains direct outward supplies in Table 3.1.a, blocks ITC on Section 9(5)-attributable inputs without contaminating eligible streams, and reconciles aggregator-reported tax against the restaurant's gross revenue without the double-payment error common in mixed-portfolio F&B groups.

### GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit

Source: https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation/

- **Problem:** E-commerce operators (Amazon, Flipkart, Meesho, Swiggy, Zomato) deduct 1% GST TCS under Section 52 before releasing seller payouts — 1% IGST for inter-state and 0.5% CGST plus 0.5% SGST for intra-state. Sellers must reconcile GSTR-8 auto-populated credits in GSTR-2B against marketplace settlement statements to avoid losing claimable TCS credit.
- **Logic:** Per-marketplace matching aligns the operator's GSTR-8 line items with the seller's sales register and the TCS credit in GSTR-2B using invoice number plus order ID plus seller GSTIN plus tax period. Inter-state and intra-state TCS are segregated by place of supply rules; variances are flagged for seller-support escalation before the 10th-of-month GSTR-8 cut-off.
- **Config:** Marketplace-specific ingestion rules for Amazon MTR, Flipkart seller reports, and Meesho payout statements; order-ID mapping between sales register and settlement file; place-of-supply classifier for IGST versus CGST plus SGST.
- **Output:** Reconciled TCS credit schedule per GSTIN aligned to GSTR-2B, claim-against-output-tax plan for GSTR-3B, discrepancy log for seller-support tickets, and Form 26AS Part F cross-check.

### 1mg + PharmEasy + NetMeds: TCS Section 52 Marketplace Reconciliation

Source: https://www.terra-insight.com/insights/gst-tcs-marketplace-pharma-1mg-pharmeasy-netmeds-reconciliation/

- **Problem:** A Tier-1 pharma direct-to-consumer brand operating on the three principal Indian e-pharmacy marketplaces — 1mg (Tata 1mg subsidiary), PharmEasy (API Holdings) and NetMeds (Reliance Retail) — at an illustrative Q2 FY 2026-27 gross D2C sales of the order of Rs 45 crore per platform must reconcile every weekly or bi-weekly platform settlement against Section 52 CGST TCS at 1 percent on net supply value (gross less returns), platform commission at 6 percent, logistics recovery, payment gateway charges at 1.8 percent, and Section 34 credit notes for expired-stock, damaged and wrong-SKU chargebacks — landing at an illustrative net receipt of Rs 36.9 crore against a gross of Rs 45 crore. The reconciliation surface is platform-wise plus week-wise, with the Section 52 TCS credit reflected in the supplier's GSTR-2A / GSTR-2B against the marketplace's monthly Form GSTR-8 filing as the single most important cash-flow reconciliation and the expired-stock reverse-logistics tracker as a distinct cost centre with a Section 34 credit-note window of the month of the physical return.
- **Logic:** Build a per-platform per-week settlement workbook keyed on the marketplace supplier code. Extract the platform's settlement report at ORDER-ID level and reconcile against the supplier's own outward-supply register — matching gross value, platform commission at the contracted per-SKU-category rate, logistics recovery per the published tariff, payment gateway charges at 1.8 percent of the gross, and Section 52 TCS at 1 percent (0.5 percent CGST plus 0.5 percent SGST intra-state or 1 percent IGST inter-state) of the net supply value after netting the same-week or same-month returns. Track the Section 34 credit-note register for expired-stock, damaged-shipment, wrong-SKU and prescription-verification-failure returns and reconcile against the marketplace's subsequent-month GSTR-8 net-of-returns base. Roll the weekly reconciliations into a monthly TCS-and-tax reconciliation against the marketplace's Form GSTR-8 filing visible in GSTR-2A / GSTR-2B by 15th of the following month, and consolidate the aggregate TCS credit across all three platforms in the electronic cash ledger utilisation in GSTR-3B for the settlement month.
- **Config:** Marketplace master with platform (1mg, PharmEasy, NetMeds), supplier code per platform, contracted commission rate per SKU category, contracted logistics tariff, contracted payment gateway rate, TCS collection convention (net-of-returns definition per platform); settlement report ingest per platform per week at ORDER-ID granularity; outward-supply register cross-walk from the pharma supplier's own ERP to the platform ORDER-ID; Section 34 credit-note register with return-reason taxonomy (expired-stock, damaged-shipment, wrong-SKU, prescription-verification-failure); reverse-logistics tracker as a distinct cost centre by therapy area; TCS-credit-in-transit tracker with two-month working-capital ageing; Form GSTR-8 cross-reference from GSTR-2A / GSTR-2B for the marketplace's monthly TCS filing; expired-stock provision by therapy area against actual return rate history.
- **Output:** A weekly per-platform settlement reconciliation pack: order-level gross-to-net reconciliation, commission variance versus contract, logistics variance versus tariff, payment gateway variance versus rate, Section 52 TCS reconciliation with the net-of-returns base transparent. A monthly consolidated TCS-and-tax pack: aggregate TCS credit across all three platforms cross-referenced to the marketplaces' Form GSTR-8 filings in GSTR-2A / GSTR-2B, Section 34 credit-note register reconciled against the reverse-logistics tracker, and the electronic cash ledger utilisation feed into GSTR-3B. A therapy-area expired-stock provision report and a two-month TCS-credit-in-transit working-capital ageing report round out the reconciliation surface for the finance team's monthly close.

### GST Textile Rate Rationalisation — Sept 2025 Impact Reconciliation

Source: https://www.terra-insight.com/insights/gst-textile-rate-rationalisation-sept-2025-impact/

- **Problem:** The 22 September 2025 GST 2.0 rate rationalisation (CBIC Notifications 09-16/2025-CTR) reshaped several FMCG, kitchenware, and household categories but left most textile HSNs unchanged. However, several yarn and accessories categories saw rate revisions requiring SKU-level assessment. Textile principals with broad SKU portfolios — a vertically integrated tier-1 or a branded apparel firm operating 100+ HSN codes — face three distinct reconciliation surfaces: identifying which SKUs saw rate changes; handling straddle invoices under Section 12 time-of-supply rules for the 15 September to 5 October 2025 window; and running the GSTR-1 amendment cycle to correct rate mismatches through the Q2 FY 2026-27 filing. In-stock inventory and MRP overprint operations at branded retail add a Legal Metrology overlay, and the ITC-04 job-work chain must preserve historical rate references against the Section 143 deemed-supply clock.
- **Logic:** Build a SKU-to-HSN master with pre-cut-off rate and post-cut-off rate columns tagged against Notifications 09-16/2025-CTR. Ingest every straddle-window invoice (removal date, invoice date, payment receipt date) and apply the Section 12 earlier-of-invoice-or-payment test at consignment level to determine applicable rate. Reconcile in-stock inventory at 22 September 2025 against the SKU rate-change delta report to identify which SKUs need MRP overprint. Flow rate-correction entries into the GSTR-1 amendment cycle: Table 9A for original invoice amendment; Table 9B for credit note or debit note issued for rate correction. Preserve the ITC-04 dispatch register's historical rate reference for Section 143 deemed-supply calculations. Cross-verify against GSTR-2B for the buyer side to catch upstream supplier rate errors.
- **Config:** Rate-change register keyed to Notifications 09-16/2025-CTR effective 22 September 2025 with HSN-wise pre-cut-off and post-cut-off rate columns; SKU master with HSN code, pre-cut-off rate, post-cut-off rate, rate-change flag, MRP overprint required flag; straddle-window invoice register with removal date, invoice date, payment receipt date, and time-of-supply determination; GSTR-1 amendment cycle configuration with Table 9A original invoice amendment and Table 9B credit/debit note routing; ITC-04 dispatch register with historical rate reference field for Section 143 deemed-supply preservation; Legal Metrology (Packaged Commodities) Rules 2011 overprint procedure flag per SKU per warehouse.
- **Output:** A month-end rate-impact reconciliation pack: SKU portfolio rate-impact summary — total SKUs analysed, SKUs with rate change, SKUs unchanged, SKUs requiring MRP overprint; straddle-window invoice tracker with pre-cut-off vs post-cut-off classification per consignment; GSTR-1 amendment draft for Table 9A and Table 9B rate corrections; ITC-04 dispatch register with historical rate preservation; in-stock inventory at 22 September 2025 per warehouse per store with rate-change flag; store-wise MRP overprint completion tracker under Legal Metrology procedure; GSTR-2B buyer-side cross-check for upstream supplier rate mismatch.

### GST on Auto-Component Tooling under Rule 43: Capital-Goods ITC for Indian Suppliers

Source: https://www.terra-insight.com/insights/gst-tooling-capital-goods-rule-43-auto-component-india/

- **Problem:** Indian auto-component suppliers that capitalise OEM-funded tooling under Section 2(19) of the CGST Act must run a 60-month Rule 43 ITC amortisation schedule on every die, mould and progressive tool — with a monthly common-credit attribution of one-sixtieth of the total ITC, a proportionate reversal for any exempt or zero-rated turnover, an accelerated reversal under Section 18(6) and Rule 44(6) if the tool is sold or transferred mid-life, and a parallel piece-rate amortisation invoicing recovery from the OEM that must reconcile to the supplier's books on both the asset side and the receivable side. A Tier-1 with twenty active capitalised tools at ₹1 crore average value can carry ₹3.6 crore of unamortised ITC at any given time, and the 60-month schedule per tool is impossible to manage on a spreadsheet without compounding audit-time reversal exposure.
- **Logic:** On capitalisation, stamp every tool with date of invoice, total ITC available, 60-month end date, monthly Rule 43 attribution amount and exempt-turnover sensitivity rule; run the monthly schedule by computing (total ITC divided by 60) times (exempt turnover divided by total turnover) as the reversal for that month; track cumulative attribution against cumulative reversal; on any sale or transfer, compute remaining-useful-life ITC versus tax on transaction value and reverse the higher amount; for piece-rate recovery, run a parallel ledger of tooling-cost-recovered-per-part against the original capitalised value and surface the price-protection adjustment when actual lifetime pieces deviate from forecast.
- **Config:** Capital-goods register with tool ID, OEM programme, capitalisation date, ITC amount, 60-month end date and monthly Rule 43 row; Rule 43 reversal calendar with monthly run on the GSTR-3B prep date; exempt-turnover feed from the monthly sales register; piece-rate recovery ledger keyed to part HSN and programme; mid-life disposal workflow with Section 18(6) reversal computation and Table 4(B)(2) prep; reconciliation rule between supplier capital-goods register, GSTR-3B Table 4 and OEM tooling-charge invoice register.
- **Output:** A monthly Rule 43 ITC attribution and reversal entry for each capitalised tool; a board-visible unamortised ITC position by programme; an accelerated reversal pre-fill for any tool sold or transferred mid-life; a piece-rate recovery reconciliation showing tooling-cost-recovered versus capitalised value; and an audit-defence pack tying every Rule 43 row to the capitalised invoice, the 60-month schedule and the exempt-turnover proof.

### GST on Warranty Replacement Supplies for Auto Components: FOC Supply and Schedule I

Source: https://www.terra-insight.com/insights/gst-warranty-replacement-foc-supply-auto-component-india/

- **Problem:** Indian Tier-1 auto-component suppliers honouring warranty obligations to OEMs face an operational and GST-accounting question on every free-of-charge replacement part: is the replacement a fresh supply attracting GST, is the input ITC on the warranty stock reversible under Rule 42, and what documentation defends the position at GST audit. CBIC Circular 195/07/2022 settled the dominant pattern by clarifying that supplier-borne warranty replacements are not fresh supplies and that the input ITC is preserved, but the operational reconciliation still has to classify every replacement at dispatch, run a parallel warranty-claim register tied back to the original sale invoice, and separate warranty-bearing replacements from paid-replacement transactions where GST does apply. On a brake-pad supplier processing 18,000 warranty claims per year against a Mahindra programme with ₹38 lakh of replacement-part value, misclassification on even 5% of claims creates ₹3.4 lakh of GST exposure that surfaces at GSTR-9 reconciliation.
- **Logic:** On every warranty replacement dispatch, classify supplier-borne versus paid-replacement; for supplier-borne, raise a Rule 55 delivery challan with explicit warranty replacement against invoice description and no GST; tie the dispatch to the original sale invoice in a warranty-claim register; preserve the input ITC on the manufacturing run that produced the warranty stock; for paid-replacement, raise a Section 31 tax invoice at the agreed consideration, charge GST at the standard part rate and treat as fresh supply; reconcile the warranty-claim register monthly to the dispatch ledger and to the original sale invoice repository; produce a GSTR-9-ready warranty-replacement audit pack at year-end.
- **Config:** Warranty-classification rule on the dispatch workflow (supplier-borne versus paid-replacement); Rule 55 challan series for warranty replacements separate from production despatch; warranty-claim register keyed by OEM warranty-claim reference, failure-mode code, original-sale-invoice number; original-sale-invoice repository with retrieval by invoice number and date; Rule 42 reversal exclusion rule for inputs traced to warranty-replacement production runs; reconciliation rule between dispatch ledger, warranty-claim register and original-sale-invoice repository.
- **Output:** A monthly warranty-replacement classification report by OEM and programme; a year-end GSTR-9 warranty-replacement audit pack tying every supplier-borne replacement to its original sale invoice and CBIC Circular 195/07/2022; a paid-replacement revenue ledger separate from production revenue; a Rule 42 ITC-preservation defence file; and an exception queue for any dispatch where original-sale-invoice retrieval failed.

### GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?

Source: https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference/

- **Problem:** Since Rule 36(4) was amended in January 2022, only GSTR-2B (the 14th-of-month locked snapshot) controls ITC claims, yet many finance teams still reconcile against the always-updating GSTR-2A. The result is excess ITC claims, 18% interest exposure under Section 50, and scrutiny when suppliers file GSTR-1 after the cut-off.
- **Logic:** Reconciliation runs a three-way match between purchase register, live GSTR-2A, and locked GSTR-2B on invoice number plus supplier GSTIN plus tax period. Invoices in 2A but not 2B are parked as deferred ITC for the next period; invoices in the purchase register but not 2B are routed as supplier follow-up. Each variance is tagged so the claimable ITC pool equals the GSTR-2B amount exactly.
- **Config:** Supplier-watchlist rules flagging habitual late filers, cut-off aligned to the 11th-14th window, and deferral tracking so late-filed invoices roll into the next month's 2B automatically.
- **Output:** A GSTR-2B-aligned claimable ITC schedule, a deferred ITC carry-forward ledger, a chase-list for missing supplier filings, and evidence mapping every Rule 36(4) claim to its source GSTR-2B row.

### GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch

Source: https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation/

- **Problem:** GSTR-1 invoice-level output tax declarations and GSTR-3B summary tax payments frequently diverge because of period-end timing, late amendments via Tables 9A/9B/9C, and estimated 3B filings. Persistent variance triggers ASMT-10 scrutiny, DRC-01 demand notices, and 18% interest under Section 50.
- **Logic:** Multi-pass matching aligns every B2B, B2C, credit note, and amendment row from GSTR-1 against the output tax reported in GSTR-3B Tables 3.1 and 3.2 for the same period. Matching keys are GSTIN plus invoice number plus tax period plus tax head (IGST/CGST/SGST). Variance is classified into short-payment, excess-payment, amendment-lag, and period-shift so each one is remediated through the correct GSTR-1 Table 9 amendment or 3B Table 4 adjustment.
- **Config:** Configurable tolerance bands per tax head (zero for CGST/SGST, ₹1 for rounding), cut-off aligned to the 11th-20th filing window, and variance routing that surfaces short-payment cases before the 20th to avoid interest.
- **Output:** Reconciled output tax position per period with a filed-amendment worksheet, DRC-03 top-up trigger for short payments, and audit-ready evidence pack mapping every GSTR-1 invoice to its GSTR-3B contribution.

### Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024

Source: https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules/

- **Problem:** Finance teams continue to operate GSTR-2B reconciliation under pre-October-2024 assumptions, where GSTR-2B was auto-populated and passive. The October 2024 IMS rules made GSTR-2B the output of an active decision pipeline. Without updating the workflow, ITC claims in GSTR-3B will be systematically misaligned with the IMS-decided GSTR-2B, triggering Rule 36(4) compliance gaps and DRC-01C notices.
- **Logic:** The new GSTR-2B compliance loop has five stages: supplier GSTR-1 filing, IMS dashboard population by the 12th, buyer Accept/Reject/Pending action before the 14th cut-off, GSTR-2B generation on the 14th reflecting IMS state, and continued IMS action until the 20th deadline updating GSTR-2B. Compliance requires automated participation in all five stages with audit-trail capture at each step.
- **Config:** IMS dashboard pull schedule aligned to the 12th-14th window, decision engine fed by purchase-register match logic, 30-day Pending aging threshold with deemed-accept alert, post-decision GSTR-2B re-pull, and reconciliation against accepted-set ITC before GSTR-3B preparation.
- **Output:** Post-decision GSTR-2B aligned with the purchase register, Pending queue with aging timestamps, GSTR-3B Table 4 ITC reconciled to the accepted set, and Rule 36(4) audit pack capturing the decision timestamp for every invoice.

### GSTR-2B ITC Reconciliation Failure Modes: How to Prevent Section 16(4) Permanent Losses

Source: https://www.terra-insight.com/insights/gstr-2b-itc-reconciliation-failure-modes-india/

- **Problem:** GSTR-2B Input Tax Credit reconciliation is the single highest-severity reconciliation function on the Indian finance calendar because Section 16(4) of the CGST Act permanently forfeits any credit not claimed by November 30 of the following financial year, with no rectification, no condonation, and no recovery mechanism. Fourteen failure modes across the twelve-class taxonomy conspire to produce a permanent loss: supplier GSTR-1 non-filing on a March invoice, IMS action defaulted to Accept on a wrongly-issued document, IMS action wrongly Rejected on a legitimate invoice, purchase register gap where an inbound invoice was booked to a sibling GSTIN, missed Rule 37 180-day reversal, missed Rule 37A supplier-non-filing reversal, Section 17(5) blocked ITC wrongly claimed on motor vehicle repair, GSTR-2B pulled before a late GSTR-1 lands, import IGST from Bill of Entry not reconciled, credit note from supplier not tracked into reversal, ITC claimed in the wrong GSTIN of a multi-GSTIN entity, paise-level precision reject, B2C-to-B2B late reclassification, and the Table 4 versus Table 6 reconciliation not being run. A manual detection layer catches most of these below 200 vendors and 3,000 invoices per month — above that threshold the at-risk ITC queue stops being economically maintainable in Excel.
- **Logic:** Design the GSTR-2B stream as a monthly PAN-and-GSTIN-level ITC match with three cadence layers — daily (Bill of Entry ingestion and IMS action queue), weekly (supplier GSTR-1 watch, Rule 37 ageing, credit-note tracker), and monthly (two-way GSTR-2B vs purchase register, Table 4 vs Table 6, Section 17(5) blocked ITC check, multi-GSTIN allocation, DRC-01C mismatch simulation) plus an annual close (Rule 37A September 30 walk, Section 16(4) November 30 lockdown walk, GSTR-9 Table 8 reconciliation). Rate every failure mode against the anchored Severity scale (Section 16(4) permanent loss = 10, Section 200A demand = 9, DRC-01C intimation and CARO 2020 material weakness = 8), the Occurrence scale (frequency in an Indian purchase register), and the Detection scale (how likely the current control catches the failure before the cutoff). Apply Action Priority with Severity-first prioritisation — a Severity-10 row with even Medium Occurrence and Medium Detection is a High Action Priority. Trace every failure to its 6P cause (People, Policy, Process, Portal, Period, Partner).
- **Config:** Purchase register with invoice number, invoice date, supplier GSTIN, supplier PAN, recipient GSTIN, taxable value, IGST/CGST/SGST/Cess split, HSN/SAC code, Section 17(5) blocked-flag column (motor vehicle repair, food and beverages, works contract, personal consumption), payment status and payment date (for Rule 37 ageing), Bill of Entry number and port code (for import IGST); GSTR-2B monthly extract keyed to the same fields; IMS dashboard action log (Accept / Reject / Keep Pending / Default-Accept) by invoice; Rule 37A supplier watchlist derived from GSTR-2B suppliers with GSTR-3B filing status; multi-GSTIN allocation rule set with sibling-GSTIN cross-check; DRC-01C simulation threshold (the Rule 88D percentage and absolute limit for the intimation trigger); Section 17(5) blocked ITC master keyed to HSN/SAC and payment description; supplier master with credit-note tracker.
- **Output:** A month-end GSTR-2B ITC reconciliation pack: two-way GSTR-2B vs purchase register match with match-rate percentage and exception ageing; at-risk ITC queue keyed to earliest applicable deadline (Section 16(4), Rule 37, Rule 37A) with escalation state per invoice; Section 17(5) blocked ITC exclusion report; IMS action log with Default-Accept exception review; import IGST reconciliation against Bill of Entry; credit note tracker with cumulative ITC reversal computed; multi-GSTIN allocation reconciliation with wrong-GSTIN corrections; Table 4 vs Table 6 GSTR-3B walkthrough; DRC-01C intimation risk score for the current period; and — at year-end — the Section 16(4) November 30 lockdown walk and the GSTR-9 Table 8 reconciliation.

### GSTR-2B ITC Reconciliation Runbook: The Five-Day Cycle for Indian Finance Teams

Source: https://www.terra-insight.com/insights/gstr-2b-itc-runbook-days-11-15-india/

- **Problem:** The Days 11 to 15 window of the monthly reconciliation cadence is the highest-severity window in the twenty-day cycle. Section 16(4) of the CGST Act permanently forfeits any input tax credit that is not claimed by the 30th of November following the end of the financial year to which the invoice relates, with no rectification, no condonation, and no refund mechanism. A missed IMS action, an unbooked purchase-register invoice that appears in GSTR-2B, or an at-risk invoice whose supplier has not filed GSTR-1 can each convert into a permanent statutory loss if the runbook is not tight. The Invoice Management System introduced from October 2024 added a fourth axis to what used to be a three-way GSTR-2B reconciliation, and the runbook has to reflect the new shape or the reconciliation collapses back into a scramble on the 20th.
- **Logic:** Sequence the window as a five-day cadence with named owners. Day 11 completes IMS actions on the previous month's inbound before the 14th auto-lock. Day 12 pulls GSTR-2B on the 15th for stability and extracts the purchase register dated to the last day of the month. Day 13 runs the three-way match — purchase register versus GSTR-2B versus IMS action log — and categorises every invoice into one of five mutually exclusive buckets. Day 14 handles Rule 42 and Rule 43 common credit reversals, Rule 37 180-day non-payment reversals, Rule 37A supplier-non-filing reversals, and Section 17(5) blocked ITC. Day 15 hands the signed-off ITC figure to the controller, opens the at-risk queue against the November 30 deadline, and closes the window. The controller signs the ITC figure because Section 16(4) is Severity 10 and no other sign-off can carry the exposure.
- **Config:** One monthly close calendar published on Day 0 with the five-day window scheduled against the recipient's own filing dates. Indirect tax executive as the running owner; tax manager as the reviewer; controller as the sign-off gate. A four-column working paper — purchase register, GSTR-2B, IMS action log, GSTR-3B claim — carried across the five days. A five-bucket categorisation table maintained per invoice on Day 13. A standing at-risk queue keyed to invoice date and supplier GSTIN, refreshed after every GSTR-2B pull and escalated on Tier 1 (30 days), Tier 2 (60 days), and Tier 3 (calculated backward from November 30). A Rule 37 payables aging trigger set at 180 days from invoice date; a Rule 37A supplier GSTR-3B filing tracker set against the 30 September following the financial year. A Section 17(5) block-class register maintained in the ERP against expense heads.
- **Output:** By 5pm on Day 15, the ITC figure that will populate GSTR-3B Table 4 is signed off by the controller, every purchase-register invoice for the closed month has been placed in one of five categorisation buckets with a documented downstream action, the at-risk queue is refreshed with the current month's additions and drops, Rule 42 and 43 common credit reversals are computed and reserved for the Day 18 GSTR-3B assembly, Rule 37 and 37A reversal candidates are flagged in the following month's opening ledger as reclaim candidates once the default is cured, and the Section 17(5) exclusion register is reconciled against the ITC ledger. The window closes with a defensible working paper that traces every rupee of ITC in the Day 15 sign-off back to a bucket-one match or an explicit inclusion rule.

### GSTR-2B vs Purchase Register Reconciliation: Monthly Workflow for Indian Buyers

Source: https://www.terra-insight.com/insights/gstr-2b-vs-purchase-register-reconciliation-india/

- **Problem:** Indian buyers risk losing input tax credit when invoices in their purchase register do not match the GSTR-2B statement generated on the 14th of each month, with credit blocked by Section 16(2)(aa) and time-limited by Section 16(4).
- **Logic:** Download the static 2B on the 14th, match line-by-line to the purchase register on GSTIN plus invoice number plus tax period, categorize gaps into PR-only, 2B-only, and amount-mismatch buckets, action IMS accept/reject/pending, follow up with suppliers for missing invoices, and reconcile claimed ITC into GSTR-3B Table 4 before the 20th.
- **Config:** Match keys: supplier GSTIN, invoice number normalized for case and leading zeros, invoice date within tax period, taxable value and tax amounts within tolerance. IMS actions taken before 14th lock into the 2B. Rule 88D triggers a DRC-01C if 3B Table 4(A)(5) ITC exceeds 2B by more than the prescribed threshold.
- **Output:** A reconciled ITC figure for GSTR-3B Table 4, a supplier follow-up list with quantified rupee exposure, an IMS action log, and an audit trail linking every claimed invoice to its 2B line for the next departmental notice or annual return.

### GSTR-2B Reconciliation for Auto-Component Manufacturers with Job-Work Inputs

Source: https://www.terra-insight.com/insights/gstr-2b-reconciliation-auto-component-job-work-india/

- **Problem:** Auto-component manufacturers receive two structurally different inward streams every month — multi-state raw-material invoices from steel and non-ferrous mills, and conversion-charge invoices from a long tail of job-workers under HSN 9988 — and both must reconcile to the static GSTR-2B locked on the 14th, with each line surfaced through the IMS accept/reject/pending workflow, classified correctly as CGST+SGST or IGST against the place-of-supply rule, tested against Section 16 conditions and Rule 36(4), and cross-tied to the Section 143 challan register and to PO/GRN evidence so that no eligible ITC is dropped, no ineligible ITC is taken, no invoice is left pending past the Section 16(4) outer window, and no audit-time GSTR-3B vs 2B variance opens up under Section 65.
- **Logic:** Pull GSTR-2B JSON on the 15th of every month; split into raw-material (HSN 72/76/39 chapters) and job-work (HSN 9988) buckets; match raw-material lines to PO + GRN within tolerance and to e-invoice IRN; match job-work lines to the principal challan series and to the GRN-back register; auto-classify CGST/SGST vs IGST against billing GSTIN and ship-to plant; flag URP suppliers and RCM purchases for self-invoice; assign IMS action (accept, reject, pending) per line; roll a three-period rolling cross-foot for late-uploaded invoices; surface ineligible lines under Section 17(5); cross-check with ITC-04 challan ledger for the job-work bucket; produce a pre-3B ITC register that ties to the day the recipient files.
- **Config:** Supplier master with GSTIN, PAN, registration status, supplier type (raw-material vs job-worker vs services), HSN band, default place-of-supply; plant master with GSTIN, state and ship-to address; PO and challan registers; IMS action thresholds (auto-accept under a value cap, route exception, route to controller); tolerance bands per HSN; rolling-3-period pending window; Section 17(5) block list; cross-link rule to ITC-04 challan register; supplier-communication template for rejections.
- **Output:** A monthly 2B reconciliation pack: matched, mismatched and missing invoices per supplier; IMS action recommended per line; CGST/SGST/IGST classification; Section 17(5) ineligible-ITC list; rolling-3-period late-upload watchlist; Section 16(4) outer-window aging report; job-work bucket cross-tied to ITC-04 challan register; the pre-3B eligible-ITC register and a supplier-communication queue for rejected and pending invoices.

### GSTR-9 Filing for Auto-Component Manufacturers: Key Reconciliations and Audit Trail

Source: https://www.terra-insight.com/insights/gstr-9-auto-component-manufacturer-key-reconciliation-india/

- **Problem:** Indian Tier-1 auto-component manufacturers filing GSTR-9 face a reconciliation cycle materially more complex than a services firm or a single-product trader: Tables 4 and 5 must reconcile to the e-invoice IRN repository at line granularity across the FY, Table 6 must carry Rule 43 capital-goods one-sixtieth attribution separately from input ITC at sub-classification level, Table 7 must split Rule 42 from Rule 43 from Section 17(5) from Rule 37 reversals, Table 8 must reconcile cumulative ITC against GSTR-2B as on 30 April following FY, and twelve sector-specific reconciliation pivots span the form. A Tier-1 with ₹220 crore turnover that builds the registers retrospectively at year-end will spend six to ten weeks on the GSTR-9 cycle and typically surface ₹15 to ₹35 lakh of audit findings during the build; one that runs the registers live throughout the year files in two to three weeks with the audit-defence pack pre-built.
- **Logic:** Throughout the FY, maintain eight live registers — e-invoice IRN repository, capital-goods Rule 43 schedule, Section 143 ITC-04 open balance, warranty-replacement dispatch ledger, Rule 37 ageing register, GSTR-2B versus books reconciliation, credit-note register against OEM short-pays, and HSN-wise outward summary; at FY close, run the twelve pivot reconciliations between GSTR-9 form lines and the live registers; surface any pivot gap above a configurable threshold for finance-team investigation; build the audit-defence pack of the eight register extracts plus the twelve pivot reconciliation files; file GSTR-9 with the pack ready to surface on any audit query.
- **Config:** Live register configuration during the FY for e-invoice IRN, capital-goods Rule 43, ITC-04 job-work, warranty replacement, Rule 37 ageing, 2B versus books, OEM short-pay credit notes, HSN outward summary; pivot reconciliation rule set tying each GSTR-9 table line to the source register; configurable threshold for surfacing reconciliation gaps; audit-defence pack generation rule at FY close; year-on-year delta tracking on each pivot.
- **Output:** A GSTR-9 prep file with all 12 reconciliation pivots run and any gap surfaced; an audit-defence pack of the eight live registers as on FY close; a year-on-year delta report on each pivot; a controller-visible exception queue for any pivot gap above threshold; and a board-visible GSTR-9 readiness dashboard showing reconciliation status by table line.

### GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B

Source: https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india/

- **Problem:** GSTR-9C forces a three-way comparison between books ITC, GSTR-2B ITC, and GSTR-3B claimed ITC. Any unreconciled difference triggers 18% interest, penalties up to 100%, and potential criminal prosecution.
- **Logic:** Run monthly three-way match: books ITC (Table 12A) vs GSTR-9 ITC (Table 12E) vs GSTR-3B claimed ITC. Surface differences in Table 12F before annual filing. Classify each variance by root cause for Table 13 disclosure.
- **Config:** Turnover threshold: above ₹5 crore requires GSTR-9C. Interest: 18% under Section 50(1). Penalty: Section 122 (₹10,000 or tax evaded). Fraud: Section 74 (100% penalty) and Section 132 (prosecution).
- **Output:** Monthly three-way reconciliation report, Table 12F variance analysis with root causes, Table 13 disclosure draft, and annual GSTR-9C readiness score.

### GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics

Source: https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india/

- **Problem:** Indian steel and manufacturing companies running ₹30-50 crore of annual inbound freight from a long tail of road transporters must determine on every freight invoice whether the transporter is a GTA (issues a Consignment Note) or a goods-transport operator (exempt), whether the GTA has opted for 5% RCM (default) or 12% forward charge (Annexure V declaration), reconcile the LR → e-way bill GSTN entry → Consignment Note → GTA invoice → RCM self-invoice → GSTR-3B 3.1(d) trail, claim ITC under Section 16 in the same month, and handle the small-consignment and agricultural-produce exemptions under Notification 12/2017.
- **Logic:** For every inbound freight invoice, classify the transporter as GTA / non-GTA from the Consignment Note presence; for every GTA invoice check the latest Annexure V forward-charge declaration to determine 5% RCM vs 12% forward charge; for 5% RCM transactions issue an RCM self-invoice under Section 31(3)(f), pay 5% through GSTR-3B 3.1(d) and claim ITC in Table 4(A)(3) the same month; reconcile e-way bill consignor / consignee GSTIN against the freight invoice party; flag exemption-eligible freight (agricultural, food grain, ₹1,500 / ₹750 small-consignment threshold) for separate posting.
- **Config:** Transporter master with GTA / non-GTA classification, latest Annexure V forward-charge declaration date and validity, default 5% RCM flag, exemption category map (agricultural, food grain, small-consignment threshold); RCM self-invoice generator under Section 31(3)(f); GSTR-3B 3.1(d) inward-RCM tracker; same-month Table 4(A)(3) ITC claim trigger; e-way bill GSTIN match rule against freight invoice party.
- **Output:** A monthly GTA RCM close where every Consignment Note ties to an LR, e-way bill, GTA invoice and RCM self-invoice; 5% RCM is computed and posted to GSTR-3B 3.1(d); the matching ITC is claimed in Table 4(A)(3); forward-charge invoices are processed as normal inward supplies; exempt freight is segregated; and the consignor / consignee GSTIN match against e-way bill is enforced before posting.

### BIS Hallmarking Charges and Cost Accounting for Jewellers

Source: https://www.terra-insight.com/insights/hallmarking-bis-charges-cost-accounting-jewellery-india/

- **Problem:** Every gold jewellery piece sold at retail in India must carry a six-digit BIS Hallmark Unique Identification (HUID) mark alongside the BIS logo, purity grade, and AHC identification, compulsory from 16 June 2021 and HUID-mandatory from 1 April 2022. Jewellers submit batches of pieces to Assaying and Hallmarking Centres, receive per-piece HUID manifests, and are billed a per-piece hallmarking fee (a few tens of rupees per piece) at 18% GST as an inward supply of services. The reconciliation surface — AHC invoice against internal batch register against HUID capture in inventory master against per-piece amortisation into SKU cost of goods against Rule 42 ITC treatment — has piece-level granularity: at a mid-sized retail chain running 40,000 to 100,000 pieces a month, a single missed HUID or a single duplicate assay charge is a needle in a haystack that only structured reconciliation surfaces reliably.
- **Logic:** Anchor the reconciliation on the HUID as the primary key. Batch flow: the jeweller's despatch note lists piece descriptions and SKU codes and internal batch reference for the lot sent to the AHC; the AHC returns a piece-level manifest listing HUIDs against piece descriptions and a batch tax invoice at 18% GST; the jeweller's receiving process cross-checks the AHC piece count against the despatch count, imports the HUID manifest into the inventory master keyed by SKU, and books the batch invoice as an inward supply. Cost allocation: the AHC batch fee is divided by the number of pieces in the batch and the per-piece hallmarking cost is capitalised into the SKU work-in-progress or finished-goods inventory value under Ind AS 2. ITC treatment: the 18% GST on the AHC invoice flows into the electronic credit ledger and is available under Section 16, subject to Rule 42 reversal only where the jeweller makes exempt supplies (rare in mainstream retail). Monthly close: the controller runs an AHC-invoice-to-batch-register reconciliation, a HUID-inventory-master reconciliation, and a hallmarking-fee-to-SKU-cost reconciliation, with exceptions routed to a controller review queue.
- **Config:** AHC master: AHC identification code, GSTIN, PAN, address, recognition status, per-piece base fee, expedited-turnaround premium rate. Batch master: internal batch reference, despatch date, piece count, SKU codes covered, karat purity declared, AHC destination, expected turnaround. HUID inventory master: six-digit HUID, SKU code, karat purity reported, piece weight, batch reference, receipt date, per-piece hallmarking cost, capitalised inventory carrying value, sale-invoice reference (nullable until sold). AHC invoice master: invoice number, invoice date, batch reference, piece count billed, base fee amount, premium charges, taxable value, CGST, SGST, GSTIN of AHC, GSTR-2B reflection status. Reconciliation registers: (i) despatch-count to AHC-billing-count variance; (ii) HUID manifest to inventory master ingestion status; (iii) purity declared vs purity reported exception; (iv) ITC availed vs GSTR-2B reflection; (v) SKU-cost amortisation vs finished-goods inventory valuation.
- **Output:** A monthly reconciliation pack: AHC invoice-level exception list (batch count, purity, premium charges, GSTIN mismatch); HUID inventory master completeness report (HUIDs marked and billed vs HUIDs received into inventory); per-piece hallmarking cost allocation to SKU with amortised value and residual variance; Rule 42 reversal working (nil for entirely taxable output, calculated for mixed taxable-exempt); Section 54(3) inverted-duty refund working including hallmarking service in Net ITC numerator; sale-invoice-to-HUID traceability report for pieces sold in the month with cost of goods sold recognised at the per-piece cost including the amortised hallmarking fee; ageing report for pieces hallmarked but not sold within the standard inventory window, feeding into slow-moving-stock provision under Ind AS 2 paragraph 28.

### Hank Yarn vs Cone Yarn Duty Differential Reconciliation for Textile

Source: https://www.terra-insight.com/insights/hank-yarn-cone-yarn-duty-differential-textile-reconciliation/

- **Problem:** A Coimbatore or Erode spinner producing 200 to 300 tons of cotton yarn per month against a variable hank-versus-cone split faces a reconciliation exposure that spans three registers. First, the production output register at the winding department must record the form-of-yarn code (hank versus cone) so that the daily kilogram output ties to the finished-goods store. Second, the sales invoice register must apply the correct GST treatment — bill of supply with Notification 12/2017 exemption reference for hank yarn to registered handloom cooperatives, tax invoice at 5 percent GST for cone yarn to knitting mills, and 5 percent tax invoice for hank yarn to any buyer that is not a registered handloom cooperative. Third, the GSTR-1 filing must correctly bifurcate exempt supplies (Table 8) from taxable HSN-summary supplies (Table 12), and the HSN-wise quantity in kilograms must marry to the winding department output net of waste. A mis-classification at any of these three points invites a Section 73 or Section 74 demand for tax short-paid plus interest, and a systemic pattern of mis-classification invites a full-scope Section 65 audit.
- **Logic:** Anchor the reconciliation on the winding department daily output register keyed by shift, ring-frame lot, yarn count, and form-of-yarn code (HAK versus CON). Ingest the finished-goods store receipt against winding output net of soft waste (fed back to blending). Ingest the sales order register from the CRM keyed by buyer GSTIN and buyer-master classification flag (REGISTERED_HANDLOOM_COOP versus KNITTING_MILL versus POWERLOOM_WEAVER versus OTHER). At invoice issue, cross-check the form-of-yarn code on the dispatch challan against the buyer classification: HAK to REGISTERED_HANDLOOM_COOP triggers bill of supply with Notification 12/2017 exemption; HAK to any other buyer triggers tax invoice at 5 percent; CON to any buyer triggers tax invoice at 5 percent. Feed the invoice register into GSTR-1 Table 8 (exempt) and Table 12 (taxable HSN summary) bifurcation. Reconcile the total kilograms invoiced against the winding output net of waste on a daily basis; investigate any variance greater than 1 percent.
- **Config:** Yarn count master (Ne — 20s, 30s, 40s combed carded, 40s combed hosiery etc.) with HSN mapping (5205 for 85 percent or more cotton; 5206 for less than 85 percent cotton); form-of-yarn master with two codes (HAK for hank; CON for cone) and default GST-treatment lookup; buyer master with GSTIN, PAN, classification flag (REGISTERED_HANDLOOM_COOP / KNITTING_MILL / POWERLOOM_WEAVER / OTHER), 194Q deductor flag (Section 8 Sl. 8 code 1031), and 206C(1H) TCS applicability; Notification 12/2017 exemption serial number configured against the REGISTERED_HANDLOOM_COOP classification with a validity check against the buyer's registration certificate expiry; daily production reconciliation window (winding department output kg versus finished-goods store receipt kg versus sales invoice kg) with 1 percent variance tolerance; GSTR-1 Table 8 and Table 12 mapping keyed by invoice type (bill of supply versus tax invoice); e-invoicing threshold flag (₹5 crore aggregate turnover from 1 August 2023) governing IRN generation on tax invoices.
- **Output:** A daily spinning-mill reconciliation pack: winding department output by shift and form-of-yarn code (HAK versus CON) in kilograms, tied to finished-goods store receipt with soft-waste variance surfaced. Sales invoice register bifurcated by GST treatment — bill of supply for hank exempt supplies, tax invoice at 5 percent for cone taxable supplies, and any hank-taxable exception flagged for controller review. Monthly GSTR-1 draft populated with Table 8 exempt-supply row (hank yarn to handloom cooperatives) and Table 12 HSN summary (5205 and 5206 with quantity in kilograms and taxable value). Buyer-master Section 194Q exposure summary highlighting mills where the year-to-date purchase value has crossed ₹50 lakh and the TDS deduction has commenced. Form 26AS reconciliation feed at the spinner PAN reconciles 194Q deductions from mill buyers against the sales register. Audit-ready pack for the concurrent auditor covers the winding-to-invoice trail, the Notification 12/2017 exemption support for every hank-exempt supply, and the HSN-level quantity tally that the tax officer will read at Section 65 audit.

### Hatsun Agro Arokya Milk Tamil Nadu Reconciliation

Source: https://www.terra-insight.com/insights/hatsun-agro-arokya-milk-tamil-nadu-reconciliation/

- **Problem:** A Tamil Nadu private-sector dairy running the illustrative Hatsun Agro Arokya milk and Arun ice-cream product mix at approximately nine lakh litres per day of village procurement across roughly six lakh contributing farmers and 6,000-plus village collection centres must reconcile a farm-gate register at each village per shift, a village-society sub-ledger, a route-consolidator daily invoice for each tanker route, a chilling-centre inbound tally, a plant intake meter, a rate-card version register tied to the quarterly Tamil Nadu state milk rate notification cycle, and a dual-HSN output split between HSN 0401 branded milk at 5 percent GST and HSN 2105 ice-cream at 18 percent GST. TDS at the route-consolidator invoice level must be deducted under Income-tax Act 2025 Section 8 Sl. 4 code 1001 or code 1002, and Section 8 Sl. 8 code 1031 (successor to Section 194Q) applies at aggregate 0.1 percent on packaging, feed, and consumables purchase from single-vendor accounts that cross Rs 50 lakh in the FY. Spreadsheet-based reconciliation loses fat-SNF grade tags at the pooled-sample level, mis-attributes cold-chain freight between the milk leg and the ice-cream leg, applies stale Rule 42 apportionment ratios, and mis-classifies the code 1001/1002 boundary at borderline village-level agents, leaving the dairy exposed to Section 40(a)(ia) disallowance and ITC misclaim at year-end.
- **Logic:** Ingest the farm-gate register per village per shift with the Lactoscan pooled-sample fat and SNF grade and the rate-card version applied at the shift. Roll up to the village-society sub-ledger per shift. Ingest the route-consolidator daily invoice with village-drop-and-pickup tally and the tanker seal register. Match village-society receipt to route-consolidator invoice by village-code, shift, and litres against the illustrative below-0.5-percent chilling-loss tolerance. Ingest the chilling-centre inbound tally and dispatch tally by tanker seal and match to plant intake against the illustrative below-0.3-percent transit-loss tolerance. Split the plant intake into a fluid-milk retail pool and a value-added-products (ice-cream, curd, paneer, ghee) pool at the intake gate by lot code so that downstream Rule 42 apportionment for common inputs is fed by a physical split rather than a revenue-share estimate. Tag every route-consolidator invoice with the deductee legal form (Individual/HUF for code 1001 at 1 percent, other resident for code 1002 at 2 percent) and cross-check to Form 26AS at deductee PAN before the quarterly Form 26Q. Run a rolling aggregate-year-to-date tally at every industrial-vendor PAN so that Section 8 Sl. 8 code 1031 at 0.1 percent begins from the invoice on which the Rs 50 lakh aggregate crosses. Keep a rate-card version register tied to each Tamil Nadu state milk rate notification date and apply prospectively from the effective shift.
- **Config:** Village master with village-code, panchayat, district, route-code, and pooling society registration if any. Route-consolidator master with GSTIN, PAN, legal form (Individual/HUF for code 1001, or partnership/cooperative/company for code 1002), tanker seal series, and default TDS rate. Fat-SNF rate card by grade band, versioned by refresh date, tied to each Tamil Nadu state milk rate notification event date. Shift calendar for morning and evening pickup twice a day. Physical loss tolerance bands — below 0.5 percent village-to-chilling, below 0.3 percent chilling-to-plant, below 0.2 percent grade-drift on retest. Plant intake lot split rule with the fluid-milk-versus-value-added-products lot-code allocation. Dual-HSN output map with HSN 0401 at 5 percent for pre-packaged branded milk, HSN 2105 at 18 percent for ice-cream, HSN 0403 at 5 percent for pre-packaged curd, HSN 0405 at 12 percent for butter, and HSN 0406 at 12 percent for cheese. Rule 42 apportionment ratio refresh rule — monthly on current-month exempt-versus-taxable revenue mix, year-end reconciliation to actual. Section 8 Sl. 8 code 1031 aggregate-year-to-date monitor at every industrial-vendor PAN. Cold-chain 3PL freight rule with the ice-cream-leg-versus-milk-leg allocation.
- **Output:** A shift-level and day-level procurement reconciliation pack: farm-gate register roll-up per village, village-society sub-ledger to route-consolidator invoice tally, tanker-seal-to-chilling-centre tally, chilling-centre-to-plant-intake tally with fluid-milk-versus-value-added lot split, and end-to-end litre and grade closure per route per shift. Dual-HSN output pack showing HSN 0401 branded-milk outward-supply GST at 5 percent and HSN 2105 ice-cream outward-supply GST at 18 percent, with the Rule 42 ITC apportionment ratio applied on common inputs (packaging, energy, cold-chain, freight, admin) and reconciled monthly to GSTR-3B. TDS deducted at each route-consolidator invoice line, tagged with Section 8 Sl. 4 payment code (1001 or 1002), and cross-checked to Form 26AS at deductee PAN. Section 8 Sl. 8 code 1031 tracker on every industrial-vendor account with the Rs 50 lakh aggregate-year-to-date threshold-crossing event flagged prospectively. Rate-card version register tied to each Tamil Nadu state milk rate notification event date. Monthly procurement close pack signed off by the plant controller and the procurement head before month-end journal posting.

### HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns

Source: https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india/

- **Problem:** HDFC serves three statement channels — NetBanking CSV (truncated at ~100 chars), CMS structured report, and MT940 with /INF/ prefix — and each demands a different parser. Misconfigured /INF/ stripping breaks UTR extraction entirely, while service-charge auto-debits hide 18% GST that is recoverable as ITC.
- **Logic:** Channel-aware parsing routes HDFC CSV, CMS, and MT940 to the correct configuration. NEFT and RTGS narrations are parsed using forward-slash delimiters and /INF/ prefix stripping in :86:. NACH batch credits are matched against the HDFC sponsor-bank batch file to individual mandates. Service-charge auto-debits (format HDFC CHRG [service] [period]) are routed to the bank charges GL with the 18% GST component linked to HDFC's monthly tax invoice.
- **Config:** HDFC /INF/ parser profile, CMS SFTP ingestion, NetBanking CSV fallback with truncation alert, Section 194A TDS auto-reconciliation for interest credits above ₹40,000.
- **Output:** Clean transaction ledger from HDFC statements regardless of channel, NACH mandate-level explosion, bank charges with ITC-eligible GST schedule, and Section 194A TDS credit in Form 26AS alignment.

### Heat Treatment and Plating Job Work Reconciliation: Section 143 Compliance for Auto Suppliers

Source: https://www.terra-insight.com/insights/heat-treatment-plating-job-work-reconciliation-auto-india/

- **Problem:** An Indian auto-component supplier outsources surface treatment (zinc / nickel-chrome / e-coat plating) and heat treatment (carburising, nitriding, induction hardening, normalising) to specialised job-workers and must reconcile per-challan dispatched weight versus returned weight under Rule 55 / Section 143 of the CGST Act, with structural weight loss of 0.5 to 3 percent per process that the contract recognises as in-band, ITC-04 quarterly filing tying outbound challans to receipt-backs and one-year clock, conversion-service GST at 18 percent under HSN 9988 on the job-worker invoice, Section 194C TDS on the conversion payment, and the trivalent-chrome regulatory migration affecting plating-rate contracts.
- **Logic:** Maintain a job-work challan register per Rule 55 challan with original dispatched weight per part per heat lot per job-worker, expected per-process weight-change band, return-clock per Section 143. On receipt-back challan, tie returned weight to dispatched weight within band; out-of-band triggers reconciliation. Run ITC-04 quarterly extract per job-worker per challan. Process the job-worker invoice at conversion rate per HSN 9988 with 18 percent GST, deduct Section 194C TDS per the new payment-code rail, and post to job-work conversion expense. Maintain trivalent-versus-hexavalent chemistry mapping per plating line for rate-application discipline. Surface clock-expiry alerts at six and ten months from dispatch.
- **Config:** Job-worker master with GSTIN, PAN, contracted rate per process per part, weight-change band per process; per-challan register with outbound and inbound legs under Rule 55; ITC-04 export template with quarterly cadence and one-year clock per dispatch; per-process weight-change band master (carburising, nitriding, induction hardening, normalising, zinc plating, nickel-chrome plating, e-coat); chemistry-type flag (trivalent versus hexavalent) per plating line; Section 194C TDS rate matrix under the new payment-code rail; Form 27EQ and Form 26Q export integration.
- **Output:** A challan-level job-work reconciliation register per Rule 55 challan with one-year clock and out-of-band weight-change alerts; quarterly ITC-04 export ready for GST portal upload reconciled to the books; job-worker invoice match against dispatched challan and conversion-rate master; Section 194C TDS deduction with payment-code 26Q lineage; chemistry-type audit trail for plating lines supporting OEM-driven trivalent migration; and a clock-expiry dashboard surfacing dispatches at six and ten months from challan date.

### Heritage Foods Milk Procurement Reconciliation — AP + Telangana

Source: https://www.terra-insight.com/insights/heritage-foods-milk-procurement-ap-telangana-reconciliation/

- **Problem:** A listed AP-headquartered dairy running a village-society milk procurement network across Andhra Pradesh and Telangana at approximately 6 lakh litres per day across 3,400 villages, with farm-gate rates of Rs 38–45 per litre priced on fat and SNF grade, must reconcile a farm-gate register at each village, a village-society sub-ledger, a route-consolidator daily invoice, a chilling-centre inbound tally, and a plant intake meter — five points in the physical chain for the same litres — every twelve hours for morning and evening shifts. TDS at the route-consolidator invoice level must be deducted under Income-tax Act 2025 Section 8 Sl. 4 code 1001 (Individual/HUF contractor, 1 percent) or code 1002 (other resident contractor, 2 percent), and the cooperative bonus distributed back to the village societies at year-end must be GL-split between an operating milk procurement top-up (P&L expense) and a cooperative dividend (below-the-line appropriation). Manual reconciliation over spreadsheets loses fat-SNF grade tags, over-credits the farm-gate register against under-invoiced routes, and mis-classifies TDS payment codes at the borderline case, leaving the dairy exposed to Section 40(a)(ia) disallowance on route-consolidator payments and audit questions on inter-tier bonus GL treatment.
- **Logic:** Ingest the farm-gate register per village per shift with the pooled sample fat-SNF grade and the rate-card applied. Roll up to the village-society sub-ledger for the shift. Ingest the route-consolidator daily invoice with per-village drop-and-pickup tally. Match village-society receipt to route-consolidator invoice by village-code, shift, and litres — expected variance below 0.5 percent for chilling loss. Ingest the chilling-centre inbound tally by route and shift. Match route-consolidator dispatch to chilling-centre inbound by tanker seal number, litres, and temperature-time log. Ingest the plant intake meter by tanker per shift and match to chilling-centre dispatch — expected variance below 0.3 percent for transit loss. Tag every route-consolidator invoice with the deductee legal form (Individual/HUF for code 1001 at 1 percent, other resident for code 1002 at 2 percent) and check TDS deducted against tally at deductee PAN in Form 26AS. Separate the cooperative bonus posting stream into an operating top-up leg (P&L procurement cost) and an appropriation leg (below-the-line dividend) with different TDS treatment and different GL codes.
- **Config:** Village master with village-code, cooperative society registration (AP or Telangana Cooperative Societies Act), Section 80P eligibility flag, and route assignment. Route-consolidator master with GSTIN, PAN, legal form (Individual/HUF for code 1001 or other for code 1002), and default TDS rate. Fat-SNF rate card by grade band — refreshed weekly or fortnightly — with the FSSAI standardised, toned, double-toned, and full-cream fat-SNF floor thresholds preset. Shift calendar for morning and evening pickup twice a day. Physical loss tolerance bands — 0.5 percent village-to-chilling, 0.3 percent chilling-to-plant, 0.2 percent grade-drift on retest. Cooperative bonus posting rules with the operating-top-up-versus-dividend split policy. Section 40(a)(ia) monitor with the tax-audit-year reporting window.
- **Output:** A shift-level and day-level procurement reconciliation pack: farm-gate register roll-up per village, village-society sub-ledger to route-consolidator invoice tally, route-consolidator to chilling-centre tanker tally, chilling-centre to plant intake tally, and end-to-end litre and grade closure per route per shift. TDS deducted at each route-consolidator invoice line, tagged with Section 8 Sl. 4 payment code (1001 or 1002), and cross-checked to Form 26AS at deductee PAN. Cooperative bonus posting draft with the operating top-up and dividend legs separated. Monthly procurement close pack with village-society-wise, route-wise, and product-grade-wise litre and rupee summary — signed off by the plant controller and the procurement head before month-end journal posting.

### Hero MotoCorp Supplier Payment Reconciliation: Splendor and Passion Volume Suppliers

Source: https://www.terra-insight.com/insights/hero-motocorp-supplier-payment-reconciliation/

- **Problem:** Tier-1 suppliers to Hero MotoCorp operate inside a high-volume two-wheeler commercial regime — Dharuhera, Gurgaon, Haridwar, Neemrana, Halol and Chittoor as the six-plant footprint, Splendor and Passion as the volume-driver programmes that anchor most Tier-1 supply chains, aluminium die-cast / plastic / steel / rubber as the dominant material categories, RMPV pass-through on aluminium and copper-content SKUs, per-piece quality back-charges (not per-100-piece) as the dominant quality debit, the typical 30-45 day post-GRN payment cycle, and Section 393(1) Sl. 6(i).D(b) code 1024 TDS on the conversion charge. A ₹150 crore annual Hero book demands plant-coded settlement, programme-level decomposition, RMPV reconciliation and a Tier-2 traceback register.
- **Logic:** Decompose each Hero settlement at the plant-code level (Dharuhera / Gurgaon / Haridwar / Neemrana / Halol / Chittoor), tie each invoice and debit memo to the source two-wheeler programme (Splendor / Passion / Glamour / HF Deluxe / Karizma / Xpulse / Xtreme / Vida EV), classify per-piece quality back-charges against the supplier's OQC record, validate JIT shortage debits against ASN-GRN timing, age each FOMP / warranty claim against the per-programme running account, reconcile RMPV settlements against the contracted LME / benchmark formula, calendar Section 34 GST credit notes per accepted debit, and reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i).D(b) code 1024 against books.
- **Config:** Hero MotoCorp customer master with sub-records per plant code (Dharuhera / Gurgaon / Haridwar / Neemrana / Halol / Chittoor) and per programme, portal export-mapping for daily call-off / ASN / GRN / settlement-statement parsing, debit-note reason taxonomy aligned to Hero Supplier Quality Manual codes with per-piece quality back-charge sub-codes, FOMP / warranty back-charge register per programme, RMPV register per part with LME / benchmark reference and 30-day lag, Form 168 TDS register with Section 393(1) Sl. 6(i).D(b) code 1024 reconciliation, Tier-2 job-work payment register, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-plant, per-programme Hero settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with per-piece quality back-charge attribution, portal-sourced delivery-schedule reconciliation, rolling-PPM dashboard per part against threshold, RMPV variance register showing supplier-computed vs Hero-settled per period, Form 168 TDS register reconciled under Section 393(1) Sl. 6(i).D(b) code 1024, and a Section 34 GST credit-note action queue keyed to approaching cutoff.

### Higher Education Research Grant Reconciliation: DST, ICMR, CSIR for Indian Institutions

Source: https://www.terra-insight.com/insights/higher-education-research-grant-reconciliation-india/

- **Problem:** Indian universities and research institutions must reconcile research grants from DST, ICMR, CSIR, DBT, SERB, ICSSR across 80-200 active projects per year — sanction orders, instalment receipts, head-wise expenditure (manpower, consumables, equipment, contingency, overhead), utilisation certificates in Form GFR 12-A / 12-B under GFR 2017 Rule 238, C&AG audit and unspent balance refund — while ensuring re-appropriation approvals where head budgets are exceeded.
- **Logic:** Maintain a project master keyed by sanction order with budget head allocations; tag every transaction at posting time to project × head; reconcile bank instalment receipts to sanction order; produce head-wise expenditure subledger per project per period; generate statement of expenditure and utilisation certificate in Form GFR 12-A / 12-B; on closure compute unspent balance and produce refund evidence or re-appropriation approval.
- **Config:** Research grant configuration with agency master (DST, ICMR, CSIR, DBT, SERB, ICSSR, UGC, others), sanction-order register with head-wise budget per project, project bank account mapping, transaction tagging at posting (project × head), SERB fellowship rate master for JRF/SRF/RA, overhead institutional charge percentage by scheme, GFR 12-A / 12-B utilisation certificate generator, unspent balance refund workflow.
- **Output:** A project-by-project close where every sanctioned head reconciles to actual expenditure, every instalment receipt traces to sanction order, every utilisation certificate ties to bank statement, asset register and payroll, every closed project produces unspent balance refund evidence or re-appropriation approval, and the C&AG audit file produces head-wise traceability under GFR 2017 Rule 238.

### Home Loan Interest and Buyer TDS: Section 194A Handling in Real Estate

Source: https://www.terra-insight.com/insights/home-loan-interest-tds-real-estate-buyer-recovery-india/

- **Problem:** An Indian real estate developer running large construction finance loans across a mix of scheduled commercial banks, housing finance companies, NBFCs, and inter-corporate lenders must apply Section 393(1) Sl. 12 code 1002 (legacy Section 194A) 10% TDS on interest paid to non-exempted lenders while correctly applying the Section 194A(3)(iii)(a) banking-company exemption to the majority of the interest cost — and simultaneously not confuse this with buyer-side home loan interest (buyer's own Section 24(b) matter) or buyer-side property purchase TDS (Section 393(1) Sl. 3(i) code 1010, formerly 194-IA).
- **Logic:** Maintain a deductee exemption master keyed by lender PAN tagging each lender as banking-company-exempted or non-exempted; reconcile every interest debit from the bank statement to the deductee master; auto-flag interest paid to non-exempted lenders above the ₹5,000 annual threshold as a mandatory 10% TDS trigger; reconcile Form 26Q quarterly filing to the interest register and the general ledger interest expense filtered on non-exempted payees; keep the buyer-side sale consideration TDS (code 1010) and buyer-side home loan interest (Section 24(b), buyer's ITR) entirely separate from the developer's outbound interest TDS ledger.
- **Config:** Lender master with PAN, lender type (scheduled commercial bank / co-op bank / PFI / NBFC / private / foreign / inter-corporate), Section 194A(3)(iii)(a) exemption flag; interest register with lender ID, sanction reference, disbursement schedule, coupon rate, interest accrual date, interest payment date, gross interest, TDS deducted; deductee exemption flag refreshed against RBI scheduled bank list and Section 4A PFI notification; Form 26Q line register with challan CIN, deductee PAN, section code 1002, amount, TDS rate, TDS amount; bank statement ingestion with counterparty matching to lender master; separate buyer-side sale consideration ledger and Section 26QB (code 1010) filing trail.
- **Output:** A monthly interest-outflow report per lender showing gross interest paid, exemption status, TDS deducted, and challan reference; a quarter-end Form 26Q pre-filing pack with line-level match to the interest register and reconciled variance against the general ledger interest expense; a same-working-day exception queue for any interest debit to a non-exempted lender above ₹5,000 that has not yet been posted with TDS; a compliance dashboard confirming that buyer-side home loan disbursements landing in the escrow account have been correctly booked as sale consideration with code-1010 TDS reconciliation, not confused with developer-side interest TDS.

### Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India

Source: https://www.terra-insight.com/insights/hospital-billing-reconciliation-india/

- **Problem:** Hospital revenue spans OPD cash, UPI, POS terminals, IPD advances, and insurance co-pays across multiple departments, creating fragmented bank entries that don't match any single patient bill.
- **Logic:** Aggregate POS terminal settlements by department, match UPI collections via UTR, track advance deposit lifecycle from receipt through consumption to refund, reconcile against daily bank statement.
- **Config:** GST 18% on room rent above ₹5,000/day, UPI settlement T+1, POS batch settlement timing, advance deposit aging thresholds.
- **Output:** Department-wise revenue reconciliation, advance deposit lifecycle report, unmatched cash deposit register, GST liability calculation on room rent.

### Hospital Chain Multi-Location Revenue Reconciliation: A CFO Guide for Indian Healthcare

Source: https://www.terra-insight.com/insights/hospital-chain-multi-location-reconciliation-india/

- **Problem:** A 14-unit hospital chain consolidating IPD, OPD, pharmacy, diagnostics, and consultation revenue from HIS feeds into a central SAP or Oracle GL routinely sees unit-level variance from inter-unit transfers, doctor revenue share, cash collection leakage, and pharmacy module reconciliation gaps.
- **Logic:** Ingest unit-level HIS feeds, normalise into a common service-line taxonomy, map to GL accounts, reconcile against bank deposits and TPA settlements, and disaggregate variance by unit, service line, and collection mode for central finance review.
- **Config:** 14 unit feeds, five service lines, two collection modes (cash and digital), TDS payment code 1027 for professional fees (Sl. 6(iii).D(b)) under the 2026 migration, GST exemption mapping under Notification 12/2017 for healthcare services with pharmacy carve-out at 5%/12%/18%.
- **Output:** Consolidated revenue by unit and service line, inter-unit transfer netting register, doctor consultation TDS register by payment code 1027, pharmacy GST carve-out for the GSTR-1 return, variance drill-down from chain total to unit collection mode.

### Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India

Source: https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india/

- **Problem:** Indian hospitals deal with 5-15 insurance companies simultaneously, each with different rate cards, preauth processes, settlement cycles, and file formats, making consolidated revenue tracking a multi-payer matching challenge.
- **Logic:** Normalize settlement data across insurer formats, match each claim to patient episode and billing record, aggregate by payer type, identify underpaid and rejected claims for follow-up.
- **Config:** 5-15 insurer integrations, IRDAI 30-day settlement mandate, TDS 10% under Section 194J on corporate health, per-insurer rate cards and co-pay structures.
- **Output:** Payer-wise settlement dashboard, rejected claim resubmission queue, underpayment recovery tracker, and consolidated revenue reconciliation across all insurers.

### Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B

Source: https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india/

- **Problem:** An Indian hotel's corporate AR portfolio runs across 30 to 200 contracted accounts with 30, 60, and 90-day credit terms, mixed Local Rate Agreement and Negotiated Rate contracts, monthly statement-of-account billing, a 30-day dispute window per invoice, partial payment allocations across folios, conditional TDS treatment under Section 393(1) Sl. 2(ii).D(b) for long-stay rent versus no TDS for routine travel, and a strict GSTIN-vs-GSTIN match requirement against each corporate's GSTR-2B view. Manual reconciliation across the PMS folio register, the AR sub-ledger, the GSTR-1 outward register, and corporate remittance advices cannot reliably hold the four-way tie at month-end.
- **Logic:** Ingest BTC vouchers tagged with corporate account number and contract code (LRA or NDC) from the PMS, generate the consolidated monthly invoice per corporate at the contracted rate, post to AR with a 30-day dispute window flag, ingest corporate remittance advices and bank NEFT credits, allocate cash against open folios with explicit partial-payment handling, classify each account as rent-treated (TDS payment code 1009 under Section 393(1) Sl. 2(ii).D(b)) or routine business travel (no TDS), and run a GSTIN-vs-GSTIN match between the hotel's GSTR-1 outward register and the corporate's GSTR-2B for each invoice line.
- **Config:** Corporate master with GSTIN, contract code (LRA/NDC), credit terms (30/60/90/120 days), dispute window length, TDS treatment flag (rent under Section 393(1) Sl. 2(ii).D(b) versus routine travel), invoice cycle date, and statement-of-account format. Ageing buckets at 30/60/90/120+ days from invoice date. GSTR-1-to-GSTR-2B match tolerance on taxable value and tax period.
- **Output:** A reconciled corporate AR view that shows each BTC folio against its monthly invoice, the consolidated statement-of-account, the corporate's remittance advice, the bank NEFT credit, the typed TDS treatment, the GSTR-1 outward line, and the corporate's GSTR-2B match status — with ageing buckets refreshed daily, the dispute queue clearly separated, and Form 26AS reconciliation evidence ready for quarterly close.

### Hotel Deposit, Refund, and No-Show Reconciliation in India

Source: https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india/

- **Problem:** Indian hotels mix refundable security deposits, advances against room charges, no-show charges, and OTA virtual-card pre-authorisations in the same PMS deposit ledger, each carrying a different revenue trigger and a different GST timing under Section 13 of the CGST Act. Without typed tracking, the deposit ledger drifts, refund flows cross GST return periods uncleared, and CARO 2020 audit reviewers find stale liabilities and weak ageing on the deposit-payable balance.
- **Logic:** Track each receipt by type — REFUNDABLE_SECURITY_DEPOSIT (no GST on receipt, balance-sheet liability), DEPOSIT_AGAINST_ROOM_CHARGES (GST on receipt under Section 13, revenue at check-in), NO_SHOW_CHARGE (taxable supply at room-tariff slab), OTA_VIRTUAL_CARD_PREAUTH (timing depends on charge versus pre-auth-only). Reconcile PMS deposit ledger to accounting AR and AP, age every open balance, and emit refund vouchers and credit notes for cancellation flows that cross GST periods.
- **Config:** PMS adapter exposing deposit-type classification, separate ledger accounts in the accounting system for each deposit class, GST advance-adjustment logic per Section 13 CGST, cancellation policy rules per booking source, OTA virtual-card pre-auth-versus-charge feed, ageing thresholds for deposit-payable balances, and refund-voucher generation tied to GSTR-1 advance-and-adjustment table.
- **Output:** A typed deposit ledger with no class-confusion between security deposits and advances, a clean GSTR-1 advance-and-adjustment line every period, no-show charges raising tax invoices at the right slab, refund flows reconciled to bank debits and to credit notes, and a deposit-payable ageing report that satisfies CARO 2020 on long-outstanding balances.

### Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits

Source: https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation/

- **Problem:** Hotel finance teams must reconcile every F&B charge to a folio against its source restaurant POS chit, apply the correct GST split (room rate on room nights vs restaurant rate on F&B), capture late-posted minibar before period close, segregate banquet F&B from à la carte, and treat service charge per the July 2022 CCPA guidelines — with leakage at any layer driving revenue and tax misstatement.
- **Logic:** Match each PMS folio F&B line to its source POS chit by chit reference, room number, and amount. Apply restaurant GST rate (5% no-ITC or 18% with ITC depending on hotel-level room slab) to F&B lines, distinct from the room rate (12% or 18%). Track MINIBAR_LATE_POST as a named variance with housekeeping cut-off discipline. Route banquet F&B through the BEO sub-ledger, not the restaurant POS. Hold service charge in an opt-in tip-pool ledger compliant with CCPA.
- **Config:** Restaurant POS adapter pulling chit-level data with room number, item, and tax; PMS folio connector; minibar housekeeping feed with cut-off rules; banquet BEO sub-ledger; service-charge tip-pool ledger with opt-in flag; GST rate engine keyed to hotel-level room slab and chit type.
- **Output:** A folio-level F&B reconciliation showing every room-charge line matched to its POS chit, a clean GST split between room rate and restaurant rate at folio close, a MINIBAR_LATE_POST exception list with aging, a banquet F&B view separated from à la carte, and a CCPA-compliant service-charge ledger with disclosed opt-in capture.

### Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India

Source: https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct/

- **Problem:** A single hotel folio in India can carry four GST rates — 12% or 18% on the room, 5% no-ITC or 18% with-ITC on the in-house restaurant depending on the hotel's room slab, and 18% on banquet, laundry, and other services — but most PMS exports flatten these into a single tax line, breaking GSTR-1 line splits and creating place-of-supply and rate-mismatch exposure.
- **Logic:** Classify each folio line by HSN/SAC and apply the correct rate at line level: room rate by realised tariff (below ₹7,500 = 12%, at or above = 18%), restaurant by hotel-level published room rate (any room at or above ₹7,500 = 18% with ITC, else 5% no-ITC), banquet and ancillaries at 18%. Reconcile PMS folio totals against POS and banquet sub-systems by rate stream, then consolidate to GSTR-1 with one line per rate.
- **Config:** PMS connector pulling folio lines with HSN/SAC tags; restaurant POS adapter; banquet sub-ledger; rate-classification rules keyed to room transaction value and hotel-level published tariff; GSTR-1 line splitter that emits one row per rate stream per folio.
- **Output:** A folio-level reconciliation showing each rate stream matching its source PMS or POS line, a rate-stream summary feeding GSTR-1 Table 4/5/7 with separate lines for 5%, 12%, and 18% supplies, and an audit trail mapping every output tax rupee back to the originating folio.

### Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj

Source: https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india/

- **Problem:** Indian hotels operating under chain loyalty programs — Marriott Bonvoy, Hilton Honors, IHG One Rewards, ITC Hotels Green Points, Taj InnerCircle, Lemon Tree Smiles, OYO Wizard — accrue a deferred-revenue liability on every paid stay, recognise points-revenue on every redemption stay, carry chain-level inter-property transfers, must estimate breakage under Ind AS 115, and have to apply GST correctly across zero-consideration redemptions and chain-reimbursed redemptions. A property's PMS-level view rarely ties to the chain's central liability ledger without bridging three timing-and-allocation differences.
- **Logic:** Ingest each stay folio with member ID, status tier, accrual rate, points awarded, and points-paid versus cash-paid split. For paid stays, allocate transaction price between the room and the points (a separate Ind AS 115 performance obligation), park the points-allocated portion as deferred revenue. For redemption stays, mark as zero-consideration, partial-redemption, or chain-reimbursed and apply the appropriate revenue and GST treatment. Pull the chain's central loyalty ledger extract, reconcile the property's accruals and redemptions line by line against the central postings, classify variances into typed codes (timing, inter-property transfer, promotional rate, breakage true-up). Apply a quarterly breakage-rate true-up against rolling redemption history.
- **Config:** Loyalty program master per chain (Bonvoy, Honors, IHG, ITC, Taj, Lemon Tree, OYO Wizard) with accrual rate per status tier, points-to-rupee conversion at redemption, expiry rules, breakage rate per tier (rolling 24-36 month basis), GST treatment matrix (zero-consideration, partial-redemption, chain-reimbursed), inter-property transfer rules, and chain-ledger extract format and cadence.
- **Output:** A reconciled loyalty view per property that ties each PMS folio's accrual and redemption to the chain's central loyalty ledger, holds the deferred-revenue liability movement on the property's books with the breakage true-up posted quarterly, classifies every redemption stay's GST posture, and produces audit-grade evidence for Ind AS 115 application — with the property's loyalty position closed within hours of month-end instead of the days a manual reconciliation typically requires.

### Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline

Source: https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation/

- **Problem:** Indian hotels close the PMS day every 24 hours through a night-audit routine that has to roll three shifts forward, post room and tax, close F&B and banquet sub-systems, settle minibar and no-show, square the cash float, and bridge to the bank deposit slip plus card terminal batch plus UPI settlement — all before the system date rolls and the prior day locks. Manual checklist execution leaves five recurring exception classes uncleared, which compound into month-end variances accounting cannot reconcile.
- **Logic:** Run the close in a fixed sequence — PMS day-close (room and tax), F&B daily-Z per outlet, banquet daily settlement against event register, minibar postings, no-show charges, pending arrivals and departures, float verification — then bridge gross PMS revenue to the bank deposit slip, the credit-card terminal batch (net of MDR and GST on MDR), and the UPI or QR daily settlement. Classify residual gaps as cash short or over, unposted F&B charge, MINIBAR_LATE_POST, settled-but-uncharged, or partial folio.
- **Config:** PMS adapter for Opera or IDS Next or eZee or Hotelogix exposing the day-close sequence and exception list, F&B POS connectors emitting daily-Z totals, banquet event register feed, housekeeping minibar feed, front-desk cash float reconciliation, card terminal batch importer, UPI or QR settlement importer, and a property-level cut-off time that controls the operating day boundary.
- **Output:** A closed PMS day with the system date rolled, every exception class typed and routed for follow-up, a cash-and-card-and-UPI bridge that ties gross PMS revenue to net bank credits across the relevant settlement days, and an opening balance carried forward cleanly so that the next day's audit starts from a reconciled position.

### Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement

Source: https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation/

- **Problem:** Virtual credit card bookings from Booking.com, Agoda, and Expedia create a three-date settlement chain — booking date when the VCC is issued, charge date when the hotel swipes it at check-in, and bank credit date when the acquiring bank settles — with no OTA wire transfer to anchor the reconciliation, leaving hotels unable to confirm which bookings have actually settled.
- **Logic:** Run a three-way match between OTA extranet booking export (booking ID, VCC reference, face value, commission), acquiring bank settlement file (charge date, amount, batch reference, card mask), and PMS folio (reservation, nights, taxes). Match on OTA booking ID to PMS reservation, then on PMS reservation to acquiring bank charge through card mask and amount. Flag VCCs not yet charged, charges without a matched VCC, and amount variances.
- **Config:** OTA extranet adapters for Booking.com, Agoda, Expedia VCC exports; acquiring bank settlement file ingest (HDFC, Axis, ICICI merchant statements); PMS connector for reservation and folio data; rules for activation-window timing and charge-eligibility dates; variance handlers for partial charges, late charges, and reissued VCCs.
- **Output:** A daily VCC reconciliation showing each booking matched to its PMS reservation and acquiring bank charge, an exception list for unactivated or uncharged VCCs, a commission-leakage view comparing VCC face value to PMS folio after commission, and a ledger entry stream booking VCC revenue net of MDR and commission.

### Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger

Source: https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation/

- **Problem:** Hotel revenue flows through OTA to channel manager to PMS to ledger to bank, with each interface having distinct data formats — Opera, IDS Next, eZee, Hotelogix on the PMS side; SiteMinder, STAAH, RateGain on the channel side; multiple OTAs with different settlement file shapes — making end-to-end folio-to-ledger reconciliation a multi-system matching problem rather than a single system query.
- **Logic:** Build a chain index keyed on the OTA reference number plus the PMS folio number. Per booking, capture five events: OTA confirmation, channel manager push, PMS folio creation, PMS folio closure with final amount, and OTA settlement. Match each pair adjacently — confirmation to push, push to folio, folio to settlement, settlement to bank. Surface breakpoints at each interface as exceptions for finance team review.
- **Config:** PMS connectors for Opera, IDS Next, eZee, Hotelogix; channel manager log connectors for SiteMinder, STAAH, RateGain; OTA settlement file adapters; bank statement parser; folio-number plus OTA-reference-number composite key; exception handler per interface breakpoint type.
- **Output:** A folio-level audit trail per booking spanning OTA confirmation, channel push, PMS folio, settlement, and bank credit — with breakpoints flagged by interface type for finance team resolution and an end-to-end revenue ledger that ties to bank receipts.

### Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split

Source: https://www.terra-insight.com/insights/hotel-reconciliation-india/

- **Problem:** An Indian hotel runs five concurrent revenue streams — direct guest payments, OTA bookings across MakeMyTrip, Goibibo, Booking.com, Agoda and others, corporate billing with TDS 194C and 194I, banquet advances split across two payments, and daily F&B cash deposits — each with its own settlement model, GST slab, and timing. Manual reconciliation across PMS, OTA settlement reports, gateway settlements, and the bank statement is multi-source and cannot reliably classify the OTA gross-to-net gap into commission, TDS 194H, GST on commission, and cancellation adjustments at scale.
- **Logic:** Ingest PMS folios from Opera or IDS Next or eZee or Hotelogix, channel manager records from SiteMinder or STAAH, OTA settlement reports per platform, gateway settlements, and the bank statement. Match each bank credit to its source: OTA UTR to OTA settlement report, gateway batch to card and UPI folios, NEFT to corporate invoice. Decompose every OTA settlement variance into typed codes — OTA_COMMISSION, OTA_TDS_194H, GST_ON_COMMISSION, OTA_CANCELLATION — and route any residual to UNCLASSIFIED_OTA_ADJUSTMENT for review. Apply property-level GST classification at the room-tariff slab to F&B revenue.
- **Config:** Property-level GST classification flag (room tariff below ₹7,500 versus at or above ₹7,500), OTA settlement schema with bookings array and variance source fields, banquet advance two-phase matching keyed by event_booking_id, night-audit cut-off timezone, and PMS-to-bank lag tolerance window for gateway settlements.
- **Output:** A reconciled view that shows each PMS folio against its OTA settlement and bank credit, typed variance codes for every gross-to-net gap, deferred revenue tracked separately for banquet advances, GST slab classification applied automatically to F&B, and an exception list cleared in hours instead of the staff days a hotel finance team typically spends on month-end.

### How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders

Source: https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk/

- **Problem:** Credit officers reading bank statements for risk manually miss NACH bounce patterns, round-trip transactions, and PDF authenticity issues — producing inconsistent underwriting decisions and documentation gaps that fail RBI inspection.
- **Logic:** Follow a seven-step sequence: (1) verify PDF authenticity and balance arithmetic, (2) read opening/closing balance trend over the full statement period, (3) classify income streams excluding transfers and disbursals, (4) compute average monthly balance on 1st, 14th, and last day, (5) check NACH/EMI continuity and return codes, (6) scan narrations for 10 risk word categories, (7) compute FOIR against classified income with proposed EMI included.
- **Config:** 12-month statement for MSME loans, 6-month for personal loans, 3-month for microfinance. FOIR threshold 50% retail / 55% MSME. NACH return threshold: zero returns in last 3 months. Balance check dates: 1st, 14th, last day of month.
- **Output:** A structured credit signal report covering income classification, FOIR, average monthly balance, NACH continuity status, round-trip flag, risk word category hits, and PDF authenticity verdict — with supporting evidence for each signal.

### HUL Bru Coffee Reconciliation — Plantation Purchase vs Instant Manufacture

Source: https://www.terra-insight.com/insights/hul-bru-coffee-reconciliation-plantation-vs-instant/

- **Problem:** A Bru-scale instant coffee operation running approximately 35,000 MT of annual domestic production plus a limited export tail must reconcile green-coffee purchase from approximately 4,500 plantations and curing houses across Chikmagalur, Coorg, Wayanad, and adjacent producing tracts, Section 194C code 1023 job-work TDS on curer processing charges where the manufacturer supplies the green coffee, Section 194Q code 1031 on plantation-wise aggregate purchase above the Rs 50 lakh threshold, Section 194H code 1015 distributor commission at 5 percent on the distributor pyramid, Section 15(2) CGST treatment of BOGO and promo-scheme discounts against distributor and retailer, the Section 54(3) refund cycle on the export line under Rule 89(4), and the Section 43B(h) 45-day MSME payment discipline against smallholder plantations and MSME-registered curing houses. Manual reconciliation across the plantation-to-curer-to-roaster chain and the distributor-to-retailer chain loses grade-variance adjustments, mis-classifies curer job-work between codes 1023 and 1024, misses the Rs 50 lakh threshold crossing per plantation, and reports the export refund on the domestic ITC pool.
- **Logic:** Build a plantation master keyed to the Coffee Board registration number, the estate PAN, and the Section 43B(h) MSME flag; a curer master keyed to the curer PAN with the job-work TDS code (1023 where the manufacturer supplies the material, 1024 where the curer supplies) set on the master; a distributor master keyed to the distributor PAN with the Section 194H commission slab and the Section 15(2) promo-scheme reimbursement matrix; and a plantation running-total ledger that tracks aggregate purchase per estate across the financial year and triggers the Section 194Q code 1031 threshold-crossing switch. Reconcile each green-coffee dispatch lot from plantation to curer against the FAQ grade card and adjust the plantation purchase price on grade variance. Reconcile each curer job-work invoice against the code 1023 TDS accrual and the material despatch and receipt notes. Reconcile the distributor commission run against code 1015 TDS and the distributor promo-scheme reimbursement against the Section 15(2) qualifying tests. Extract the zero-rated export turnover and the accumulated ITC into the Rule 89(4) refund workbook and file GST RFD-01 monthly or quarterly against the export line; track the domestic ITC pool separately as a normal duty structure.
- **Config:** Plantation master with estate code, Coffee Board registration number, PAN, MSME Udyam number where applicable, Section 43B(h) flag, and starting-year threshold state for code 1031; curer master with curer code, PAN, job-work TDS code (1023 or 1024 per contract), FAQ grade card issuance flag, and MSME flag; distributor master with distributor code, PAN, commission slab, Section 15(2) promo-scheme matrix (BOGO, quantity discount, cash-back, retailer secondary reimbursement), and territory; FAQ grade schedule keyed to Arabica Plantation A/AA/AB/PB/C, Arabica Cherry AB/C/PB, Robusta Parchment AA/AB/PB/C, Robusta Cherry AB/C/PB/BBB; plantation running-total ledger with Rs 50 lakh threshold alert; curer job-work ledger with material despatch and receipt note references; roaster intake ledger keyed to the common dispatch lot identifier; GSTR-1 and GSTR-3B feed for the Rule 89(4) zero-rated export refund workbook; MSME payment ageing report against the 45-day Section 43B(h) rule for year-end deduction discipline.
- **Output:** A month-end and year-end Bru-scale reconciliation pack: plantation-wise purchase register with FAQ grade variance adjustment against the curer grade card and code 1031 TDS on threshold-crossing plantations; curer-wise job-work register with code 1023 TDS accrual reconciled against Form 26AS at the curer PAN and material despatch and receipt notes tied to each curer invoice; roaster intake register keyed to the common dispatch lot identifier with grade variance flagged for supplier-quality review; distributor-wise commission run with code 1015 TDS at 5 percent and Section 15(2) qualifying promo-scheme reimbursement reconciled against the distributor's secondary sales claim; Rule 89(4) zero-rated export refund draft with the accumulated ITC on the export line separated from the domestic ITC pool; Section 43B(h) MSME payment ageing report with the 45-day cut-off applied against every MSME plantation and curer for year-end deduction discipline; and — at year-end — a supplier-quality scorecard that ranks plantations and curers on grade consistency, dispatch lead time, and payment cycle compliance.

### Hyundai Motor India Supplier Settlement: Reconciliation for Tier-1 and Tier-2 Auto Suppliers

Source: https://www.terra-insight.com/insights/hyundai-motor-india-supplier-reconciliation/

- **Problem:** Tier-1 suppliers to Hyundai Motor India (HMI) operate inside a Korean-parent-influenced commercial regime — Sriperumbudur Chennai as the operating plant, the new Talegaon site (ex-GM) ramping, HMI Vaatika as the supplier touchpoint, kanban / JIT release discipline that runs without traditional MRP push, Mobis India as the in-house module Tier-1 running a separate commercial framework, RMPV pass-through on aluminium die-cast and copper-content parts, the typical 60-day post-GRN payment cycle, and Section 393(1) Sl. 6(i).D(b) code 1024 TDS overlay on the job-work component. A ₹120 crore annual HMI book demands plant-coded settlement, programme-level FOMP decomposition, rolling 12-month PPM tracking, and RMPV reconciliation against the contracted formula.
- **Logic:** Decompose each HMI settlement at the plant-code level (Sriperumbudur / Talegaon), tie each invoice and debit memo to the source vehicle programme (i20 / Creta / Venue / Verna / Alcazar / Ioniq 5 / Exter), classify debit reasons against the HMI taxonomy, age each FOMP claim against the per-programme running account, monitor PPM rolling 12-month per part against contractual threshold, reconcile RMPV settlements against the contracted LME / benchmark formula with the 30-day lag, calendar Section 34 GST credit notes per accepted debit at 30 November of next FY, and reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i).D(b) code 1024 against the supplier's books.
- **Config:** HMI customer master with sub-records per plant code (Sriperumbudur / Talegaon) and per vehicle programme, separate Mobis India parent record for module-routed supply, Vaatika export-mapping for daily call-off / ASN / GRN / settlement-statement parsing, debit-note reason taxonomy aligned to HMI Supplier Quality Manual codes, FOMP running account per programme, PPM threshold matrix per part with rolling 12-month window, RMPV register per part with LME / benchmark reference and 30-day lag, Form 168 TDS register, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-plant, per-programme HMI settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with FOMP / tooling / PPM penalty attribution, Vaatika-sourced delivery-schedule reconciliation, rolling-PPM dashboard per part against threshold with breach alerts, RMPV variance register showing supplier-computed vs HMI-settled per period, Form 168 TDS register reconciled to books under Section 393(1) Sl. 6(i).D(b) code 1024, and a Section 34 GST credit-note action queue keyed to approaching cutoff.

### IATA BSP Airline-Agent Reconciliation for Indian Travel Agencies

Source: https://www.terra-insight.com/insights/iata-bsp-airline-agent-reconciliation-india/

- **Problem:** An Indian IATA-accredited travel agency reconciles a weekly BSP-link settlement against GDS booking files (Amadeus, Sabre, Galileo) per ticket per airline, manages a Refund Application + ADM/ACM cycle with airline-initiated dispute windows, holds a GST split between 5 percent tour-operator (Notification 11/2017 entry 23) and 18 percent agency commission (SAC 998551), and chases lagged airline-incentive TDS under Section 393 code 1006 across 22+ deductor airline TANs. The reconciliation must hold ticket-number granularity from GDS issuance through BSP weekly settlement through bank-statement debit, with ADM/ACM ageing and incentive-receivable chase live concurrently.
- **Logic:** Build a per-ticket master from GDS issuance files keyed by ARN, ticket number, PNR, airline code, fare basis and commission/incentive structure. Ingest the BSP-link weekly report at ticket granularity and match to GDS issuance with one of four outcomes (clean match, ADM debit, ACM credit, refund settlement). Tie the weekly net debit to bank statement on settlement day. Split agency commission (18 percent SAC 998551 forward charge) from tour-package revenue (5 percent or 18 percent under tour-operator option). Run ADM dispute register with airline reference, response status and 30/60/90 ageing. Chase Section 393 code 1006 TDS on airline incentives through Form 26AS by deductor airline TAN by quarter.
- **Config:** Ticket master keyed by ARN-ticket-number with PNR, airline code, GDS source, fare basis and per-ticket commission structure; airline master with deductor TAN, incentive scheme tier, and Section 393 code 1006 default rate; BSP weekly report ingest with ticket-level matching engine; GDS file ingest per source (Amadeus/Sabre/Galileo) with cut-off reconciliation rules; ADM/ACM register with airline-reference, error code, 30/60/90 ageing and dispute response log; GST classification table separating SAC 998551 18 percent agency commission and Notification 11/2017 5 percent tour-operator option; OTA aggregator master with Section 393 code 1035 and Section 52 CGST TCS flag; Form 26AS quarterly reconciliation by deductor airline TAN.
- **Output:** A weekly BSP-link to GDS reconciliation report with ticket-level match and exception breakdown; per-airline ADM/ACM ageing report with dispute response status; monthly agency-commission revenue with 18 percent GST output split from any tour-package revenue at the elected GST rate; per-airline incentive-receivable ledger with Section 393 code 1006 TDS chase; OTA-aggregator settlement reconciliation with code 1035 TDS and Section 52 CGST TCS credit; quarterly Form 26AS reconciliation by deductor TAN with chase-list for missing credits; FEMA-compliant outbound forex log for international ticket settlements where applicable.

### IB Group Poultry Feed Reconciliation — Input Tax Credit Discipline

Source: https://www.terra-insight.com/insights/ib-group-poultry-feed-reconciliation-input-tax-credit/

- **Problem:** A poultry feed integrator running an IB Group-scale operation at 50,000 MT of monthly compound feed production must reconcile a mixed-rate input register (maize at nil HSN 1005, soya de-oiled cake at 5 percent HSN 2304, micronutrient premix at 18 percent, polypropylene woven feed bags at 18 percent HSN 3923) against a dual-rate output register (60 percent fortified poultry feed variants at 5 percent, 40 percent cattle and aqua feed at nil under HSN 2309 per Notification 2/2017-Central Tax), a Section 43B(h) MSME 45-day payment aging ledger against Rs 40 to Rs 60 crore quarterly turnover-through-Udyam-registered feed-input suppliers, a Section 194Q TDS code 1031 deduction at 0.1 percent above the Rs 50 lakh single-supplier annual threshold, and a Section 54(3) inverted-duty refund cycle on the nil-rated cattle-and-aqua-feed leg. Manual reconciliation across these four surfaces under-collects Rule 89(5) refund on the nil-rated leg, over-claims Section 43B accrual-basis deduction on payments delayed beyond the Section 15 MSMED Act window, and mis-triggers the Section 194Q threshold when suppliers are aggregated at the wrong PAN level.
- **Logic:** Extract per-SKU output rate from the material master and split the daily production batch log into a 5 percent output ledger and a nil output ledger. Apportion input ITC on soya de-oiled cake (5 percent) and packaging (18 percent) between the two output legs using SKU-level bill-of-materials weightings sourced from the feed-formulation master, and lock the apportionment basis before the tax period closes. Feed the nil-rated output turnover and the apportioned Net ITC (excluding input services and capital goods per the Notification 14/2022 amendment) into the Rule 89(5) formula and generate the Form GST RFD-01 refund draft monthly or quarterly. Ingest the Udyam Registration Certificate status against every input supplier master and clock each purchase against the acceptance date of goods; run a Section 43B(h) aging bucket at 30-day, 45-day, and 45-day-plus intervals and surface any supplier where the aging has crossed 45 days (or 15 days absent a written agreement) as a year-end deduction-preservation exception. Aggregate purchases per supplier PAN across a rolling financial year for Section 194Q threshold computation and flip the 0.1 percent code 1031 deduction switch at the invoice-processing stage from the first rupee above the Rs 50 lakh cumulative threshold.
- **Config:** Input supplier master with supplier PAN, Udyam Registration Certificate number and validity, MSME classification (micro / small / medium), Section 194Q threshold-crossing flag, and written-agreement flag for 45-day versus 15-day Section 15 clock; input HSN master with HSN code, input GST rate, and Section 43B(h) applicability; SKU output master with output HSN, output GST rate (nil or 5 percent), and bill-of-materials linkage to input soya DOC and packaging; feed-formulation master with per-SKU input consumption ratio for apportionment of ITC between the two output rates; production batch log with batch number, output SKU, batch weight, and manufacturing date for the daily inverted-duty apportionment; GSTR-1 and GSTR-3B feed for the Rule 89(5) refund workbook; MSMED Act Section 15 aging bucket schedule (30-day, 45-day, 45-day-plus) at supplier and invoice grain; Section 194Q per-supplier YTD purchase aggregation with the Rs 50 lakh threshold-crossing alert.
- **Output:** A month-end poultry-feed reconciliation pack: dual-rate output ledger split between 5 percent-rated poultry feed variants and nil-rated cattle-and-aqua feed, apportioned Net ITC per output leg with the input-service and capital-goods exclusion under the Notification 14/2022-amended Rule 89(5) formula, a Form GST RFD-01 refund draft against the nil-rated leg, a Section 43B(h) MSME payment-aging exception report keyed to Udyam-registered supplier and acceptance date with a year-end deduction-preservation escalation, a Section 194Q code 1031 threshold-crossing register per supplier PAN with the flipped-deduction schedule from the first invoice above the Rs 50 lakh aggregate, and a de-oiled cake versus day-old chick DOC-tagging exception report that surfaces mis-tagged general-ledger entries before they contaminate the supplier PAN aggregation.

### ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)

Source: https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india/

- **Problem:** Section 143(3)(i) of the Companies Act 2013 requires statutory auditors to opine on ICFR adequacy and operating effectiveness, mapped to the COSO 2013 framework via the ICAI Guidance Note. Reconciliation is the largest ICFR control domain — persistent unreconciled bank items past 90 days or GST ITC gaps above ₹10 lakh are the two most common material-weakness findings.
- **Logic:** Each reconciliation is elevated to a documented ICFR control with objective, risk statement, preparer, reviewer, frequency, and aging threshold (typically 15 days to complete, 90 days to resolve exceptions). SA 330 dual-purpose testing selects 25-60 reconciliations per period and verifies on-time preparation, review sign-off, and exception resolution; failure rate above 10% indicates the control is not operating effectively.
- **Config:** ICFR control register linking each reconciliation to COSO component, preparer or reviewer role matrix, aging threshold configuration (15 days preparation, 90 days resolution), and evidence-vault for SA 330 testing.
- **Output:** ICFR-ready reconciliation control documentation, operating-effectiveness evidence for every period, deficiency log tied to material-weakness definitions, and Board-report and AOC-4 disclosure inputs.

### ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching

Source: https://www.terra-insight.com/insights/icici-bank-reconciliation-india/

- **Problem:** ICICI CIB statements use hyphen-delimited NEFT narrations and a /TXT/ prefix in MT940 :86: (not HDFC's /INF/), so running the wrong parser produces null match keys. iCollect virtual account numbers are the correct primary key for collection accounts, not the UTR — a common misconfiguration that routes payments to the wrong invoice.
- **Logic:** ICICI parser profile strips /TXT/ prefix and splits narration by hyphens to extract UTR, counterparty, and reference. iCollect credits are keyed on virtual account number as the primary identifier, with UTR as a secondary key. Service-charge auto-debits are routed to the bank charges GL with 18% GST linked to the monthly ICICI tax invoice for ITC.
- **Config:** ICICI /TXT/ parser profile with hyphen delimiters, iCollect virtual-account-first routing, CIB CSV and MT940 dual ingestion, and Section 194A TDS check on interest credits above ₹40,000.
- **Output:** Correctly extracted UTR and counterparty for every ICICI credit, invoice-accurate iCollect attribution via virtual account number, bank charges ITC schedule, and reconciled ledger ready for BRS reporting.

### IDFC FIRST Bank Corporate Reconciliation: Statement Formats and Narration Conventions

Source: https://www.terra-insight.com/insights/idfc-first-bank-corporate-reconciliation-india/

- **Problem:** IDFC FIRST corporate statements arrive across three channels — portal CSV/Excel, MT940 over SFTP, and connected banking files — each with hyphen-delimited narrations that reconciliation parsers built for HDFC or ICICI forward-slash formats break on. NACH batch entries also hide mandate-level detail, and service-charge auto-debits bury 18% GST that is recoverable as input tax credit.
- **Logic:** Channel-aware parsing routes IDFC FIRST portal CSV, MT940, and connected banking exports to dedicated configurations. Narrations are split on hyphens and validated by segment shape: 22-character UTR in segment two for NEFT and RTGS, 12-digit reference for UPI, and batch reference for NACH. NACH single-line batch credits are exploded against the NPCI settlement report. Service-charge auto-debits are mapped to the bank charges GL with the 18% GST component linked to the monthly tax invoice.
- **Config:** IDFC FIRST hyphen-delimited parser profile, SFTP ingestion for MT940 and connected banking files, portal CSV fallback with narration completeness alert, Section 194A TDS auto-reconciliation for interest credits above ₹40,000.
- **Output:** Clean transaction ledger from IDFC FIRST statements regardless of channel, mandate-level NACH explosion via NPCI report join, bank-charges GL line with ITC-eligible GST schedule, and Section 194A TDS credit aligned to Form 26AS.

### IFFCO Cooperative Fertilizer DBT Claim Reconciliation

Source: https://www.terra-insight.com/insights/iffco-cooperative-fertilizer-dbt-claim-reconciliation/

- **Problem:** An Indian fertilizer cooperative's regional finance team running 12,500 authorised retail dealers with 42,000 metric tonnes of monthly Urea dispatch must reconcile the plant-to-depot stock transfer register, the depot-to-outlet dispatch invoice against each outlet's Form O-1 authorisation, the outlet-level e-Urvarak PoS sales register with Aadhaar-biometric authentication flag on every retail transaction, the weekly claim workbook uploaded to the DoF's iFMS system, and the 6-to-8-week DBT sanction credit landing in the cooperative's bank account. A single mis-classified authentication mode, a dispatch to a deauthorised outlet, or a stock-ledger over-sale at the outlet layer surfaces at the DoF as a rejected claim line that must be tracked as a receivable-in-dispute across three or four subsequent weekly cycles. Manual reconciliation over three surfaces at this scale loses per-transaction Aadhaar-biometric flags, over-states weekly claim value against actual PoS-authenticated sales, and mis-attributes the DoF-sanction delay to the Section 43B(h) MSME payable cycle — exposing the cooperative to a mixture of DBT-claim rejection, GST notice at year-end audit, and disallowance of MSME-payable deductions in the current year.
- **Logic:** Build a plant-to-depot-to-outlet stock ledger keyed on Form O-1 authorisation ID at every outlet, expand each dispatch line into the expected outlet receipt window and the expected PoS sales tally within the depot cycle, and match dispatch quantity, grade, and MRP against the outlet's opening stock plus receipt. Ingest the e-Urvarak PoS terminal export per outlet on the daily upload cycle and attribute each PoS-recorded sale to a bag-count deduction from the outlet's stock ledger. Carry the Aadhaar-biometric authentication mode (bio, OTP, IRIS, demographic-fallback) as an immutable attribute of every PoS sale line, and aggregate authentication-mode ratios per outlet per week as a reconciliation quality metric. Feed the weekly claim workbook from the aggregated PoS-authenticated sales tally by outlet by grade, apply the Urea Cost-Plus differential per bag for the Urea SKU and the NBS nutrient-based subsidy per bag for P and K grades, submit to the DoF's iFMS, and reconcile the sanctioned DBT credit (6 to 8 weeks later) line by line against the submitted claim — rejected lines flow to a receivable-in-dispute register with rejection reason attribution for the subsequent claim cycle. Layer the Section 43B(h) MSME ageing bucket on the retail-dealer commission and depot-to-outlet freight vendor masters so the Q4 tightening cycle clears MSME payables ahead of 31 March irrespective of the DBT sanction lag.
- **Config:** Authorised-outlet master with Form O-1 authorisation ID, GSTIN (where the outlet is registered above threshold), PAN, TDS code 1015 (commission-agent Section 194H at 5 percent) or 1002 (contractor Section 194C at 2 percent) per the outlet's operating structure, and MSME registration flag; plant and depot master with production capacity, cost-of-production reference by grade for the Cost-Plus formula, and dispatch-cycle configuration; SKU master mapping every SKU to a subsidy scheme (Urea Cost-Plus versus NBS) with nutrient content for the NBS grades; e-Urvarak PoS terminal ID at every outlet with authentication-mode ratios versioned by week; weekly claim workbook template configured for Urea and NBS separately, submitted to the DoF's iFMS on the weekly upload cycle; DoF sanction reconciliation window (6 to 8 weeks) with alert thresholds at 45 days and 60 days from claim upload; Section 43B(h) MSME ageing bucket configuration (45 days where written agreement exists; 15 days otherwise); Section 65 GST audit interface with the depot-to-outlet dispatch invoice register for e-way-bill reconciliation.
- **Output:** A month-end fertilizer DBT reconciliation pack: opening depot stock by grade, plant-to-depot receipts, depot-to-outlet dispatches by Form O-1 outlet, outlet-level PoS-authenticated sales with authentication-mode split, closing depot and outlet stock, weekly claim workbook submissions to the DoF's iFMS by week, sanctioned DBT credit landings against submitted claims with rejection-line attribution, and the running receivable-in-dispute register with age against the DoF's 6-to-8-week window. Section 43B(h) MSME ageing bucket surfaces retail-dealer commission and depot-freight payables approaching the 45-day threshold ahead of Q4 close. Per-outlet authentication-mode quality score feeds the field-force communication to outlets running high fallback ratios so the ratio is corrected before the DoF's iFMS deprioritises the outlet for secondary verification.

### IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts

Source: https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation/

- **Problem:** A multi-state business with five GSTINs runs five GSTR-3B filings and three tax head buckets (IGST, CGST, SGST) per GSTIN, each with distinct place-of-supply rules and a mandatory Section 49 set-off hierarchy. An inter-state supply mis-booked as intra-state leaves CGST plus SGST credit that cannot offset IGST liability, creating demand exposure in both states.
- **Logic:** Classification applies IGST Act place-of-supply rules to every invoice using supplier state plus buyer state plus supply type (goods, services, stock transfer). ITC set-off is applied in the Finance Act 2019 sequence: IGST credit offsets IGST, then CGST, then SGST; CGST credit offsets CGST then IGST; SGST credit offsets SGST then IGST. Each GSTIN ledger is reconciled independently, then inter-GSTIN stock transfers are netted across the group.
- **Config:** Per-GSTIN tax-head ledger with place-of-supply classifier, Section 49 set-off engine, and inter-state stock-transfer tracker for same-PAN multi-GSTIN groups.
- **Output:** GSTR-3B ready with correct tax-head splits per GSTIN, inter-state mis-classification exception list for credit-note correction, consolidated group-level ITC utilisation schedule, and audit trail showing compliance with the mandatory set-off sequence.

### Import Alert 89-08: Reconciling Lost US Revenue Under Ind AS 115

Source: https://www.terra-insight.com/insights/import-alert-89-08-lost-revenue-reconciliation-pharma/

- **Problem:** A Tier-1 Indian pharma formulator with a US-market injectable footprint of the order of USD 42 million FOB across February and March 2026 shipments receives an Import Alert 89-08 listing on its Hyderabad-area injectable plant with effect from April 2026. The shipments dispatched pre-alert are already at or approaching the US port and are placed on Detention Without Physical Examination on release inspection. The finance team must simultaneously (a) reverse the Ind AS 115 revenue on the alert-affected shipped-but-detained batches because the paragraph-56-to-58 highly-probable threshold is no longer met, (b) restore the corresponding cost of goods sold and inventory, (c) reassess the net realisable value of the shipped-but-detained inventory under Ind AS 2 against the third-country re-export or destruction alternatives, (d) recognise the Ind AS 37 provision for US-port demurrage, restocking, and destruction cost, (e) preserve the Section 54(3) LUT-bond export-side IGST refund cycle which is unaffected by the destination-country alert, and (f) gate any refund payment back to the US buyer through the correct Section 195 TDS treatment with DTAA and TRC overlay. The reconciliation workbook must isolate the alert-affected SKUs and batches with shipment-level granularity, hold the pre-alert and post-alert accounting entries separately, and roll a monthly view against the DoP-inspection remediation cycle that ultimately determines when the alert is lifted and the revenue recognition can resume on a prospective basis.
- **Logic:** Build a shipment-level FOB export register for the affected plant, keyed to shipping bill number, export general manifest date, US-buyer name (anonymised in the reconciliation extract), invoice amount in USD and INR, cost of goods sold amount, and SKU-and-batch identifiers. Cross-reference the register to the Import Alert 89-08 SKU scoping — the alert typically applies to a specific manufacturing surface (an injectable line, a specific dosage form category) rather than to the plant's full portfolio, so the reconciliation must isolate the alert-affected SKUs and batches. For each alert-affected shipment, apply the Ind AS 115 reassessment at the reporting date under paragraphs 56 to 58 — the paragraph-57 external-regulatory-factor test breaks the highly-probable threshold, and the revenue is reversed in the current reporting period with a corresponding restoration of inventory (Ind AS 2 at the lower of cost and net realisable value) and reversal of cost of goods sold. Recognise the Ind AS 37 provision for the estimated US-port demurrage, restocking, destruction, and buyer-indemnity outflow at the best-estimate figure under paragraph 36. Preserve the Section 54(3) IGST refund cycle on the export-side accumulated ITC — the export status is anchored to the Indian shipping bill and export general manifest which are pre-alert and unaffected. Gate any refund to the US buyer through the Section 195 TDS treatment, splitting the refund between return-of-consideration (no TDS) and consequential-loss (DTAA-modulated TDS with TRC). Reassess each reporting date until the plant is removed from Import Alert 89-08 and prospective revenue recognition can resume.
- **Config:** Plant master with USFDA-inspection status per plant per date (including Import Alert stage — 66-40 plant-wide, 89-08 category-specific, 99-32 detention-with-cause, and Consent Decree); alert-effective-date register with per-SKU scoping of the alert-affected manufacturing surface; shipment-level FOB export register keyed to shipping bill number, EGM date, US-buyer identifier, invoice amount (USD and INR), COGS amount, SKU and batch identifier; Ind AS 115 reassessment workbook per reporting date with the paragraph-56-to-58 reassessment output for each alert-affected shipment; Ind AS 2 net realisable value estimate holding the third-country re-export price (net of freight, re-labelling, expiry) alongside the destruction-outcome zero value; Ind AS 37 provision workbook per reporting date with the US-port demurrage, restocking, destruction, and buyer-indemnity best-estimate figures; Section 54(3) IGST refund continuity register showing the export-side ITC accumulation, LUT registration status, and monthly Form GST RFD-01 filing progress unaffected by the alert; Section 195 TDS workbook per refund payment with the return-of-consideration versus consequential-loss split, the DTAA article reference (Article 22 other income typically), the buyer TRC on-file flag, the applicable TDS rate, and the Form 27EQ quarterly return schedule; and a rolling monthly reassessment feed against the DoP-inspection and USFDA-remediation cycle status that ultimately governs the alert removal and prospective revenue recognition resumption.
- **Output:** A monthly reporting-date Import Alert 89-08 reconciliation pack: the shipment-level FOB export register isolating the alert-affected batches; the Ind AS 115 revenue reversal computation per shipment with the paragraph-56-to-58 reassessment memo; the Ind AS 2 inventory restoration with the net realisable value adjustment where third-country re-export is not economic; the Ind AS 37 provision movement for US-port demurrage, restocking, destruction and buyer-indemnity; the Section 54(3) IGST refund continuity confirmation on the export-side ITC accumulation (Form GST RFD-01 monthly filing progress unaffected); the Section 195 TDS working per refund payment to the US buyer with the return-of-consideration versus consequential-loss split, the DTAA article and TRC treatment, and the Form 27EQ quarterly return line; and the roll-forward view against the remediation-and-closure cycle that will ultimately govern the alert removal and the resumption of prospective US-market revenue recognition. The pack rolls into the quarterly Ind AS 8 accounting-estimate-change disclosure and the year-end audit file.

### Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics

Source: https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements/

- **Problem:** A fabricated bank statement often contains transactions dated on days when specific payment rails were closed — national bank holidays, 2nd and 4th Saturdays, Sundays. These dates are impossible for NEFT, RTGS, and cheque transactions because the underlying settlement infrastructure was not operating. Human reviewers rarely cross-check each transaction date against a holiday calendar.
- **Logic:** For every NEFT, RTGS, and cheque transaction in the statement, check the transaction date against the RBI bank holiday calendar plus the 2nd and 4th Saturday schedule. Flag any transaction dated on a day when that rail's settlement system was closed. Exclude UPI, IMPS, and cash transactions — those rails operate 24x7 and have no closed-date constraint.
- **Config:** Holiday calendar: 150+ RBI-notified national bank holidays from 2019 to 2026, plus all 2nd and 4th Saturdays and Sundays. Rail classification: derive from transaction description keywords (NEFT/N/, RTGS/R/, CTS/CHQ for cheque; UPI/, IMPS/I/ for 24x7 rails).
- **Output:** List of flagged transactions showing: date, rail type, amount, counterparty, and the reason for flagging (national holiday / 2nd Saturday / 4th Saturday / Sunday). Presented in the fraud signals section of the analysis report with the specific holiday name where applicable.

### IMS Accept / Reject / Pending Workflow for Indian Finance Teams

Source: https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india/

- **Problem:** Finance teams operating IMS without a structured Accept/Reject/Pending decision framework either reject too aggressively (losing ITC on recoverable invoices), accept too leniently (claiming ITC on misfiled or fictitious invoices), or leave too much in Pending (triggering 30-day deemed-Accept on invoices that should have been Rejected).
- **Logic:** A three-decision framework maps each invoice to one of three outcomes based on objective tests: exact purchase-register match plus amount within tolerance triggers Accept; no purchase-register match or amount mismatch above tolerance triggers Reject; partial or ambiguous match triggers Pending with vendor follow-up. Pending items are aged with a day-25 alert before the 30-day deemed-accept threshold.
- **Config:** Decision-rule thresholds (amount tolerance, date tolerance), actor-role mapping (analyst, manager, controller), Pending aging alert at day 25, audit-trail capture with actor identity and timestamp per decision, and integration with vendor-management workflow for Pending follow-up.
- **Output:** Per-month IMS decision log with actor identity and timestamp for each Accept, Reject, and Pending, audit pack mapping decisions to purchase register and GSTR-2B lines, and Pending queue aging report ready for day-25 review.

### IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews

Source: https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india/

- **Problem:** Supplier-side GSTR-1 amendments under Type 9 and Type 9A surface in the buyer's IMS as new actionable entries with references to original invoices. Buyers who accepted the original must re-act on the amendment, and buyers who rejected the original face the ghost-invoice risk where the amendment can deemed-Accept past 30 days. Without a structured amendment workflow, ITC integrity breaks at scale.
- **Logic:** An amendment-aware workflow tracks original-amendment pairs by reference, presents both versions to the buyer with the action delta clearly marked, applies the same purchase-register match logic to the amended version, and inherits or rolls back the original action based on buyer decision. Section 16(4) time limit alerts surface for prior-period amendments approaching the deadline.
- **Config:** Amendment-pair tracking on supplier GSTIN plus original invoice number plus amendment reference, action-delta presentation, inheritance rules from original to amendment, Section 16(4) deadline alerts per invoice, and re-action SLA aligned to the 30-day deemed-Accept clock.
- **Output:** Amendment-cycle decision log with original-versus-amended action history, post-amendment GSTR-2B reflecting the buyer's latest decisions, Section 16(4) time-limit dashboard for pending amendment items, and audit trail capturing both original and amended decision timestamps.

### GST IMS Dashboard Actions Step-by-Step: Accept, Reject, Pending for Indian Businesses

Source: https://www.terra-insight.com/insights/ims-dashboard-actions-step-by-step-india/

- **Problem:** Indian finance teams must act on every IMS record before GSTR-2B generation or risk auto-accepted, undisputable ITC on wrong invoices and Rule 88C/88D notices downstream.
- **Logic:** Classify each IMS record against PO, GRN, and supplier-filing status, then map to one of three actions — Accept, Reject, Pending — within the open window before 2B is locked for the period.
- **Config:** Daily IMS pull from the GST portal, PO/GRN match against ERP, supplier GSTR-1 filing status check, action push back to the portal, escalation queue for unresolved items by day 11 of the following month.
- **Output:** Clean GSTR-2B reflecting only intended ITC, reduced Rule 88C/88D mismatch notices, audit-ready action log per invoice, and lower ITC reversal risk under Section 16(2)(aa).

### Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce

Source: https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail/

- **Problem:** High-volume Indian retail and e-commerce operators face 5,000+ monthly inward invoices across 8-12 state GSTINs plus marketplace B2B flows. Manual IMS reconciliation in the six-day window between GSTR-2B generation and GSTR-3B filing is mathematically infeasible, and deferred ITC directly impacts inventory-linked cash flow.
- **Logic:** Per-GSTIN IMS data is pulled and consolidated into a unified decision queue keyed on supplier GSTIN plus invoice number plus state GSTIN. Category-wise accept/reject rules apply differential tolerance per supplier tier. Marketplace-issued invoices are cross-matched against marketplace settlement reports before IMS decision. Exception triage routes to state finance owners with vendor follow-up SLAs.
- **Config:** Per-GSTIN dashboard credentials, supplier category mapping (strategic / mid-tier / tail), category-specific tolerance rules, marketplace settlement report ingestion, inventory cycle alignment for Pending review, and state finance owner routing.
- **Output:** Consolidated IMS decision queue across all GSTINs, category-specific exception reports, post-decision GSTR-2B per GSTIN, ITC working-capital impact projection by state, and audit pack tying every accepted invoice to purchase register and goods-receipt note.

### IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do

Source: https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation/

- **Problem:** Since October 2024, GSTR-2B contents are determined by the recipient's Accept, Reject, or Pending actions in the Invoice Management System — making the old two-way purchase register vs GSTR-2B reconciliation structurally incomplete. The 14th-to-20th six-day IMS window forces bulk invoice review before GSTR-3B filing.
- **Logic:** Three-way matching compares purchase register against IMS pending queue against the resulting GSTR-2B on invoice number plus supplier GSTIN plus tax period. Auto-recommended IMS actions (Accept, Reject, Pending) are generated from the purchase-register match so the finance team only reviews exceptions. Once IMS actions are posted, the reconciliation re-runs against the updated GSTR-2B.
- **Config:** Purchase-register-to-IMS mapping rules, auto-action recommendations per match type (exact, partial, orphan), six-day window scheduler aligned to the 14th-20th cycle, and amendment tracker for mid-period IMS changes.
- **Output:** IMS action recommendation list ready for one-click submission, post-action GSTR-2B aligned with the purchase register, Pending queue for roll-forward, and audit trail linking every GSTR-3B ITC claim to the IMS decision that produced it.

### IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters

Source: https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching/

- **Problem:** Finance teams operating under pre-IMS assumptions treat GSTR-2B as a passive feed that auto-populates from supplier GSTR-1. Since October 2024, GSTR-2B is the output of an IMS decision pipeline. The structural shift changes who acts, when, what happens to mismatches, Rule 36(4) compliance burden, and the cash flow timing on ITC realisation — none of which are visible to teams that have not updated their workflow.
- **Logic:** A side-by-side comparison maps the two models across six dimensions: who acts, when action happens, mismatch handling, Rule 36(4) evidence chain, cash flow timing, and audit trail composition. The IMS model is strictly the more rigorous of the two; the legacy model is functionally closed for current-period invoices.
- **Config:** Six-dimension comparison matrix, transition checklist for teams moving from legacy to IMS workflow, cash flow impact modelling for the deferred ITC scenarios, and Rule 36(4) audit-trail upgrade specification.
- **Output:** Operational gap analysis between current workflow and IMS-compliant workflow, cash flow impact projection per period, audit-trail upgrade plan, and implementation roadmap for transition to active in-cycle decision model.

### Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies

Source: https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india/

- **Problem:** Contract modifications mid-project (scope changes, rate revisions) require reassessment of performance obligations under Ind AS 115, and failure to track these creates material misstatement risk in revenue.
- **Logic:** Map each contract to performance obligations, track modifications against the five-step model, recalculate transaction price allocation on scope changes, reconcile cumulative revenue against cash and receivables.
- **Config:** Ind AS 115 five-step model, variable consideration constraints, contract modification prospective vs cumulative catch-up treatment, MCA notification requirements, ICAI guidance notes.
- **Output:** Contract-level revenue reconciliation, modification impact analysis, remaining performance obligation disclosure, and disaggregated revenue report by type and geography.

### Ind AS 38 vs Section 35(2AB): Reconciling Book vs Tax R&D Treatment

Source: https://www.terra-insight.com/insights/ind-as-38-r-and-d-capitalisation-vs-section-35-2ab-pharma/

- **Problem:** An illustrative Tier-2 biosimilars formulator running a Bangalore DSIR-approved in-house R&D facility incurs total R&D expenditure of the order of Rs 320 crore in FY 2026-27 on an active biosimilars development pipeline — for example an anti-VEGF biosimilar in Phase 3 pivotal trials and regulatory filing preparation. The spend splits into a research-phase component of Rs 145 crore (pre-clinical work and Phase 1 safety trials, expensed under Ind AS 38 and deducted under Section 35(2AB)) and a development-phase component of Rs 175 crore (Phase 2 and Phase 3 trials, comparability studies, process scale-up and regulatory filing preparation, capitalised under Ind AS 38 on the balance sheet but revenue-expensed for tax under Section 35(2AB) at the DSIR-approved facility). The book-tax gap of Rs 175 crore in FY 2026-27 gives rise to a deferred tax movement of the order of Rs 44 crore at an MAT-adjusted effective tax rate of 25.17 percent, which is disclosed in the Ind AS 12 deferred tax note and reconciled in the effective tax rate walk. The gap unwinds over the ten-year amortisation life of the capitalised intangible asset once the biosimilar launches.
- **Logic:** Extract the R&D cost centre from the accounting system at project sub-ledger level. Split each project's monthly spend into research-phase versus development-phase using the Ind AS 38 six-condition test evidence, with a documented capitalisation trigger date per project (typically Phase 2 entry or a comparability-study milestone). Run in parallel the Section 35(2AB) DSIR-eligibility classification per project (scientific research staff salaries, consumables, internal clinical trial costs, patent costs, DSIR-listed items are eligible; land and buildings, civil engineering, non-listed plant and machinery, market research, non-linked outsourced testing are not). Compute the book-tax temporary difference per project per year as the capitalised amount less the tax deduction claimed. Post the Ind AS 12 deferred tax movement per project at the enacted or substantively enacted effective tax rate. Reconcile the three parallel registers (book capitalisation, Section 35(2AB) eligibility, Ind AS 12 deferred tax bridge) to the same source expenditure ledger, so the year-end Form 3CL quantum, the Ind AS 38 intangible asset addition, and the Ind AS 12 deferred tax movement all trace to a single per-project workbook.
- **Config:** R&D project master with project code, therapeutic area, development phase (pre-clinical, Phase 1, Phase 2, Phase 3, regulatory filing), capitalisation trigger date and six-condition test evidence memo reference; R&D cost centre general ledger with per-project sub-ledger split into DSIR-eligible categories (staff salaries, consumables, clinical trial internal costs, patent costs, DSIR-listed items) and non-eligible categories (land and buildings, civil engineering, non-listed plant and machinery, market research); Form 3CM DSIR facility approval date and three-year renewal cycle monitor; Form 3CL year-end quantum register with DSIR-empanelled CA certification workflow; Form 3CLA return-of-income schedule generator; Ind AS 38 capitalisation register per project with useful-life and amortisation-start-date fields; Ind AS 12 deferred tax bridge per project per year with the temporary difference, the enacted effective tax rate, and the deferred tax asset or liability movement; annual report disclosure feed to the intangible-asset note, the deferred-tax movement note, and the effective-tax-rate reconciliation.
- **Output:** A year-end R&D book-tax reconciliation pack that separates research-phase expensed spend from development-phase capitalised spend under Ind AS 38, aligns the Section 35(2AB) eligible-expenditure quantum to the Form 3CL certification base, computes the per-project book-tax temporary difference and the Ind AS 12 deferred tax movement, and traces every rupee of R&D expenditure to a single per-project source ledger. The pack outputs three primary deliverables — the Ind AS 38 intangible asset schedule with the addition, amortisation and closing balance per project; the Form 3CL and Form 3CLA quantum for the return of income; and the Ind AS 12 deferred tax movement schedule that feeds the annual report disclosure and the effective tax rate reconciliation. A quarterly review reconciles the three registers to the source ledger and surfaces any classification breakages for correction before the year-end audit.

### Input Tax Credit on Capital Goods for Auto-Component Manufacturers: Section 16, 17(5), Rule 43

Source: https://www.terra-insight.com/insights/input-tax-credit-capital-goods-auto-manufacturing-india/

- **Problem:** Indian auto-component manufacturers undertaking greenfield or brownfield capex face a line-by-line ITC eligibility decision under Section 16(1) of the CGST Act, Section 17(5) blocks, Rule 43 spreading where output is partly exempt or zero-rated, the EPCG scheme override for export-tied imported capex, and Section 18(6) accelerated reversal on mid-life disposal. A ₹18 crore greenfield press shop typically carries 60 to 90 capex line items spanning press lines, CNC machining, robotic cells, paint booths, ETP, ASRS, IoT sensors, MEP infrastructure, civil works and office equipment — each line with a different ITC story. Mis-classifying even a small number of lines at capitalisation creates ₹15 to ₹40 lakh of audit-findable exposure that surfaces at GSTR-9 reconciliation, and the structural Rule 43 reversal on the 10% to 15% export share creates a recurring ITC leakage that compounds over the 60-month attribution window.
- **Logic:** Build a line-by-line capex ITC eligibility matrix at the procurement stage; classify each line as (a) Section 16 eligible plant and machinery, (b) Section 17(5) blocked, (c) partly blocked under Section 17(5)(c) for civil-works-adjacent infrastructure, (d) EPCG-imported with refund-versus-utilise decision, or (e) shared-use with Rule 43 attribution; for each eligible line, stamp the capitalisation date, ITC amount, 60-month schedule and Rule 43 monthly attribution; run the monthly Rule 43 reversal automatically against the live exempt-turnover ratio; on disposal, compute the Section 18(6) reversal; reconcile to capital-goods register at GSTR-9 Tables 6C and 7.
- **Config:** Capex line-item master with Section 16/17(5) classification, EPCG status flag, shared-use status, Rule 43 schedule, monthly attribution and reversal; live exempt-turnover ratio feed from sales register; refund-versus-utilise decision workflow for EPCG-imported assets; disposal workflow with Section 18(6) computation; reconciliation rule between capex line-item master, GSTR-3B Tables 4 and GSTR-9 Tables 6 and 7.
- **Output:** A line-by-line capex ITC eligibility decision register; a monthly Rule 43 attribution and reversal schedule across all capitalised assets; a refund-versus-utilise position for EPCG-imported capex; a disposal-side Section 18(6) reversal queue; and a GSTR-9 audit-defence pack tying every capex line to Section 16, 17(5) or Rule 43.

### Intercompany Reconciliation in India: Group Finance Complexity

Source: https://www.terra-insight.com/insights/intercompany-reconciliation-india/

- **Problem:** Multi-entity Indian groups process intercompany charges that must net to zero across entities before consolidated financial statements. TDS and GST on intercompany transactions add complexity.
- **Logic:** Match intercompany receivables against corresponding payables across entity pairs. Identify timing differences, amount mismatches from TDS deductions, and missing entries.
- **Config:** Entity pair mapping, intercompany account codes, TDS section applicability (194J for management fees, 194C for shared services), GST on intercompany supplies, tolerance band for rounding.
- **Output:** Entity-pair reconciliation with net position, unmatched intercompany entries, TDS receivable/payable mismatches, and elimination entries for consolidation.

### Internal Audit of OEM Receivables for Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/internal-audit-oem-receivables-auto-component-india/

- **Problem:** OEM receivables at an Indian auto-component Tier 1 are the highest-volume, highest-variability receivables in Indian manufacturing — the scheduling-agreement-to-invoice-to-receipt chain has six control points, the OEM debit-note regime can short-pay 8% to 12% of monthly billing, RMPV claims are variable consideration with forward estimation risk, the OEM portal is the source of truth, and the SA 240 fraud overlay covers round-tripping, phantom RMPV, debit-note suppression, and DRC-08 GST patterns. A generic AR internal audit checklist will miss four out of these five distinct risk layers.
- **Logic:** Apply a domain-specific controls testing matrix. Test the SA-to-invoice-to-receipt chain with six control points, each sampled at 30 to 60 transactions. Test the debit-note authorisation matrix with segregation of duties testing. Test the RMPV claim approval workflow with constraint-policy alignment. Run cum-quantity drift sampling per SA. Run short-pay decomposition by reason. Overlay SA 240 fraud-risk procedures — analytical review on dispatch trend, claim acceptance sample, GST credit note reconciliation. Document exception findings with materiality flagging and recommended remediation.
- **Config:** Six-control SA-to-invoice-to-receipt matrix with control owner, frequency, evidence, and exception threshold per control. Debit-note authorisation cap matrix per role. RMPV claim register with constraint-policy tier per claim. Cum-quantity drift sampling rule per SA. Short-pay reason taxonomy with ageing buckets per reason. SA 240 fraud-risk pattern library mapped to test procedure. OEM portal data access for substantive testing.
- **Output:** An internal-audit working-paper file per OEM with control test results, exception list with materiality flagging, fraud-risk pattern test conclusions, recommendation matrix with severity ranking, and a management letter draft addressing identified control weaknesses. A quarterly internal-audit report to the Audit Committee summarising OEM-receivables control state across the entire OEM portfolio.

### Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence

Source: https://www.terra-insight.com/insights/internal-audit-reconciliation-india/

- **Problem:** Section 138 of the Companies Act 2013 plus Rule 13 mandate internal audit for listed companies and thresholds (₹50 crore paid-up, ₹200 crore turnover, ₹100 crore borrowings). SA 530 sampling requires sufficient evidence across bank, party, TDS, and GST reconciliations — spreadsheet-only reconciliations with no version history fail ICAI peer review.
- **Logic:** Risk-based sampling stratifies reconciliation populations by value and transaction count (high-risk: vendor-payment bank accounts, GST ITC; low-risk: petty cash floats). Each selected reconciliation is tested for design and operating effectiveness: preparer plus reviewer sign-off, aging analysis, exception resolution within SLA, and management-response trail. Findings feed SIA 330 documentation.
- **Config:** SA 530 stratified sampling at 95% confidence plus 5% tolerable error, SIA 330/350 evidence templates, aging threshold of 90 days for unresolved items, and risk-weighted scope for high-value ledgers.
- **Output:** Signed-off audit evidence pack with sample selection rationale, variance testing results, ICFR-feed memo for Section 143(3)(i), and prior-observation follow-through log for the Audit Committee.

### Internal Financial Control (ICFR) Reporting under Section 143(3)(i): Indian Auditor Guide

Source: https://www.terra-insight.com/insights/internal-financial-control-icfr-section-143-3-i-india/

- **Problem:** Section 143(3)(i) of the Companies Act 2013 requires the statutory auditor to opine on ICFR adequacy and operating effectiveness, separately from the financial statements opinion. The auditor must classify each control gap as a deficiency, significant deficiency, or material weakness, and choose between an unmodified, qualified, or adverse ICFR opinion. Misclassification is the most common NFRA disciplinary finding since 2023.
- **Logic:** The ICAI Guidance Note prescribes a two-phase test: design effectiveness (walkthrough of a single transaction through each control point) and operating effectiveness (SA 330 dual-purpose testing of a sample, typically 25 to 60 instances depending on frequency). Each gap is evaluated for likelihood and magnitude of potential misstatement; only those with reasonable possibility of material misstatement rise to material weakness and force a modified opinion.
- **Config:** Engagement-level ICFR control register linked to COSO 2013 components, walkthrough templates per process, SA 330 sample-size matrix by control frequency, deficiency evaluation worksheet with likelihood-magnitude grading, opinion-paragraph template library covering unmodified, qualified, and adverse formats.
- **Output:** Section 143(3)(i) opinion paragraph drafted with appropriate modification language, deficiency communication letter to those charged with governance under SA 265, engagement file evidence supporting the opinion, and Board-report disclosure inputs under Section 134.

### International Card MDR: Cross-Border + Forex Layering for Indian Merchants

Source: https://www.terra-insight.com/insights/international-card-mdr-cross-border-forex-layering-india/

- **Problem:** International card transactions are the highest-cost MDR cell in the Indian payment stack — Visa and Mastercard cross-border at 2.69 to 3.5 percent before forex, American Express issued abroad above that band, and a 1 to 1.5 percent forex conversion margin layered on top for non-INR settlements. The Cashfree 2.69 percent promo applies only up to ₹10 lakh of monthly international GTV with overflow billed at 2.99 percent, Razorpay and PayU publish 3 percent flat, and Amex-abroad sits outside the Cashfree international promo entirely. A travel OTA, SaaS exporter or D2C brand with cross-border buyers can lose 50 to 100 basis points of margin per international order to slab misclassification, unreconciled forex margin, or a domestic BIN incorrectly charged at the international rate.
- **Logic:** Reconciliation joins the gateway settlement file against the merchant OMS and the BIN-to-issuer-country lookup, then runs five checks per cycle. Check one matches issuer country to scope and flags any domestic BIN billed at the international slab and any foreign BIN billed at the domestic slab. Check two tracks cumulative international Visa and Mastercard GTV against the Cashfree ₹10 lakh promo threshold and validates the per-transaction MDR sits in the correct band — 2.69 percent below the line, 2.99 percent above. Check three isolates American Express transactions, splits Amex Indian-issued at 2.95 percent from Amex-issued-abroad at the standard international Amex rate, and confirms neither is being routed into a promo band. Check four reconciles forex conversion margin reported by the acquirer as a separate line from MDR and validates the spread against the relevant scheme reference rate band. Check five verifies that MDR retained on refunded international transactions is captured as a non-recoverable cost in the international fee scorecard.
- **Config:** Gateway settlement file ingestion for Cashfree, Razorpay and PayU with payment_id and order_id joins to the OMS; BIN-to-issuer-country lookup table covering Visa, Mastercard, American Express and Diners; per-instrument rate set for international Visa and Mastercard at the 2.69 percent promo band, 2.99 percent overflow band and 3 percent flat where applicable; American Express rate set for Indian-issued 2.95 percent and Amex-abroad standard international rate; cumulative international GTV running tally against the ₹10 lakh promo threshold with mid-month alerting; forex conversion margin reconciliation against the acquirer reference rate; refund-MDR non-reversal capture against the international book; monthly GST-on-MDR invoice matcher for input tax credit; and an exception log of slab-misclassification events that drives the next renegotiation cycle.
- **Output:** A monthly international card fee scorecard with per-instrument effective rate split across Visa and Mastercard cross-border, American Express Indian-issued, American Express abroad and Diners; the cumulative international GTV position against the ₹10 lakh promo cap with rupee headroom remaining for the month; a slab-misclassification exception list with rupee impact per flagged transaction; a forex conversion drag estimate computed against the acquirer reference rate; a refund-MDR non-recoverable cost line for the international book; a reconciled GST-on-MDR claim ready for GSTR-2B input tax credit; and an annual exposure number the controller can take to the board for the cross-border renegotiation or a switch to a multi-currency settlement structure.

### Inventory Valuation for Auto-Component Manufacturers under Ind AS 2

Source: https://www.terra-insight.com/insights/inventory-valuation-auto-component-ind-as-2-india/

- **Problem:** Auto-component Tier 1 inventory valuation under Ind AS 2 requires monthly cost-vs-NRV testing across thousands of WIP and finished-good SKUs, fixed-overhead absorption based on normal capacity (with unabsorbed portion expensed not capitalised), abnormal-waste exclusion above engineered standard yield (stamping skeleton, forging flash, casting melt-loss), and slow-moving NRV provision build for platform-cycle stock approaching programme end-of-life. A typical ₹180 crore casting Tier 1 closing month-end carries 2,400 active SKUs, 4 furnace cost centres, 12 machining cost centres, and a 14-bucket slow-moving ageing schedule — none of which a generic ERP costing module values together correctly.
- **Logic:** Apply Ind AS 2 layer by layer. Capitalise direct material at landed cost (LME/JPC index-linked plus customs, net of GST ITC). Capitalise direct labour at standard wage rate. Capitalise variable production overhead at actual rate and fixed production overhead at normal-capacity absorption rate. Exclude abnormal waste above engineered yield, storage costs, administrative overhead, and selling costs. Run cost-vs-NRV test per SKU at month-end. Apply slow-moving provision matrix by ageing bucket. Reconcile WIP movement at each cost centre against physical count quarterly.
- **Config:** SKU master with cost-layer tagging (direct material / direct labour / variable overhead / fixed overhead), normal-capacity baseline per cost centre updated annually, engineered standard-yield rate per process (stamping coil-to-part / forging billet-to-part / casting melt-to-part / machining stock-removal), abnormal-waste threshold formula, NRV reference per SKU (selling price minus costs-to-complete minus costs-to-sell), slow-moving ageing bucket matrix with provision rate per bucket, LME/JPC index feed for raw material cost layer.
- **Output:** A month-end inventory valuation register per SKU showing cost layers, NRV, lower-of-cost-or-NRV booked value, slow-moving provision applied, and reconciliation to physical count where applicable. A monthly fixed-overhead-absorption report showing actual vs normal capacity and the unabsorbed portion routed to P&L. An audit-defensible trail for the Schedule III Division II inventory disclosure and the statutory auditor's substantive testing.

### Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing

Source: https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india/

- **Problem:** Electronics manufacturers face an inverted duty structure where input GST (often 18%) exceeds output GST on certain finished goods (12% or 5%), accumulating unutilised ITC that requires periodic refund under Section 54 of the CGST Act and Rule 89 — with the Rule 89(5) formula restricting eligible ITC to inputs only (not input services or capital goods, per the 2018 and 2022 amendments upheld in VKC Footsteps), a 2-year time limit, and the FORM GST RFD-01 workflow with GSTR-2B matching as the critical rejection-avoidance discipline.
- **Logic:** Tag every SKU by its GST output rate; identify inverted-rated supplies where output rate is below input weighted average; build a monthly Net ITC pool restricted to inputs (excluding input services and capital goods per Rule 89(5)); apply the Rule 89(5) formula (Inverted_Turnover / Adjusted_Total_Turnover × Net_ITC − Tax_Payable_on_Inverted); file FORM GST RFD-01 with Annexure-B; reconcile each claim line to GSTR-2B; track the 2-year time limit and seek provisional refund under Section 54(6) for 90% within 7 days.
- **Config:** GST configuration with SKU master tagged by output rate, input invoice classification (input / input service / capital good), inverted-rated supply identification, Net ITC pool builder per Rule 89(5), Annexure-B builder for FORM GST RFD-01, GSTR-2B reconciliation against claimed ITC, 2-year time-limit dashboard, refund claim tracker with provisional and final disbursement stage.
- **Output:** A monthly inverted-duty refund cycle where the Rule 89(5) Net ITC pool is computed correctly excluding input services and capital goods, FORM GST RFD-01 ties to GSTR-2B-confirmed input invoices, claim lines without GSTR-2B match are excluded before filing, provisional refund is sought under Section 54(6), the 2-year time-limit dashboard surfaces aging claims, and the bank receipt closes each refund cycle against the original accumulated ITC pool.

### GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow

Source: https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation/

- **Problem:** Since October 2024, the GST IMS layer sits between GSTR-1 filing and GSTR-2B generation. Unactioned invoices in IMS create ITC gaps that may not surface until GSTR-3B filing.
- **Logic:** Compare purchase register invoices against IMS inbox. Classify each as accepted (flows to 2B), rejected (excluded from 2B), or pending (needs action). Cross-reference against GSTR-2B.
- **Config:** IMS action deadline before 14th of each month, GSTIN validation, invoice-level amount matching with tolerance ≤ ₹2, automatic acceptance rules for known suppliers.
- **Output:** IMS action queue, GSTR-2B gap analysis, ITC at risk from pending invoices, and supplier follow-up list for unactioned invoices.

### Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams

Source: https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india/

- **Problem:** Indian invoices are paid net of TDS, so a ₹1,00,000 invoice produces a ₹90,000 bank credit under Section 194J at 10%. Generic matching tools flag the ₹10,000 gap as an exception; 40–60% of professional services AR payments get mislabelled as variances every month.
- **Logic:** Match gross invoice = net bank credit + TDS receivable + any withheld fee. Apply section-level rate rules (1% or 2% for 194C, 10% for 194J, 2% for 194C technical, 5% for 194H commission) and flag cases where the deducted rate differs from the expected rate for correction request.
- **Config:** Vendor and customer master with expected TDS section and rate, partial-TDS allocation for mixed-taxable invoices, and section rate library aligned to the Income Tax Act.
- **Output:** Matched AR with explicit TDS receivable posting against Form 26AS, identified over-deductions queued for correction return, and a clean receivable ageing that no longer carries phantom variances.

### IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP

Source: https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india/

- **Problem:** A DRHP requires three years of restated financials with line-level reconciliation between originally reported and restated figures. Unreconciled TDS in Form 26AS, ITC gaps, intercompany balances, or pending GST demands surface as material disclosures, risk factors, or contingent liabilities and can delay SEBI approval.
- **Logic:** Start 12–18 months before filing, reconcile TDS receivable by TAN and section against Form 26AS for each of three years, match ITC claimed to GSTR-2B, clear intercompany balances between group entities, and produce a restatement reconciliation that explains every line-item difference.
- **Config:** Three-year rolling reconciliation workpapers, per-entity TAN and GSTIN registers, restatement-to-original crosswalks, and a related-party transaction ledger tied to the restated financials.
- **Output:** DRHP-ready restated financials, clean statutory auditor's report, a restatement reconciliation schedule, and a contingent-liability disclosure pack that withstands SEBI and merchant banker scrutiny.

### IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals

Source: https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india/

- **Problem:** IRDAI mandates 30-day claim settlement timelines, standardized claim forms, and grievance tracking through IGMS — hospitals must maintain audit trails proving compliance across hundreds of monthly claims.
- **Logic:** Track each claim against IRDAI settlement timeline (30 days from last document), log grievance resolutions via IGMS reference, validate claim form completeness, generate compliance reports.
- **Config:** Health Insurance Regulations 2024, 30-day settlement deadline, IGMS grievance system, standardized claim form fields, TPA registration validity.
- **Output:** IRDAI compliance dashboard with settlement timeline adherence, grievance resolution log, claim form completeness audit, and regulatory reporting package.

### IRDAI Insurance TPA Payout Reconciliation for Indian Hospitals

Source: https://www.terra-insight.com/insights/irdai-insurance-tpa-payout-reconciliation-india/

- **Problem:** IRDAI-regulated TPA payouts arrive as net credits with stacked deductions across non-payable items, room-rent proportionate cuts, co-pay, deductible, sub-limit caps, and query rejections. Hospitals that book the net amount without decomposing it lose the per-class audit trail needed for grievance escalation and the next empanelment rate revision.
- **Logic:** Ingest TPA explanation-of-benefits sidecar, tag every deduction line with an IRDAI deduction class code, separate regulatory-valid deductions (List I NPI, contractual sub-limits) from disputable deductions (List II/III misclassification, wrong proportionate base, query rejections with documentation), aggregate disputable totals per insurer for the grievance and empanelment workflows.
- **Config:** IRDAI deduction class taxonomy (NPI Lists I/II/III, room-rent proportionate base inclusion/exclusion rules, co-pay percentage by policy, deductible threshold, disease-specialty sub-limits, package rate cap per procedure code), TPA-specific MoU parameters (rate-card discount, package list, escalation contact), grievance ladder timelines (GRO 14 days, IGMS, Ombudsman).
- **Output:** Per-deduction-class payout decomposition, disputable amount register by insurer with grievance status, NPI misclassification log feeding into the next MoU rate revision, GST-exempt revenue and TDS receivable register for Section 393(1) Sl. 6(iii).D(b) / payment code 1027 reconciliation.

### Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel

Source: https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india/

- **Problem:** Indian integrated steel manufacturers procure ₹400-800 crore of iron ore and ₹300-500 crore of coking coal annually across a small set of large suppliers (NMDC, OMC, MOIL, CIL subsidiaries, merchant miners, importers). Every supplier easily crosses the ₹50 lakh per-PAN annual threshold for Section 393(1) Sl. 8(ii) buyer-side TDS (payment code 1031, 0.1%). The legacy Section 206C(1H) seller-side TCS on goods is functionally inapplicable since 1 April 2025 and is not carried forward in the Income-tax Act 2025, so only buyer-side TDS under code 1031 operates on the goods sale leg. The same procurement also runs a 5% input GST creating inverted-duty against 18% finished steel output and a Section 54(3) refund opportunity, plus a 30% export duty on iron ore exports keyed to the IBM grade classification.
- **Logic:** Build a per-vendor-PAN year-to-date purchase tracker on iron ore and coking coal in posting sequence; trigger Section 393(1) Sl. 8(ii) at 0.1% from the invoice that takes cumulative purchase above ₹50 lakh; deposit by 7th of following month under payment code 1031; track accumulated ITC against 5% input vs 18% output and file Section 54(3) refund quarterly; tag every iron ore export by IBM grade and apply the corresponding export duty rate; reconcile cross-era FY 2025-26 deductions filed under legacy 194Q against Form 26AS / Form 168.
- **Config:** Mineral vendor master keyed on PAN with prior-year buyer-turnover above ₹10 crore flag; Section 393(1) Sl. 8(ii) ₹50 lakh per-PAN annual threshold reset on 1 April; payment code 1031 default; legacy 194Q tag retained for cross-era; coal compensation-cess rate map (₹400/tonne where applicable); IBM iron ore grade classification with linked customs export duty rate; Section 54(3) inverted-duty refund tracker with Rule 89(5) formula; royalty rate map by state and mineral.
- **Output:** A monthly mineral procurement close showing per-vendor YTD purchase value (iron ore, coking coal, ferro-alloys), Section 393(1) Sl. 8(ii) deductions made under code 1031, deposits filed by the 7th, accumulated inverted-duty ITC against Section 54(3) refund file, IBM-graded iron ore export entries with applicable export duty, and any cross-era 194Q items still open for FY 2025-26.

### ITC-04 Filing for Auto-Component Manufacturers: A Step-by-Step Guide

Source: https://www.terra-insight.com/insights/itc-04-filing-auto-component-step-by-step-india/

- **Problem:** Auto-component principals — Tier-1 and Tier-2 suppliers — dispatch thousands of semi-finished parts every month to job-workers (platers, heat-treaters, machinists, painters, phosphaters), often in multi-hop sequence, on Section 143 delivery challans without GST against a one-year input return clock or three-year capital-goods clock; the quarterly ITC-04 must declare every Table-4 dispatch, every Table-5A return, every Table-5B supply from job-worker premises and every Table-5C inter-job-worker movement, reconcile to the principal's challan register and to GSTR-1, and surface any open balance approaching the statutory window — and a missed return triggers a retrospective deemed supply with 18% interest under Section 50.
- **Logic:** Stamp every Section 143 dispatch challan with job-worker GSTIN, process type, input or capital-goods flag, quantity and a one-year (or three-year) clock from the original principal dispatch date; track multi-hop parts on the single original clock across Table-5C inter-job-worker challans; match return GRN to dispatch on quantity within tolerance into Table 5A; flag Table-5B supplies from job-worker premises against GSTR-1; roll opening + dispatched − returned − supplied-from-premises = closing per job-worker per quarter; alert 60 and 30 days before the statutory window; cross-foot ITC-04 to the challan register before filing.
- **Config:** Job-worker master with GSTIN, PAN, process type and Section 393(1) Sl. 6(i) TDS rate (codes 1023 at 1% for individual/HUF, 1024 at 2% for other); challan series per principal GSTIN under Rule 45; statutory clock per challan (1 year inputs, 3 years capital goods, none for jigs/fixtures/moulds/dies); multi-hop routing map per part; quarter-end / half-year ITC-04 calendar by turnover band; Table-5B linkage to GSTR-1; cross-reconciliation rule to job-worker conversion-charge invoices in GSTR-2B; alert thresholds 60 and 30 days before the window.
- **Output:** A quarter-end ITC-04 pre-filing pack: Table-4 dispatches, Table-5A returns, Table-5B supplies from job-worker premises, Table-5C inter-job-worker movements, opening and closing balances per job-worker, reconciliation to the principal's challan register and to GSTR-1, a deemed-supply risk register listing every open balance within 60 days of the Section 143 window, and the JSON-ready upload file for the GST portal.

### ITC-04 Quarterly Return Reconciliation for Textile Job-Work

Source: https://www.terra-insight.com/insights/itc-04-quarterly-return-textile-job-work-reconciliation/

- **Problem:** Vertically integrated textile mills send grey fabric, yarn, and grey garments to external job-workers — dyers, printers, cutters, sewers — across regional clusters like Pali, Bhilwara, Tiruppur, and Surat under Rule 55 delivery challans. Each quarter, ITC-04 demands line-by-line reconciliation of goods sent versus goods received back at delivery-challan-serial-number granularity, with pending balances still within the 1-year window. Multi-hop chains where output of dyeing becomes input to printing which becomes input to cutting create identity-tracking failures — goods appear to double-count if the mill reports each hop separately, or disappear if the mill reports only the mill-to-first-hop leg. HSN mismatches between outbound and inward, missing challan numbers on return-inward invoices, and process-loss ambiguity accumulate through the quarter and surface as unreconcilable positions on the 25th filing day.
- **Logic:** Build a Section 143 job-work register keyed by delivery-challan serial number and date, with columns for goods description, HSN out, quantity out, taxable value, job-worker GSTIN, expected return date, and the 1-year anniversary. Parse the return-inward register from the goods-inward gate — each return challan carries a reference to the original delivery challan, HSN in, quantity in, and process-wastage line. Match each outbound challan to one or more return-inward postings by challan reference, allowing legitimate HSN transformation but flagging HSN clerical errors. For multi-hop chains, sequence the endorsed challan trail from mill to hop-1 to hop-2 to hop-3 back to mill, and reconcile end-to-end with the 1-year clock running from the original mill dispatch date. Roll pending balances forward with an aged ticker — 0-90 days (normal), 91-180 days (monitor), 181-270 days (escalate), 271-365 days (deemed-supply provision territory), 365+ days (retro-liability crystallised).
- **Config:** Delivery challan sequence with consecutive serial number, sender GSTIN, job-worker GSTIN, HSN, quantity, taxable value, dispatch date, expected return date, and 1-year anniversary; goods-receipt register from the mill's inward gate keyed by return-challan number referencing the original outbound challan; process-wastage tolerance per fabric type per job-worker; multi-hop endorsement trail linking hop-1 to hop-2 to hop-3; ITC-04 filing frequency flag (quarterly if turnover greater than ₹5 crore, half-yearly if ₹5 crore or lower); HSN transformation map (grey fabric HSN → dyed fabric HSN → printed fabric HSN → cut fabric HSN) so legitimate transformations do not raise reconciliation breaks; ageing bucket cutoffs (0-90 / 91-180 / 181-270 / 271-365 / 365+ days); Section 143 deemed-supply provision rule.
- **Output:** A quarterly ITC-04 reconciliation pack: goods sent in period (line-item detail per delivery challan), goods received back in period (matched to outbound challan with HSN transformation validated), goods pending with job-workers as of period-end (aged and colour-coded), and deemed-supply provision on the 365-plus bucket. A separate multi-hop chain report tracks endorsed challan sequences end-to-end with cumulative hop time. A process-wastage summary reconciles the outbound quantity to the sum of return-inward quantity plus documented wastage per line. Any HSN clerical errors and missing challan-reference numbers on return-inward invoices are surfaced as an exception queue for correction before the 25th filing day.

### ITC Clawback at Day 180 vs Day 181: Section 16(2) Second Proviso Boundary

Source: https://www.terra-insight.com/insights/itc-clawback-180-day-boundary-auto-oem-section-16-second-proviso-india/

- **Problem:** Section 16(2) Second Proviso of the CGST Act reverses input tax credit availed by a buyer if payment to the supplier is not made within 180 days from the invoice date. Day 180 is safe; Day 181 triggers formal reversal in GSTR-3B with interest at 18 percent per annum from the date ITC was originally availed. Auto component suppliers on 90 or 120-day OEM payment cycles operate close to this boundary constantly.
- **Logic:** For each supplier invoice on which ITC has been availed, calculate the 180-day boundary from invoice date. Track cumulative payments made against that invoice up to the boundary. If any amount remains unpaid on Day 181, reverse ITC proportional to the unpaid balance in the GSTR-3B for that tax period. When the balance is later paid, reclaim the reversed ITC in the GSTR-3B for the tax period of payment. Maintain a permanent register of reversals and re-availments — the interest cost between the original availment and the reversal date is not recoverable.
- **Config:** Invoice date as the anchor for the 180-day count (not invoice receipt date, not SAP posting date). Payment date is bank debit date, not cheque issue or NEFT initiation date. Proportional reversal for partial payments per CBIC Circular 170/2021-GST. Reversal reported in GSTR-3B Table 4(B)(2); re-availment in Table 4(A)(5). Interest computed under Section 50(3) at 18 percent per annum on the reversed amount from availment date to reversal date.
- **Output:** Invoice-level 180-day ageing register with columns for invoice date, ITC availed, cumulative payment, days outstanding at boundary, reversal amount, reversal GSTR-3B period, re-availment amount, re-availment GSTR-3B period, and interest cost. Feeds a monthly reversal preview report before GSTR-3B filing, and a year-end interest cost report for the tax audit.

### ITC Clawback on Partial Payment: Proportional Reversal — Not Full

Source: https://www.terra-insight.com/insights/itc-clawback-partial-payment-proportional-auto-oem-india/

- **Problem:** Auto OEMs frequently pay Tier-1 and Tier-2 supplier invoices in tranches — a portion at the acceptance stage and the balance withheld for retention, quality holds, or aggregated month-end release. When a portion remains unpaid at Day 181 from the invoice date, many finance teams reverse the entire ITC on the invoice, treating the Second Proviso to Section 16(2) as an all-or-nothing switch. This inflates the reversal amount by the ratio of paid-to-total and creates a working-capital hit that is legally unnecessary.
- **Logic:** Compute the unpaid portion of every open invoice at Day 181. Apply the invoice-level tax rate to only that unpaid portion to derive the ITC amount to reverse. Report the proportionate reversal in Table 4(B)(2) of GSTR-3B for the return period of the breach. When the buyer subsequently pays the balance, re-avail the ITC in Table 4(A)(5) with the reference in Table 4(D)(1). Match the re-availment to the delta payment (not the invoice) so the register stays tied to bank movements.
- **Config:** Ageing counter starts at invoice date, not GRN date or acceptance date; 180-day window applied to net-of-credit-note unpaid balance; retention amounts tagged and excluded from the reversal test unless they exceed the contractual warranty release window; buyer-issued debit notes ignored for reversal calculation unless mirrored by a supplier credit note; re-availment triggered by bank debit UTR, not by AP payment run.
- **Output:** Proportionate-reversal register showing invoice number, invoice date, invoice value, GST amount, paid-to-date, unpaid balance at Day 181, tax rate, proportionate ITC to reverse, Table 4(B)(2) reporting line, re-availment status, re-availment UTR, and Table 4(A)(5) reporting line. Register reconciles to GSTR-3B Table 4 on both the reversal and re-availment side for every return period.

### ITC Leakage under Rule 36(4): What Suppliers' GSTR-1 Filing Delays Cost You

Source: https://www.terra-insight.com/insights/itc-leakage-rule-36-4-gst-india/

- **Problem:** Indian recipients of B2B supplies face structural ITC leakage under Rule 36(4) of the CGST Rules because Input Tax Credit availability depends on supplier-side GSTR-1 filing flowing through the recipient's GSTR-2B. Suppliers who file late create lagged leakage with working-capital cost and Section 50 interest exposure; suppliers who never file create permanent leakage. Without a supplier-ageing workflow tied to the GSTR-1 filing calendar and the IMS dashboard, the recipient's GSTR-3B Table 4(A)(5) claim runs systematically below the procurement-side tax position, and the gap shows up as either an interest charge or a structurally written-off credit.
- **Logic:** Maintain a procurement ITC ledger keyed by supplier GSTIN, invoice number, taxable value, GST split, supplier filing cycle (monthly or quarterly), and expected GSTR-1 filing window. Daily-pull IMS data and weekly-pull GSTR-2B reflection per recipient GSTIN. Match every books-side ITC entry to its 2B counterpart. Age every unreconciled invoice in 5 / 20 / 45 / annual-return buckets keyed to the supplier's GSTR-1 deadline. Route each bucket to a specific recovery action. Track permanent vs lagged classification and feed the Discovered Money register on the tax-deduction class.
- **Config:** Procurement ITC ledger with supplier GSTIN, invoice number, taxable value, IGST / CGST / SGST split, supplier filing cycle, expected GSTR-1 window. IMS dashboard sync per recipient GSTIN. GSTR-2B reflection match-engine with primary keys on supplier GSTIN, invoice number, period and amount. Ageing buckets day-5, day-20, day-45, annual-return-deadline. Escalation playbook by bucket. Section 50 interest calculator keyed to original credit-availment date. Permanent vs lagged classifier. Audit trail for every reclassification.
- **Output:** A daily ITC-at-risk dashboard by supplier with rupee credit, days outside 2B reflection, and recovery probability. A weekly supplier-side escalation pack with GSTIN, period, and invoice-level detail. A monthly Section 50 interest-exposure projection. A quarterly permanent-vs-lagged leakage trend that feeds the audit committee. A standing recovery register tracking rupees in claim, rupees recovered, rupees structurally lost.

### ITC Recovery for Indian Businesses: Rule 36(4) Provisional ITC and Rule 37 Reversal Reclaim

Source: https://www.terra-insight.com/insights/itc-recovery-rule-36-4-rule-37-india/

- **Problem:** Indian finance teams routinely carry crores of provisional ITC at risk every month because suppliers under-file or mis-file GSTR-1, invoices mismatch on amount or place-of-supply, and the Rule 37 180-day payment clock trips quietly on slow-paid vendors. The recovery happens ad-hoc — someone chases suppliers when a number looks wrong, write-offs get taken at year-end, and DRC-01C notices land without supporting evidence. A structured monthly cycle with named owners, calendar-driven SLAs, and an at-risk register turns ITC recovery from a quarterly scramble into a standing tax-desk capability.
- **Logic:** Run a monthly cadence anchored to the GSTR-2B drop on T+13. Reconcile books ITC against 2B ITC and decompose the gap into four categories — missing invoice, amount mismatch, GSTIN mismatch, place-of-supply mismatch. Maintain a GSTIN-wise supplier filing dashboard with a defaulter list. Adopt the Invoice Management System for accept / reject / pending discipline. Operate a parallel Rule 37 watchlist that flags every ITC-claimed invoice unpaid at day 165. For provisional ITC unrecovered by T+45, post the reversal with Section 50 interest and track the reclaim entry. Maintain an at-risk register that holds every disputed line until it is recovered, reclaimed, or structurally lost.
- **Config:** T+0 to T+45 calendar with named owners (tax controller, AP controller, supplier-relations lead). GSTIN-wise supplier filing dashboard with on-time / delayed / defaulter status. IMS daily review queue. Four-category mismatch resolution playbook. Rule 37 day-165 watchlist with weekly tax-desk review. DRC-01B and DRC-01C response templates. ITC at-risk register with status field (chased, accepted, rejected, reversed, reclaimed, structurally lost). Monthly tax-committee pack and quarterly audit-committee feed.
- **Output:** A monthly ITC at-risk register decomposing the provisional ITC pool by category and supplier. A weekly defaulter list driving supplier escalation. A Rule 37 watchlist driving on-time vendor settlements. A monthly reversal-and-reclaim journal posted with regulator-aligned narration. A quarterly tax-committee pack showing ITC recovered, ITC in pipeline, ITC structurally lost, and Section 50 interest avoided.

### ITC Reversal Under Rule 42 and 43: How the Calculation Works

Source: https://www.terra-insight.com/insights/itc-reversal-rule-42-43/

- **Problem:** Rule 42 apportions common ITC between taxable and exempt use using monthly turnover ratios, while Rule 43 spreads capital-goods ITC over 60 months — any classification error into T1/T2/T3/T4 pools understates the reversal in GSTR-3B Table 4(B) and creates a year-end shock when the actual annual ratio is computed in GSTR-9.
- **Logic:** Every inward invoice is classified into T1 (taxable-only), T2 (exempt-only), T3 (blocked under Section 17(5)), or T4 (common) using vendor, cost-centre, and use-code mappings. D1 is computed as T4 times (exempt turnover divided by total turnover) each month; D2 is 5% of T4 for non-business use. Capital-goods ITC is spread at one-sixtieth per month and the same exempt ratio is applied on that slice for Rule 43.
- **Config:** Classification ruleset (vendor plus HSN plus cost-centre), monthly turnover ratio auto-computed from GSTR-1, capital-goods amortisation schedule with 60-month tracker, and year-end true-up using the actual annual ratio.
- **Output:** Monthly Table 4(B)(1) reversal figure, capital-goods 60-month amortisation ledger, GSTR-9 annual true-up worksheet showing provisional versus actual, and a reclaim or top-up entry for the March 3B.

### Mixed-Rate Jewellery Invoice Reconciliation: 3% + 5% + 18% GST on One Bill

Source: https://www.terra-insight.com/insights/jewellery-gst-tax-mixed-invoice-3-5-18-percent-reconciliation-india/

- **Problem:** A single retail jewellery invoice in India routinely carries three or four GST rates simultaneously — gold or silver at 3% under HSN 7113, making charges at 5% under the job-work entry of Notification 11/2017-CTR, diamond or precious-stone value at 0.25% under HSN 7102/7103, and ancillary items (presentation box, die, safety plate, security clasp) at 18% under general HSN codes. The customer-facing bill must show the split, the GSTR-1 filing must aggregate line-by-line into distinct tax-rate rows, the GL must recognise revenue and cost of goods sold across the same split, and Section 54(3) inverted-duty refund calculations must partition ITC between the 3% output supply and the 18% ancillary output supply. Retailers who blend rates informally over- or under-collect GST, misfile GSTR-1, and either lose the inverted-duty refund or invite a Section 74 audit notice at year-end.
- **Logic:** Build a line-item classifier that assigns each invoice line to one of four rate buckets — 3% (jewellery HSN 7113 or silver), 5% (making charges as job-work services), 0.25% (diamond and precious stones HSN 7102/7103), and 18% (packaging, dies, safety plates, general HSN 7326 or 4819). Classify each ancillary line as either naturally bundled (composite supply, taxed at principal-supply rate 3%) or independently sellable (mixed supply, taxed at highest rate 18%) per Section 2(30) and Section 2(74). Aggregate lines into GSTR-1 tax-rate rows and reconcile against the trial-balance revenue by HSN. Split ITC on 18% inputs between goods used commonly for taxable and exempt supplies (Section 17(5)) and goods contributing to inverted-duty structure (Section 54(3) refundable). Cross-foot output tax collected to GSTR-3B output tax liability before month-end close.
- **Config:** Item master with HSN code, rate flag (3% / 5% / 0.25% / 18%), composite-bundle indicator, and BIS HUID capture where applicable; making-charges service line with SAC code and 5% rate; diamond master with certification (IGI/GIA/HRD) reference and per-carat value; packaging and die master with 18% rate and Section 17(5) or 54(3) attribution flag; scheme master for discount treatment under Section 15(3); customer master with GSTIN (for B2B) and PAN (for jewellery above ₹2 lakh cash-consideration reporting under Rule 114B); karigar master with PAN and Section 393(1) Sl. 4 (194C) TDS rate flag; old-gold exchange indicator with unregistered-customer default and registered-customer alternate path.
- **Output:** A monthly reconciliation pack: invoice-level tax-rate split by 3%, 5%, 0.25%, and 18%, aggregated to GSTR-1 tax-rate rows; GL revenue reconciliation by HSN with variance tolerance per line; ITC reconciliation split between fully utilisable (18% ancillary output supply), inverted-duty refundable (18% inputs against 3% jewellery output), and Section 17(5) restricted; Rule 89(5) refund working with turnover of inverted-rated supply, net ITC, and adjusted total turnover; karigar labour TDS reconciliation at Section 393(1) Sl. 4 rate against Form 26AS; per-invoice audit trail showing composite versus mixed classification and Section 15(3) discount treatment on old-gold exchange.

### Eighteen Jewellery Reconciliation Scenarios Indian Auditors Actually Ask About

Source: https://www.terra-insight.com/insights/jewellery-reconciliation-scenarios-india-18-audit-defensible-cases/

- **Problem:** Indian jewellery retailers face eighteen legally distinct reconciliation surfaces on top of every operating month — mixed-rate retail invoices, gold-versus-making classification, karigar labour under Section 393(1) Sl. 4, purchase of finished goods under Sl. 8, franchise royalty under Sl. 15, distributor commission under Sl. 18, metal loans with delivery-day price fixation, old-gold exchange under Section 15(3), gold-scheme customer deposits, hallmarking pass-throughs, damaged returns under Section 34, EMI-scheme revenue recognition, wastage and manufacturing loss, gold-scrap RCM under Section 9(4), bullion versus retail supply classification, stone-and-diamond studding under HSN 7102/7103, export partial realisation under FEMA with EEFC treatment, and wedding-purchase PAN capture under Rule 114B. Each scenario has a distinct regulatory anchor, a distinct audit question, and a distinct reconciliation control. Retailers who treat them as one blur under-reconcile every one; retailers who name and separate the eighteen build audit trails that survive Section 74 assessment.
- **Logic:** Build a scenario classifier that reads every source transaction (POS invoice line, karigar bill, bank statement narration, franchise remittance, export shipping bill, gold-scheme deposit ledger entry, damaged-return docket, EEFC credit) and assigns it to one or more of the eighteen scenarios by inspecting HSN or SAC code, counterparty type, consideration amount, TDS applicability, GST rate class, FEMA relevance, and PAN capture requirement. For each assigned scenario, route the transaction through the scenario-specific reconciliation control — mixed-rate invoices reconcile to GSTR-1 tax-rate rows; karigar labour reconciles to Form 26AS at Sl. 4 code 1001/1023; metal loans reconcile to bank statement UTR at delivery-day price; old-gold exchange reconciles to Section 15(3) discount log; franchise royalty reconciles to Sl. 15 code 1005 Form 26AS entry; export partial realisation reconciles to EDPMS + EEFC + shipping bill triangle. Cross-scenario transactions (a wedding invoice with old-gold exchange and karigar labour above the Rule 114B PAN threshold) hit multiple controls concurrently and must reconcile clean across all of them.
- **Config:** Item master with HSN/SAC code, rate class (3% / 5% / 0.25% / 18%), composite-bundle indicator, and BIS HUID field. Counterparty master with type (retail customer / karigar / franchisee / bank / export buyer / unregistered seller / gold-scheme depositor), PAN, GSTIN, Section 393 Sl. classification, and Rule 114B threshold flag. Scheme master for EMI, gold deposit, and franchise revenue recognition. Metal-loan master with delivery-day and fixation-day price fields, bank counterparty, and interest rate. Export master with shipping bill number, EDPMS reference, EEFC account link, FEMA realisation timeline flag, and partial-realisation write-off rule. Damaged-return master with Section 34 credit-note window tracking. Gold-scrap RCM flag for Section 9(4) inward supply. Franchise royalty percentage and Sl. 15 code 1005 TDS rate. Distributor commission percentage and Sl. 18 code 1015 TDS rate.
- **Output:** A monthly reconciliation pack that answers all eighteen audit questions with source-document traceability: invoice-level HSN split reconciling to GSTR-1 tax-rate rows; karigar payment ledger reconciling to Sl. 4 TDS deposit and Form 26AS at karigar PAN; metal-loan settlement register reconciling to bank statement UTR at delivery-day fixation; old-gold exchange log with Section 15(3) discount treatment against the outbound invoice; export realisation triangle across EDPMS + EEFC + shipping bill with FEMA timeline compliance; wedding-invoice register above ₹2 lakh with Rule 114B PAN capture; franchise royalty register with Sl. 15 TDS at 10% and Form 26AS reconciliation; scrap-purchase RCM register under Section 9(4) with ITC availment; damaged-return register with Section 34 credit-note dates and GSTR-1 amendment status. Exception list surfaces before return filing, not after audit lands.

### JLR and Tata Motors: Reconciliation for Suppliers Selling to Both Domestic PV and Export Programmes

Source: https://www.terra-insight.com/insights/jlr-tata-motors-domestic-vs-export-supplier-reconciliation/

- **Problem:** A single Indian Tier-1 supplying both Tata Motors PV (Nexon / Harrier / Safari / Curvv / Punch / Tiago / Tigor / Altroz) and JLR Sourcing India (export for JLR UK Solihull / Halewood and Slovakia Nitra plants) runs two entirely parallel commercial universes inside one customer master. Domestic INR under TML SRM portal flow with Section 393 TDS, Section 34 GST credit-note timing and standard Indian Tier-1 commercial terms. Export EUR / GBP under LUT bond, GSTR-1 Table 6A submission, RoDTEP claim filing, EPCG capital-goods discipline, IEC registration, VDA-format EDI translation, and a separate PLI eligibility computation segmented domestic vs export. The reconciliation engine that blends the two loses recoverable revenue on both sides — RoDTEP claims lapse, EPCG export obligation slips, PLI segmentation fails audit.
- **Logic:** Decompose every transaction into the domestic INR sub-ledger (Tata Motors PV) or the export EUR / GBP sub-ledger (JLR Sourcing India), tie each transaction to the source vehicle programme on both sides (Nexon / Harrier / Safari / Curvv on Tata; Range Rover Sport / Defender / Discovery / F-Pace / E-Pace on JLR programmes via Solihull / Halewood / Nitra), maintain LUT bond utilisation register on the export leg with each export invoice matched to a shipping bill, file and track RoDTEP claims against each export shipment via ICEGATE, maintain EPCG export-obligation progress register against the six-year obligation window, track PLI eligibility segmentation between AAT-approved and non-AAT sales with domestic and export carved separately, reconcile VDA-format EDI translation variance, and split the Form 168 TDS register between domestic Section 393 deductions and the supplier's outgoing Tier-2 Section 393 register on the Tier-2 leg that supports both domestic and export production.
- **Config:** Customer master with separate parent records for Tata Motors PV (TML SRM portal flow) and JLR Sourcing India (export-Tier-1 flow), VDA EDI middleware for JLR export messages translated to and from Indian Tier-2 conventions, LUT bond register with utilisation tracking, GSTR-1 Table 6A export-invoice register matched against shipping bills, RoDTEP claim register tied to ICEGATE filing references, EPCG capital-goods register with export-obligation progress, IEC registration reference, PLI eligibility register segmented by AAT-approval status and by domestic vs export, Form 168 TDS register split between domestic Tata-deducted (Section 393) and the supplier's outgoing Tier-2 Section 393 register, Section 34 GST credit-note calendar on the domestic leg, currency revaluation discipline at close on the export receivables ledger.
- **Output:** A dual-ledger view — domestic Tata Motors PV settlement decomposed per programme with debit / credit reason coding under standard Indian Tier-1 discipline, and JLR Sourcing India export settlement reconciled against LUT bond utilisation, GSTR-1 Table 6A submissions matched to shipping bills, RoDTEP claims filed and credited, EPCG export-obligation progress, PLI eligibility segmentation, VDA translation variance, and currency revaluation on the EUR / GBP receivables at quarter close. Form 168 TDS register reconciled per leg. Section 34 GST credit-note action queue on the domestic leg.

### Jeweller Buying Goods and Giving Job-Work: Section 194C vs 194Q Trap

Source: https://www.terra-insight.com/insights/job-work-gold-jewellery-section-194c-vs-194q-classification-india/

- **Problem:** Indian jewellers routinely transact with the same counterparty — a bullion dealer, a karigar workshop, or a hybrid supplier — under two economically distinct flows in the same month: buying gold bar or finished-goods inventory under a purchase order, and sending out gold under a job-work challan for making. The Income-tax Act 2025 sharply splits the TDS treatment — 0.1 percent under Section 393(1) Sl. 8 (legacy 194Q, code 1031) on the purchase leg above ₹50 lakh aggregate, versus 1 percent or 2 percent under Section 393(1) Sl. 4 (legacy 194C, codes 1001 / 1023) on the making leg above the ₹30,000 / ₹1,00,000 threshold. Mixed invoices, unflagged vendor masters, and default TDS rules routinely apply the 0.1 percent goods rate to the making-charge portion, silently short-withholding by a factor of 10 or 20. On a ₹6 lakh mixed monthly envelope the short-withhold is ₹4,500 to ₹9,500; scaled to 200 karigars and 12 months, the annual gap crosses ₹50 lakh — sitting as the jeweller's own liability under Section 415 (successor to 201) with 1 percent per month interest and possible penalty.
- **Logic:** Build a per-counterparty flow map that separates the goods-purchase flow from the job-work flow at the source document. Every purchase order for bullion or finished goods enters the goods register with HSN 7108 or 7113 and 3 percent GST; every job-work challan enters the job-work register with GST heading 9988 at 5 percent on the making-charge line. The TDS engine reads the vendor master (bullion supplier / karigar / mixed counterparty), the source document type (PO / job-work challan), the PAN category (individual-HUF / other), and applies the correct code: 1031 at 0.1 percent for goods purchase leg above the ₹50 lakh aggregate; 1001 at 1 percent for individual-HUF karigar or 1023 at 2 percent for other resident karigar on the making leg. Mixed invoices are refused at the AP gate and returned for two-line billing. At quarter-end, the challan-out register is reconciled to the challan-back plus making-charge invoice register — un-returned challans are either work-in-progress (still 194C) or disguised sales (now 194Q) and disposition before the 27Q / 26Q filing.
- **Config:** Vendor master flags — bullion supplier / karigar / mixed counterparty / PAN category (individual-HUF / other); source document types — purchase order versus job-work challan with distinct numbering series; HSN and GST rate rules — 7108/7113 at 3 percent for gold, 9988 at 5 percent for job-work; TDS code map — code 1031 at 0.1 percent for legacy 194Q (Section 393(1) Sl. 8), code 1001 at 1 percent for legacy 194C on individual-HUF (Section 393(1) Sl. 4), code 1023 at 2 percent for legacy 194C on other resident deductees; threshold aggregation windows — ₹50 lakh per seller per FY on the goods leg, ₹30,000 single credit / ₹1,00,000 aggregate per FY on the works-contract leg; quarter-end challan-out versus challan-back reconciliation with WIP ageing buckets; TCS override rule under Section 206C(1H) mutual precedence.
- **Output:** A month-end and quarter-end jewellery TDS reconciliation pack: per-counterparty split of goods-purchase leg versus job-work leg, per-PAN cumulative aggregation against the two thresholds, TDS deducted per payment code, challan-out versus challan-back register with WIP ageing, and rectification worksheet for any leg mis-classified in the current or prior quarter. The pack feeds Form 27Q / 26Q filing, cross-foots to Form 26AS at PAN-counterparty level, and supports the year-end statutory audit and Section 415 (legacy 201) inquiry defence if the department challenges the split.

### Joint Business Plan (JBP) Modern Trade Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/joint-business-plan-jbp-modern-trade-fmcg/

- **Problem:** The JBP commits an FMCG brand to four distinct flows with a modern trade chain — minimum off-take, BTL co-investment, listing-fee structure, and a BTL activity calendar — but each clears through a different ledger on a different cadence. Off-take is measured in dispatch volume; BTL spend sits in the marketing GL; listing fees are chain-initiated debit notes; and the quarterly volume-tier rebate sits as an accrual that only settles at the year-end true-up. Without per-JBP per-quarter reconciliation, brands carry an unresolved trade-spend balance into the year-end true-up call where the chain holds negotiating leverage, mis-classify BTL co-investment and excess-rebate against Section 15(2) CGST treatment, and lose 4 to 8 percent of the JBP's commercial value to leakage, mis-debited listing fees, and stuck rebate claims.
- **Logic:** Build a per-JBP master keyed by chain code, FY, and SKU/category coverage that carries four registers — off-take commitment ladder, BTL co-investment commitment, listing-fee schedule, and BTL activity calendar — each with a Section 15(2) treatment flag. On a quarterly cycle, parse actual off-take from the dispatch register, actual BTL spend from the marketing GL with chain references, actual listing-fee debits raised by the chain, and the chain's settlement statement. Match each actual line to its JBP commitment line; compute the quarterly volume-tier rebate earned, the BTL co-investment balance owing in either direction, and the listing-fee variance. Surface the cumulative balance per chain per JBP after each quarter, with ageing on stuck rebate claims and disputed listing-fee debits. At year-end, run the JBP true-up — convert the cumulative balance into either an excess-rebate credit note (Section 34 within 30 November) or a short-fall penalty journal.
- **Config:** JBP master per chain per FY with: minimum off-take ladder by SKU or category, quarterly milestones, volume-tier rebate slabs, BTL co-investment commitment per quarter, listing-fee schedule per SKU per cluster with debit cadence, BTL activity calendar with named promotions, and Section 15(2) treatment flag per flow. Dispatch feed by chain by SKU by period from the brand's order-to-cash system. Marketing GL feed by chain BTL cost centre. Chain debit-note feed for listing fees with debit reference and dispute window. Chain settlement-statement parser for the quarterly true-up. Pre-22-September 2025 versus post-22-September 2025 rate effective-date field on every JBP flow. Year-end true-up rule per JBP — short-fall penalty mechanic or excess-rebate credit-note path.
- **Output:** A per-JBP quarterly reconciliation pack: off-take actual versus committed with slab attainment, BTL spend actual versus committed, listing-fee debits raised versus scheduled, volume-tier rebate accrued, and chain settlement-statement reconciliation. Per-chain ageing on stuck rebate claims and disputed listing-fee debits. A Section 15(2) treatment register per JBP flow feeds the credit-note cycle. The year-end true-up output is either an excess-rebate credit-note batch with Section 34 timing, or a short-fall penalty journal with the next-FY JBP renegotiation note attached.

### Joint Property Buyers and Section 194IA: Why TDS Still Applies on Split Payments

Source: https://www.terra-insight.com/insights/joint-buyer-property-tds-194ia-aggregation-india/

- **Problem:** Indian residential property transactions with joint buyers routinely miscompute Section 194IA TDS by treating each buyer's individual share as a separate threshold test — if each buyer is under ₹50 lakh they skip Form 26QB entirely — while CBDT Circular 07/2017 clarifies unambiguously that the threshold is a property-level test on aggregate consideration and every co-owner must deposit TDS proportional to their share once aggregate consideration crosses ₹50 lakh; the defect leaves the seller unable to reflect the credit in Form 26AS and exposes the buyers to interest under Section 201(1A) and penalty under Section 271C.
- **Logic:** Test the ₹50 lakh threshold on aggregate consideration for the immovable property irrespective of the number of transferees or transferors; where aggregate crosses ₹50 lakh, every buyer files a separate Form 26QB for every seller for their proportional share, remits TDS at 1% of their share within 30 days from end of the month of deduction under Rule 30(2A), and issues Form 16B to the seller; reconciliation ties sale deed consideration through the Form 26QB grid to Form 16B and back to seller Form 26AS credit trail.
- **Config:** Property transaction master keyed by immovable property with aggregate consideration, list of co-owner buyers with PAN and share %, list of co-owner sellers with PAN and share %; Form 26QB grid computed as (buyers × sellers) with per-cell consideration attribution and 1% TDS; Rule 30(2A) 30-day payment calendar; Form 16B download tracker with TRACES receipt; seller-side Form 26AS credit trail tied to the aggregate transaction; interest calculator under Section 201(1A) for missed windows.
- **Output:** A per-transaction Form 26QB grid showing buyer-seller-share-TDS-status-challan-Form-16B for every cell, a rolled-up view of aggregate consideration vs cumulative TDS deposited, a Rule 30(2A) due-date monitor for TDS payment, and an audit-ready evidence pack per property that ties sale deed × Form 26QBs × Form 16Bs × seller Form 26AS in a single reconciled report.

### JPC Steel Price Index for RMPV Claims: A Tier-1 Auto-Component Supplier Guide

Source: https://www.terra-insight.com/insights/jpc-steel-price-index-rmpv-auto-india/

- **Problem:** Tier-1 auto-component suppliers running steel-content RMPV claims against OEM contracts that name JPC as the reference index must reconcile grade mismatch (JPC publishes HRC/CRC but suppliers consume E34/IF/BH auto-specific grades), city-base ambiguity (ex-Mumbai vs ex-Delhi), publication lag (15-day delay after month-end), and Section 34 cutoff exposure on downward claims. Errors create OEM disputes, lost margin, and mis-timed GST events.
- **Logic:** Map every steel-content part to the closest published JPC grade at programme award with a grade-premium adjustment held fixed. Apply the contractual city base (ex-Mumbai for western India, ex-Delhi for north); resolve ambiguity via BOM match → location → escalation panel. Run the standard RMPV formula: Claim = (JPC_Current − JPC_Base) × Material_Weight × Quantity × Adjustment_Factor. Apply the contractual averaging method (monthly, three-month moving, quarter-end spot) to JPC values. Book Ind AS 37 provision at quarter-end on observed movement; true up on JPC publication. Route upward claims to supplementary invoice, downward to Section 34 credit note within cutoff.
- **Config:** Part master row per steel-content part carrying material grade, JPC reference grade with grade-premium, city base, base JPC level, averaging method, trigger band. JPC monthly feed by grade and city. Quantity-supplied feed by revision period per OEM. Quarter-end provision ledger with Ind AS 37 booking. GST routing splitting upward vs downward with Section 34 cutoff watch. Grade-premium escalation panel records.
- **Output:** Per-claim worksheet showing JPC reference grade and city base used, base and current JPC values, applied averaging method, grade-premium adjustment, computed differential, rupee claim, GST treatment (supplementary invoice or Section 34 credit note), Ind AS 37 provision-vs-actual true-up, and Section 34 cutoff watch flag.

### Juspay Orchestration Fees: Why It's Not an MDR Layer (and How to Reconcile)

Source: https://www.terra-insight.com/insights/juspay-orchestration-fees-not-mdr-india/

- **Problem:** A multi-gateway merchant runs Juspay as the orchestration layer in front of Razorpay, PayU and Cashfree. The Juspay invoice arrives as a fixed per-transaction fee plus AMC, while each underlying gateway's settlement file separately deducts MDR plus GST on MDR. Treating Juspay's fee as an MDR component double-counts cost; netting it against gateway MDR breaks the per-instrument effective-rate calculation; and conflating Juspay's fee with routing savings hides where the real economics come from.
- **Logic:** Carry Juspay fees as a separate ledger line distinct from instrument MDR. Reconcile each underlying gateway's settlement file on its own — settlement ID against bank UTR, per-instrument MDR against contract, GST on MDR for ITC — then ingest the Juspay invoice separately and match its per-transaction count to the sum of successful transactions across all routed gateways for the same period. Build a combined effective cost-per-transaction view by adding Juspay fee plus weighted-average gateway MDR plus GST, never by folding Juspay into the MDR percentage.
- **Config:** Juspay invoice ingestion at per-transaction granularity, routing-decision log mapping each payment ID to the gateway it was sent to, separate per-gateway settlement reconciliation pipelines for Razorpay, PayU, Cashfree and any other PAs on the orchestration network, and a combined effective-rate dashboard that decomposes total cost into routing fee, gateway MDR, GST on MDR and GST on routing fee.
- **Output:** Reconciled Juspay invoice with per-transaction count matched to gateway settlement counts, per-gateway MDR variance flagged against contracted rates, GST on both Juspay fee and gateway MDR booked separately as ITC-eligible expense, and a management view that attributes savings to ROUTING (rail selection) versus underlying gateway negotiation versus orchestration fee — three distinct levers that a single blended number conceals.

### Joint Venture (JV) Real Estate Reconciliation for Indian Developers

Source: https://www.terra-insight.com/insights/jv-joint-venture-real-estate-reconciliation-india/

- **Problem:** An Indian developer running a JV project with a landowner — whether area-share, revenue-share, or profit-share — operates two principals' books simultaneously, with GST Section 9(3) RCM on the landowner's transfer of development rights, deemed-supply GST on the developer's transfer of constructed area to the landowner, Section 393(1) Sl. 3(i) code 1010 TDS on revenue-share consideration above ₹50 lakh, transfer pricing under Section 92 for related-party JVs, and RERA joint-promoter or sole-promoter classification driving escrow control — none of which a generic project-cost ledger handles without explicit JV configuration.
- **Logic:** Reconcile the JV by maintaining a JV-master that classifies the structure (area-share / revenue-share / profit-share), tracking landowner's development rights transfer as RCM liability in GSTR-3B 3.1(d), valuing developer's deemed-supply of constructed area at open-market value and booking output GST, applying Section 393(1) Sl. 3(i) code 1010 on revenue-share payments above ₹50 lakh per landowner per year, maintaining the Form 3CEB transfer-pricing pack for related-party JVs, and aligning RERA escrow control to joint-promoter or sole-promoter status.
- **Config:** JV master keyed by RERA registration with structure type, landowner PAN and entity classification, sharing ratio, area-share split or revenue-share percentage, related-party flag; cost ledger tagged to JV project; landowner development-rights RCM liability register tied to JDA notification rates; deemed-supply output GST register tied to handover trigger; Section 393(1) Sl. 3(i) code 1010 deduction register on revenue-share payments; Form 3CEB transfer-pricing documentation library for related-party JVs.
- **Output:** A per-JV close pack showing landowner's share computed in the agreed structure, RCM liability on landowner's development-rights transfer reflected in GSTR-3B 3.1(d) and ITC claim in 4(A)(3), deemed-supply output GST on developer's transfer of constructed area, Section 393(1) Sl. 3(i) code 1010 TDS on revenue-share payments, transfer-pricing documentation pack for related-party JVs, and the RERA joint-promoter or sole-promoter escrow control reconciled to the bank statement.

### Kanban vs MRP-Based Delivery: How the Supply Model Affects Auto-Component Reconciliation

Source: https://www.terra-insight.com/insights/kanban-vs-mrp-delivery-reconciliation-auto-india/

- **Problem:** Kanban supply at Indian OEMs — Hyundai, Maruti Suzuki, Toyota Kirloskar, Bosch as a system supplier — runs on pull-based line-side replenishment with no advance ASN, no per-shipment call-off, and settlement against monthly OEM consumption reports rather than receipt. Finance teams that treat kanban supply with MRP logic miss the consigned-stock liability sitting at the OEM premises, over-recognise revenue on dispatch rather than consumption, and break the GST e-invoice cycle because the supply event under GST is consumption from the consignment stock, not dispatch from the supplier dock.
- **Logic:** Treat the kanban supply chain as four distinct financial events: dispatch from supplier dock under Rule 55 delivery challan (no tax invoice, no revenue), receipt into consigned stock at OEM premises (supplier-owned inventory, no control transfer), consumption at the OEM line (control transfer under Ind AS 115, revenue recognised), and periodic GST e-invoice consolidating consumed quantity for the billing window (tax-invoice event, output GST, Section 393(1) Sl. 8(ii) TDS base). Maintain a daily consigned-stock register at the OEM end keyed by part code and plant code. Tie the monthly consumption report to dispatch and to billing as the canonical match.
- **Config:** Customer master with kanban-flag per part-plant combination, consigned-stock register at the OEM end, Rule 55 delivery-challan generator for dispatch movement, OEM monthly consumption report ingester, periodic GST e-invoice against consumed quantity (not dispatch), Section 393(1) Sl. 8(ii) TDS base on conversion portion of consumption-based invoice, consigned-stock balance dashboard for month-end audit.
- **Output:** A kanban-aware reconciliation pack showing dispatch via delivery challan to consigned-stock register to OEM monthly consumption to periodic GST e-invoice. Consigned-stock balance reconciled to supplier inventory register and to OEM-confirmed stock at month-end. Section 393(1) Sl. 8(ii) TDS deducted at consumption-based invoice value reconciles to Form 26AS. Ind AS 115 revenue recognised at consumption event, not at dispatch.

### Karigar / Workshop Labour TDS Reconciliation for Jewellers

Source: https://www.terra-insight.com/insights/karigar-workshop-labour-tds-section-194c-code-1001-jewellery/

- **Problem:** Indian jewellery manufacturers and retailers pay hundreds of individual karigars for skilled making labour across their workshop network, and each per-piece payment is a small amount — well below the ₹30,000 single-invoice trigger. But over a financial year, cumulative payments to the same karigar routinely cross the ₹1,00,000 aggregate threshold under Section 393(1) Sl. 4 (legacy 194C) of the Income-tax Act 2025, at which point TDS at 1 percent (payment code 1001 for Individual or HUF) must be deducted on the crossing payment and every subsequent payment in that FY. Jewellers running piecework payments through cash memos or piece-rate tickets without a per-PAN cumulative tracker routinely miss the crossing, under-remit TDS, and face Section 201(1A) interest, Section 40(a)(ia) disallowance, and Section 271C penalty exposure.
- **Logic:** Maintain a karigar master keyed by PAN with constitution (Individual/HUF versus other), deduction rate (1% code 1001 or 2% code 1023), classification memo (contractor under 393(1) Sl. 4 versus employee under Section 192), and workshop location. For every payment cycle, insert the payment into the karigar's cumulative running total for the FY. Check two triggers on each insert: single-payment above ₹30,000 (immediate deduction on that payment), or new cumulative crossing ₹1,00,000 (deduction on the crossing payment applied to the full payment amount). Once either trigger fires, deduct at the karigar's coded rate on the crossing payment and continue deducting on every subsequent FY payment. Cross-foot the deductor's running total to the challans deposited under Section 200 and to the Form 26AS credit appearing at the karigar's PAN — a quarterly cross-foot before Form 26Q filing catches deduction misses before the return is filed.
- **Config:** Karigar vendor master with PAN, constitution (Ind/HUF/Firm/LLP/Company), TDS rate code (1001 or 1023), classification memo (contractor vs employee) with employment-indicia checklist, workshop address, and bank details. Per-FY running aggregate register keyed to PAN. Threshold configuration (₹30,000 single-payment, ₹1,00,000 FY aggregate). Payment feed from the making-charge accounting system with karigar PAN, invoice/piece-ticket reference, payment date, gross amount, TDS deducted, and net paid. Challan register (Section 200 deposits) mapped by TAN and section code. Form 26Q filing calendar (quarterly). Form 26AS reconciliation feed at the karigar's PAN and at the jeweller's TAN. Vendor-master classification review calendar (start of each FY).
- **Output:** A quarterly karigar TDS reconciliation pack: per-karigar running aggregate as of quarter-end, threshold-crossing register (karigars who crossed ₹30,000 single-invoice or ₹1,00,000 aggregate in the quarter), TDS deducted versus TDS deductible (variance flag), challans deposited under the deductor's TAN, and 26AS credit reflected at each karigar's PAN. A classification exception list flags karigars whose payment pattern (frequency, fixed monthly amount, PF/ESI coverage) has drifted toward employment substance and warrants re-classification to Section 192. Year-end pack feeds Form 26Q Q4 filing, the Section 40(a)(ia) disallowance schedule, and any Section 201(1A) interest deposit for missed deductions caught in the year-end sweep.

### Kaveri Seed Bt Cotton Trait-Fee Reconciliation India

Source: https://www.terra-insight.com/insights/kaveri-seed-bt-cotton-trait-fee-reconciliation-india/

- **Problem:** A Hyderabad-headquartered listed hybrid-seed producer with Bt cotton hybrids representing roughly 30 to 40 percent of segment turnover across FY 2016-17 to FY 2020-21 must reconcile a Bollgard II trait-fee accrual to the non-resident technology licensor against a state-notified Maximum Retail Price cap set by the Maharashtra Cotton Seed Price Control Committee from 2015-16 onwards and by Gujarat, Andhra Pradesh, and Telangana under parallel notifications, discharge Section 195 TDS on the cross-border royalty under the India-United States Double Taxation Avoidance Convention Article 12, comply with the Section 43B(h) 45-day MSME rule on grower buy-back invoices arising from grow-out plot contract cultivation, maintain Rule 10D transfer-pricing documentation where the licensor is an associated enterprise, and file a Section 54(3) refund of unutilised ITC under the nil-rated (exempt) supply category because HSN 1209 seed for sowing carries a 0 percent output rate against 18 percent packaging and lab-testing input GST. Manual reconciliation across five simultaneous surfaces — trait-fee-per-packet accrual, state MRP register, TDS-treaty withholding, MSME grower-payment aging, and nil-rated ITC refund — under-recovers trait fee against the licence agreement, mis-applies the treaty cap without a live Tax Residency Certificate check, and mis-computes the refund by drawing input services and capital goods into the Net ITC base.
- **Logic:** Ingest the Bt cotton trait-fee licence agreement as a structured contract object with the trait-fee-per-packet rate, the SKU coverage, the effective season, the beneficial-owner counterparty, and the associated-enterprise flag. Aggregate packet-level dispatch by state by season from the sales sub-ledger and multiply against the contractual trait-fee rate to derive the trait-fee accrual per state per season. Cross-key each state's dispatch to the state Cotton Seed Price Control Committee notified MRP for that season and expose the under-recovery where the notified MRP is below the contractual ex-factory recovery. Route the trait-fee payable to the foreign-remittance workflow with a Tax Residency Certificate and Form 10F validity check gated to the remittance instruction date, apply the India-US DTAA Article 12 treaty rate where the beneficial-ownership test is met, and generate the Form 15CA and Form 15CB filing package for the authorised-dealer bank. Ingest the grow-out plot buy-back invoice register keyed to grower Udyam Registration Number, apply a Section 43B(h) 45-day aging lens, and alert treasury at day 30 for the priority payment run. Split the input GST register at source into eligible input-goods ITC (packaging materials, lab-testing consumables, godown storage), input services ITC (freight, professional fees), and capital-goods ITC (seed-cleaning machinery, colour-sorter, packaging line) — feed only the eligible input-goods pool into the Rule 89(2) and (4) refund workbook, generate the GST RFD-01 filing under the exempt-supply refund category with the Statement-3/3A/5 workings, and reconcile the refund realisation into the electronic credit ledger. Maintain the Rule 10D transfer-pricing documentation stack where the licensor is an associated enterprise and generate the Form 3CEB draft for accountant certification.
- **Config:** Bt cotton trait-fee licence-agreement master with counterparty, beneficial owner, associated-enterprise flag, trait-fee-per-packet rate, SKU coverage, effective season, and licence-agreement version history; state MRP notification master keyed to state, notification date, effective season, packet SKU, notified price, and reconciled ex-factory recovery; foreign-remittance register with Tax Residency Certificate expiry, Form 10F expiry, applicable DTAA article, treaty rate, and Form 15CA-15CB linkage; Rule 10D transfer-pricing documentation stack with ownership chart, functional-and-risk analysis, comparability analysis, methodology selection, and economic analysis; grower master with grower name, Udyam Registration Number, MSME classification, agreed credit period, and buy-back contract; grower buy-back invoice register with invoice date, contract rate, packet quantity, and 43B(h) aging flag; input GST register split into eligible input-goods, ineligible input-services, and ineligible capital-goods buckets at source; Section 54(3) nil-rated refund workbook keyed to tax period with Statement-3/3A/5 workings; state-wise sales sub-ledger keyed to state, season, and packet SKU.
- **Output:** A month-end and season-end Bt cotton reconciliation pack: trait-fee accrual by state by season keyed to the licence agreement rate and packet dispatch; state-by-state MRP under-recovery register with the notification effective date and quantified variance against contractual ex-factory recovery; foreign-remittance file with TRC validity, Form 10F validity, DTAA Article 12 treaty rate applied, Section 195 withholding computed, and Form 15CA-15CB pair generated per remittance instruction; Rule 10D transfer-pricing documentation stack refreshed for the season with Form 3CEB draft ready for accountant certification; MSME grower-payment aging with 30-day priority-run alert and 43B(h) disallowance projection at year-end; Section 54(3) nil-rated refund draft under Rule 89(2) and (4) with input-services and capital-goods ITC segregated out of the Net ITC pool per Notification 14/2022 and the VKC Footsteps holding; season-end Board-pack summary of trait-fee under-recovery, MRP litigation status per state, and refund realisation position.

### Kohinoor Foods Basmati Export FX Realisation Reconciliation

Source: https://www.terra-insight.com/insights/kohinoor-foods-basmati-export-fx-realisation-reconciliation/

- **Problem:** A premium basmati export house shipping approximately 1.2 lakh MT per year across 40 percent UK, 30 percent Middle East, 20 percent US, and 10 percent other corridors — with an illustrative weighted average realisation of USD 1,380 per MT for Pusa Basmati 1121 — must reconcile every shipping bill against the commercial invoice, the bill of lading, the AD bank's e-BRC realisation, the RoDTEP e-scrip credit on the ICEGATE ledger, the APEDA cess payment and any offset, and the Ind AS 21 fx-variance GL entry generated by the 60 to 90 day USD receivable cycle. The DGFT MEP straddle from August 2023 (USD 1,200 per MT floor) through October 2023 (USD 950 per MT floor) through September 2024 (MEP withdrawal) creates three distinct pricing regimes within one financial year at the change-over point; shipping bills filed within each regime must be tagged to the applicable floor. Manual reconciliation across the seven touchpoints loses e-BRC-to-shipping-bill matches, mis-books the Ind AS 21 exchange-difference to the wrong period, mis-classifies the RoDTEP credit against the wrong shipping bill, and exposes the exporter to Section 43AA tax reconciliation mismatches at Form 3CD disclosure.
- **Logic:** Build a shipping-bill master keyed on ICEGATE shipping bill number, capturing FOB in USD, HSN 1006 30 20, RoDTEP or DBK election, bill of lading date, buyer master, corridor tag, and applicable MEP regime by shipping bill date. Extend the master with the commercial invoice reference, the Bill of Lading number, and the bill of lading date to establish the shipment closure event. Book the Ind AS 21 initial recognition at shipping-bill-date spot rate against the internal FX rate feed; carry the USD receivable and the INR carrying amount on the AR sub-ledger with the source spot rate stamped as an immutable attribute. Retranslate the outstanding USD receivable at each balance-sheet date to closing rate and post the exchange difference under paragraph 23(a) plus paragraph 28. Ingest the AD bank's e-BRC feed from the DGFT portal against the shipping bill number; the e-BRC realisation date, realisation-date spot rate, and realised INR are matched to the AR sub-ledger and the residual exchange difference is posted on settlement. Ingest the RoDTEP e-scrip credit feed from ICEGATE against the shipping bill number; reconcile the credited rate against the notified Appendix 4R rate on the FOB value. Ingest the APEDA scheme ledger and reconcile the export cess paid against the shipment and any scheme-administered offset. Generate the Form 3CD fx-variance reconciliation between Ind AS 21 accounting treatment and ICDS VI tax treatment at year-end.
- **Config:** Shipping bill master with SBN, SB date, HSN, FOB in USD, corridor, RoDTEP versus DBK election, MEP-regime tag (pre-MEP, USD 1,200 window, USD 950 window, post-withdrawal); buyer master keyed on buyer code, corridor, credit terms, base currency, RCMC coverage flag, EU Certificate of Authenticity requirement flag; commercial invoice master keyed on invoice number, shipping bill number, invoice date, USD value, INCOTERM, payment terms; internal FX rate feed with source (RBI reference rate or authorised dealer counter rate) and time stamp; AR sub-ledger keyed on invoice with USD receivable, INR carrying amount, spot rate stamp, next-retranslation date; balance-sheet-date closing-rate schedule for month-end, quarter-end, and year-end; e-BRC feed from the AD bank with shipping bill match key; RoDTEP e-scrip feed from ICEGATE with rate and value reconciled against Appendix 4R; APEDA scheme ledger with cess and any offset; ICDS VI cross-reconciliation workbook feeding Form 3CD.
- **Output:** A per-shipment lifecycle pack: shipping bill filed on ICEGATE with FOB and MEP-regime tag, commercial invoice raised, bill of lading closure, Ind AS 21 initial recognition entry at shipping-bill-date spot rate, balance-sheet-date retranslation entries with exchange-difference posting, e-BRC realisation match with realisation-date exchange-difference posting, RoDTEP e-scrip credit reconciliation, APEDA cess and offset reconciliation, closure of the FEMA outstanding-export register at the AD bank, and a year-end Form 3CD fx-variance reconciliation between Ind AS 21 accounting and ICDS VI tax treatment. Per-corridor realisation dashboard splits the weighted-average USD realisation across UK, Middle East, US, and other corridors and separates MEP-regime shipments from post-withdrawal market shipments. Portfolio-level fx-variance analytics show translation-date gain or loss, realisation-date gain or loss, and the residual receivable at each period-end.

### Kotak Mahindra Bank Corporate Statement Reconciliation

Source: https://www.terra-insight.com/insights/kotak-mahindra-bank-corporate-reconciliation-india/

- **Problem:** Kotak Mahindra exposes the same transactions across Kotak FYN CSV, MT940, and a separate collections report — with bank-specific narration prefixes ('/PRI/' in :86:) and Kotak-internal Batch Payment IDs ('KOTBP' references) that hide individual beneficiary credits behind consolidated debit lines. Without batch-ID joins to the FYN batch-status file, payroll and NACH collection lines remain unmatched and exception queues balloon.
- **Logic:** Channel-aware ingestion routes Kotak CSV, MT940, MT942, and the collections report to separate parser profiles. NEFT and RTGS narrations are tokenised on single-space delimiters with '/PRI/' prefix stripping in :86:. Batch Payment IDs of the form 'KOTBP[YY][NNNNNN]' on consolidated debit lines join to the Kotak FYN batch-status file to explode beneficiary-level detail. Service-charge debits route to the bank charges GL with the GST component split for input tax credit.
- **Config:** Kotak FYN '/PRI/' parser profile, MT940 end-of-day SFTP ingestion, MT942 intra-day visibility stream, Batch Payment ID join to FYN batch-status file, NACH collections report linkage, Section 194A TDS auto-recon for interest credits above ₹40,000.
- **Output:** Clean Kotak transaction ledger reconciled against MT940 :62F:, payroll and vendor payment batches exploded to beneficiary level via Batch Payment ID, NACH collections matched at mandate level, GST-eligible fee debits in the ITC register, and Section 194A TDS aligned with Form 26AS.

### KRBL India Gate Basmati Mandi Procurement Reconciliation

Source: https://www.terra-insight.com/insights/krbl-india-gate-basmati-mandi-procurement-reconciliation/

- **Problem:** A large listed basmati miller aggregating 40,000 to 55,000 metric tonnes of paddy per month during the October to December peak procurement window from a network of Punjab (Sangrur, Bathinda) and Haryana (Kaithal, Karnal) mandis must reconcile every mandi arhtia's gate-pass and weighbridge slip against each plant's procurement register, deduct Section 194Q code 1017/1031 TDS at 0.1 percent on aggregate purchase above Rs 50 lakh per arhtia PAN per financial year, deduct Section 194H code 1015 arhtia commission TDS at 5 percent on the commission line, and extend the reconciliation into inter-plant paddy and by-product transfer between milling units and the group's ethanol distillery arm at CGST Rule 28 open-market valuation. Manual reconciliation across four legs (mandi gate-pass, plant weighbridge, procurement register, and TDS challan) at peak season volume routinely over-deducts on composite value, misses the Rs 50 lakh per-PAN threshold cut-over, and inflates the ethanol OMC lifting register with two-day timestamp drift — exposing the miller to Section 201 short-deduction demand on 194Q reversals and to Section 74 GST demand on inter-unit transfer under-valuation.
- **Logic:** Ingest the mandi arhtia gate-pass at the point of paddy loading, key each slip to the arhtia licence number and PAN, and carry the auction sale value forward to the plant weighbridge slip on arrival. Match gate-pass quantity against weighbridge net weight within the tolerance band (typically 0.25 percent for basmati paddy) and surface variances beyond the band as exceptions on the procurement register close. Aggregate the arhtia PAN-level running total on the paddy price component alone (excluding mandi fee, rural development cess, and arhtia commission), and trigger Section 194Q TDS at 0.1 percent on the incremental value above the Rs 50 lakh threshold per arhtia PAN per financial year with the payment code 1017 or 1031 as per the chart-of-accounts classification. Deduct Section 194H TDS at 5 percent on the commission line under code 1015 on a separate accrual and remit both codes through the same Form 26Q filing. Feed inter-plant paddy and by-product transfers (broken rice, husk, bran to the distillery) into an inter-unit stock ledger with a Rule 28 valuation note (open market value or 110 percent of cost). Reconcile the distillery output register against the OMC lifting confirmation with a timestamp normalisation for the two-day OMC dispatch lag, and clear the inter-unit settlement to a zero balance every month-end.
- **Config:** Arhtia master with licence number, PAN, GSTIN (where registered above the aggregate turnover threshold), TDS payment codes 1017/1031 for 194Q and 1015 for 194H, and commission slab (typically 2.5 percent kachha arhtia rate for basmati); mandi master with APMC market code, weighbridge station code, mandi fee rate, and rural development cess rate; plant master with weighbridge station, procurement register schema, and Section 194Q per-PAN running-total table refreshed at every purchase entry; variety master with paddy variety code (1121, PB1509, Pusa) mapped to expected outturn ratio for milling yield reconciliation; inter-plant transfer master with source GSTIN, destination GSTIN, Rule 28 valuation method (open market or 110 percent of cost), and HSN mapping (1006 paddy, 1102 broken rice, 2302 bran, 2303 husk); ethanol distillery master with OMC-registered capacity, weekly output tally against alcohol strength, and OMC dispatch schedule feed for lifting reconciliation; e-BRC feed from the DGFT portal for the basmati export leg where the group also runs the branded export business.
- **Output:** A month-end multi-leg mandi procurement reconciliation pack: opening arhtia PAN-level running total, per-mandi per-day gate-pass and weighbridge tally with variance flagged beyond tolerance, plant procurement register close by variety (1121, PB1509, Pusa) and by grade, Section 194Q code 1017/1031 TDS accrual keyed to each arhtia PAN with the Rs 50 lakh threshold cut-over date stamped, Section 194H code 1015 commission TDS accrual on the arhtia commission line, Form 26Q filing base with both codes reconciled to the TDS remittance schedule, inter-plant paddy and by-product transfer register with CGST Rule 28 valuation note, distillery output tally reconciled against the OMC lifting confirmation with two-day timestamp normalisation, and — where the group runs a branded basmati export business — an e-BRC to shipping bill reconciliation base for the RoDTEP scrip claim under HSN 1006 30 20 and 1006 30 90.

### Lawful Interception and Government Billing Reconciliation for Indian Telecom Operators

Source: https://www.terra-insight.com/insights/lawful-interception-billing-reconciliation-india/

- **Problem:** Indian telecom operators carry two regulator-and-government-touched reconciliation streams: lawful interception compliance under the DoT unified licence (LEA access provisioning, retention, LEI infrastructure, limited cost recovery) and government customer billing (defence, railways, central and state PSUs and departments) where Section 393(1) Sl. 6(i) contractor code 1024 (2% government deductor) TDS is withheld by the government deductor. Reconciliation must tie licence-compliance capex amortisation and opex, recoverable provisioning charges where permitted, government bill-to-receipt with 26AS credit by deductor TAN under Section 393(1) Sl. 6(i), and 18 percent GST output on government supplies.
- **Logic:** For lawful interception: capitalise LEA access and LEI infrastructure under Ind AS 16; amortise per useful life; opex the retention storage and compliance staffing; raise recoverable provisioning charges on the requisitioning authority where permitted by the licence framework. For government billing: tie bill to government work order; track receipt against bill with T+90 to T+180 ageing; reconcile Section 393(1) Sl. 6(i).D(b) code 1024 TDS at 2 percent on net of GST against Form 26AS by deductor TAN; raise GSTR-1 outward at 18 percent and reconcile to GSTR-3B 3.1(a); manage the long-cycle receivable working-capital position.
- **Config:** Lawful interception capex register with Ind AS 16 useful life; LEA access provisioning charge schedule; government customer master with deductor TAN and work order reference; bill-to-receipt ledger with ageing; Section 393(1) Sl. 6(i).D(b) code 1024 TDS rule for government deductors with 26AS reconciliation by TAN; GST 18 percent telecom-service classification for GSTR-1 outward.
- **Output:** A reconciled licence-compliance and government-billing position showing lawful-interception capex amortisation and opex, recoverable provisioning charges raised, government bill cycle with T+90/T+180 ageing, Section 393(1) Sl. 6(i).D(b) code 1024 TDS receivable per deductor TAN reconciled to Form 26AS, and 18 percent GST output liability tied through GSTR-1 to GSTR-3B.

### Nil-Rated Life-Saving Drugs: Cancer, HIV, TB, Rare Disease Schedule

Source: https://www.terra-insight.com/insights/life-saving-drugs-nil-rate-gst-cancer-hiv-tb-rare-disease/

- **Problem:** A biosimilar oncology manufacturer with a Rs 1,100 crore annual portfolio spanning trastuzumab and rituximab biosimilars plus a supporting basket of oncology formulations moves the specified life-saving drugs to a nil GST output rate effective 22 September 2025. Input GST paid on API under HSN Chapter 29 at 5 percent, on aseptic packaging under HSN 3923 or 4819 at 18 percent, on sterile fill-finish services at 18 percent, on cold-chain logistics at 18 percent, and on labelling at 12 or 18 percent, remains payable at the same rates. Section 17(2) CGST restricts ITC to the taxable-supply share, and Rule 42 (inputs and input services) plus Rule 43 (capital goods amortised over 60 months) compute the exempt-attributable reversal each period. Manual reconciliation across product lines, common-credit registers, input-specific registers, capital-goods amortisation schedules, and monthly versus annual reconciliation cycles routinely under-reverses at interim months and either over-corrects or under-corrects at the annual Rule 42(2) true-up — exposing the manufacturer to Section 73 or Section 74 GST demand notices and to interest under Section 50.
- **Logic:** Split the outward supply register by HSN and by rate into four buckets: nil-rated life-saving formulations, 5-percent regular formulations and other drugs, 5-percent medical devices under HSN 9018 to 9022, and residual 12 or 18 percent lines. Compute E as aggregate exempt supplies (nil-rated portion plus any pure exempt lines) and F as total turnover in the State each period. Segregate the input tax credit for the period into T1 (non-business), T2 (exclusive to exempt — dedicated API lots and dedicated oncology-only packaging), T3 (blocked), T4 (exclusive to taxable including zero-rated exports), and residual C2 (the common pool that flows into both taxable and exempt output). Compute D1 = (E / F) x C2 as the exempt-attributable reversal and D2 = 0.05 x C2 as the notional non-business reversal. Post D1 plus D2 to GSTR-3B Table 4B(1) for the period. For capital goods, maintain a Rule 43 amortisation schedule per asset code: Tc from the GST paid at purchase, Tm = Tc / 60, Te = (E / F) x Tm added to the same GSTR-3B Table 4B(1) line. Track the annual Rule 42(2) reconciliation for each financial year before the September following the year end, redo the ratio on year-end aggregates, and adjust the interim monthly reversals up or down against the annual figure.
- **Config:** Product master with SKU code, HSN code, output GST rate (0 nil / 5 / 12 / 18), 22 September 2025 rate change flag, and life-saving-drug schedule flag; input master with input code, HSN code, input GST rate, exclusive-use flag (taxable-only, exempt-only, common), and per-batch consumption link to the manufacturing execution system; capital-goods master with asset code, capitalisation date, ITC amount at purchase (Tc), useful-life months (60 default), exclusive-use flag or common flag, and change-of-use log; monthly Rule 42 workbook that recomputes E, F, C2, D1, and D2 from the GSTR-1 and GSTR-2B feed; monthly Rule 43 workbook that carries the Tm amortisation forward for each common-use asset and computes Te; annual Rule 42(2) true-up workbook that redoes the ratio on year-end aggregates; GSTR-3B Table 4B(1) reconciliation from the D1+D2+Te aggregate; product-level P&L view that surfaces the reversal cost per SKU.
- **Output:** A period-close pharma common-credit reversal pack: outward supply split by HSN and rate with the nil-rated life-saving portion isolated, T1 through T4 and C2 segregation of period ITC with the common pool sized, Rule 42 D1 and D2 for the month with the E/F ratio audit trail, Rule 43 Te per asset code with the Tm amortisation schedule visible, GSTR-3B Table 4B(1) posting reconciled against the D1+D2+Te aggregate, and — at year-end — the Rule 42(2) annual reconciliation with an interim-to-annual variance line. Product-level view attributes the reversal cost to the nil-rated life-saving SKUs so the finance team can model the net-of-reversal margin on the oncology portfolio and set the correct DPCO ceiling-price submission to the National Pharmaceutical Pricing Authority for the affected NLEM-scheduled formulations.

### Line-Stop Charges and Liquidated Damages in Indian Auto Supply: Accounting Treatment

Source: https://www.terra-insight.com/insights/line-stop-charge-liquidated-damages-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers face OEM line-stop charges at ₹50,000 to ₹50 lakh per incident, billed at contractual per-minute or per-hour rates encoded in the master supply agreement's liquidated damages clause. Ind AS 37 provisioning applies when the line-stop event occurs, force-majeure carve-outs require written notice within 7-14 days, aggregate liability is capped at 5-10% of annual contract value, and the post-CBIC Circular 178/10/2022 position is that LDs are not a taxable supply and therefore outside GST.
- **Logic:** On each line-stop event communication, capture the OEM line log (date, duration, attributed cause), check against the MSA force-majeure carve-out and the aggregate cap status, raise Ind AS 37 provision at the supplier's best estimate of probable settlement, route to accept-or-contest based on attribution evidence, recognise no GST on the LD charge (per CBIC Circular 178/10/2022), and track the aggregate-liability cap consumption against annual contract value.
- **Config:** MSA line-stop rate matrix by OEM and vehicle programme, force-majeure event register with written-notice timer (7/10/14 days), aggregate-liability cap counter per OEM contract per FY, line-stop event log with attribution evidence (line log, supplier shortage record, GRN, monsoon/strike declarations), Ind AS 37 provision workflow keyed to line-stop event, contest queue with force-majeure and attribution sub-tracks.
- **Output:** A line-stop event register per OEM with attributed-cause classification and contest status, aggregate-liability cap consumption dashboard per OEM per FY with remaining headroom, Ind AS 37 provision roll-forward by quarter, force-majeure notice tracker with notice-window timers, and a monthly line-stop trend by vehicle programme for the provision refresh.

### LME Aluminium and Copper Pricing for Indian Auto-Component RMPV Claims

Source: https://www.terra-insight.com/insights/lme-aluminium-copper-pricing-rmpv-auto-india/

- **Problem:** Indian auto-component suppliers running non-ferrous RMPV claims against OEM contracts that name LME as the reference must convert USD-per-MT settlement prices to delivered INR-per-kg through four layers (LME settlement + LBMA FX + Mumbai aluminium premium + GST at consumption), reconcile cash-vs-3-month ambiguity, hold the alloy premium and the landed premium fixed, and time the Ind AS 37 provision against LME's first-business-day-of-following-month finalisation.
- **Logic:** Anchor on the LME cash settlement (or 3-month forward, contract-specified) for the revision period at the contractual averaging method. Convert through LBMA-published or contract-specified INR FX. Apply the fixed-at-award Mumbai aluminium premium for delivered-base. Apply the fixed-at-award alloy premium (A356 over LME-primary, OFE copper over LME copper). Compute: Claim = (LME_INR_per_kg_Current − LME_INR_per_kg_Base) × Material_Weight × Quantity. Book Ind AS 37 provision at quarter-end; true up on LME finalisation. Route upward to supplementary invoice, downward to Section 34 credit note within cutoff.
- **Config:** Part master row per non-ferrous-content part carrying LME metal (aluminium / copper / nickel / lead / zinc), reference type (cash / 3-month forward), averaging method, FX rule, landed premium fixed at award, alloy premium fixed at award, base LME-INR-per-kg level. LME feed by daily settlement. LBMA FX feed. Quantity-supplied feed by revision period per OEM. Quarter-end provision ledger. GST routing splitting upward vs downward with Section 34 cutoff watch.
- **Output:** Per-claim worksheet showing LME reference type and metal, base and current LME-USD-per-MT values, FX applied, landed premium fixed, alloy premium fixed, derived LME-INR-per-kg differential, rupee claim, GST routing (supplementary invoice or Section 34 credit note), Ind AS 37 provision-vs-actual true-up, Section 34 cutoff watch flag, and recorded FX/premium fixings for audit defence.

### Loan-Licensing and Third-Party Manufacturing: The Pharma Reconciliation Guide

Source: https://www.terra-insight.com/insights/loan-licensing-manufacturing-pharma-cdmo-reconciliation-guide/

- **Problem:** A Tier-1 Indian pharma brand-owner and market-authorisation holder running its Sikkim manufacturing unit for active pharmaceutical ingredient and intermediate production under the Section 80-IE 100 percent profit deduction, dispatching the active pharmaceutical ingredient to a Baddi loan-licensee for finished dosage form manufacture, must reconcile Section 143 CGST job-work dispatch challans against physical return of finished goods within the 1-year window for inputs and 3-year window for capital goods; the third-party's HSN 9988 job-work invoice at 12 percent IGST (Sikkim-to-Baddi being inter-state) against the specific dispatch batch and challan; the ITC-04 quarterly filing against the challan-level dispatch and return register; the electronic credit ledger utilisation of the IGST job-work invoice ITC against the brand-owner's own finished-product output tax; and the Section 43B(h) 45-day MSME payment aging for the third-party's job-work invoice where the loan-licensee is registered as a Micro or Small enterprise. Manual reconciliation across four cascading surfaces — dispatch challan, return challan, ITC-04, job-work invoice — misses the 1-year window on individual batches, over-states the electronic credit ledger IGST balance, and exposes the brand-owner to a Section 143 deemed-supply demand with interest from the dispatch date at year-end audit.
- **Logic:** Build a challan-level dispatch register at the brand-owner's Sikkim plant capturing every active pharmaceutical ingredient and intermediate movement to the Baddi loan-licensee, keyed by challan number, batch number, dispatch date, HSN classification (Chapter 29 or 30), quantity, and taxable value under Rule 45. Track the return of finished dosage form against the original challan through the loan-licensee's return challan with the master batch record reference. Age every open dispatch against the 1-year Section 143 input window and the 3-year capital-goods window with a mid-window alert at 10 months. Ingest the third-party's HSN 9988 job-work invoice, match each invoice line to the specific dispatch batch through the batch number and the tariff schedule, and reconcile the IGST at 12 percent (inter-state) against the brand-owner's GSTR-2B receipt. Aggregate the challan-level dispatch and return movements into the ITC-04 filing base under the four ITC-04 categories. Flag every loan-licensee that is Udyam-registered as Micro or Small under the MSMED Act, apply the Section 15 payment window (45 days if written agreement, 15 days otherwise), and age every unpaid job-work invoice against that window for the Section 43B(h) tax-provisioning workbook.
- **Config:** Loan-licensee master with vendor code, GSTIN (with state-code parsing for inter-state versus intra-state classification), PAN, Udyam Registration Number and MSMED classification (Micro / Small / Medium), written agreement flag (drives the 45-day versus 15-day window under Section 15 MSMED), tariff schedule per finished dosage form batch, and drug-licence linkage to the brand-owner's market authorisation; dispatch challan register with challan number, batch number, HSN (Chapter 29 or 30), quantity, taxable value at dispatch, dispatch date, and Section 143 input-vs-capital-goods flag; return register keying the return challan to the original dispatch challan through the batch number; job-work invoice register with invoice number, invoice date, batch reference, HSN 9988 line item, and the IGST-versus-CGST-plus-SGST split based on state combination; ITC-04 filing schedule per current CBIC-notified periodicity (half-yearly up to Rs 5 crore turnover, annual above); Section 43B(h) MSME payment aging tracker with 15-day / 45-day window flag and mid-window alert; the brand-owner's electronic credit ledger IGST balance and utilisation ordering under Section 49(5) for cross-reference against the job-work invoice ITC pool.
- **Output:** A month-end and quarter-end loan-licensee reconciliation pack: open dispatch challan aging by loan-licensee against the Section 143 1-year (input) and 3-year (capital-goods) window with a hard-stop flag at 11 months; batch-level match between dispatch challan, return challan, and third-party job-work invoice with aggregate margin and per-batch tariff verified against the loan-licensing agreement; ITC-04 periodic draft with dispatch and return counts, taxable-value totals, and a variance explanation for challans still open at the reporting date; electronic credit ledger IGST reconciliation showing the loan-licensee job-work ITC pool matched against GSTR-2B and utilised against the brand-owner's own finished-product output tax; Section 43B(h) aging tracker categorising every unpaid job-work invoice at the balance-sheet date into 'within window' (deductible in current year) and 'beyond window' (disallowed and deductible only when paid), with the tax provisioning workbook fed for current-tax and deferred-tax computation; and — for the Sikkim Section 80-IE brand-owner — the deduction-eligible profit worked out on the brand-owner's own manufacture of active pharmaceutical ingredient and intermediates, cleanly segregated from the third-party's finished-dosage-form conversion margin (which is not an 80-IE deduction line for the brand-owner).

### LT Foods Daawat Basmati Export Reconciliation — Royal + Devaaya

Source: https://www.terra-insight.com/insights/lt-foods-daawat-basmati-export-recon-royal-devaaya/

- **Problem:** A large branded basmati exporter operating three brand portfolios — Royal in the US-Canada market, Daawat across UK, EU, and Middle East, and Devaaya as a premium Middle East offering — at an illustrative 2.85 lakh MT of annual export shipped from Kandla, Mundra, Nhava Sheva, Kolkata, and Vizag ports at a weighted average realisation of USD 1,450 per MT must reconcile brand-wise shipment logs against per-contract price, FOB invoice, shipping bill assessed value, e-BRC realisation from the AD Category-I bank, RoDTEP scrip issuance at ICEGATE under Appendix 4R for HSN 1006 30 20 and 1006 30 90, and APEDA RCMC-based export scheme reimbursement. Overlaid on the base reconciliation are the shipment-date Minimum Export Price (MEP) flag (USD 1,200 per MT window August-October 2023, USD 950 per MT window October 2023 through September 2024, no-MEP window from 13 September 2024 onwards), the FEMA nine-month realisation clock from shipping bill let-export order date, and — for the domestic-branded operation running alongside — a Section 54(3) CGST refund cycle on LUT-based export supplies and a smaller inverted-duty position on packaging inputs at 18 percent against domestic branded rice output at 5 percent. Manual reconciliation across brand, port, AD bank, and scheme leaks per-shipping-bill RoDTEP scrip closure, mis-ages the FEMA realisation bucket, and loses APEDA scheme reimbursements at the claim-window boundary.
- **Logic:** Ingest the brand-wise shipment log at contract, invoice, and shipping bill stages, keying every shipment to (a) brand (Royal / Daawat / Devaaya), (b) destination country and buyer entity, (c) port of export, (d) delivery quantity and per-MT FOB, (e) shipment date, and (f) the applicable MEP window at shipment date. Match the shipping bill assessed value against the FOB invoice per MT and expose any MEP-window violation (FOB below the notified floor during the MEP period) as a customs exception. Ingest the AD bank's e-BRC feed via the DGFT portal or direct AD bank statement, match e-BRC to shipping bill by SB number, and maintain a shipping-bill-to-realisation ageing bucket bucketed at 3, 6, and 8 months from let-export order date. Feed the RoDTEP scrip credit stream from ICEGATE and reconcile scrip receivable per shipping bill against the Appendix 4R notified rate on the HSN-and-quantity basis. Feed the APEDA cess line from every shipping bill and reconcile against APEDA scheme reimbursement claims by claim window. Run two parallel Section 54(3) refund workbooks per period — Rule 89(4) LUT refund on zero-rated export supplies with Net ITC drawn from inputs and input services on the export leg, and Rule 89(5) inverted-duty refund on the domestic branded rice operation where 5 percent output sits against 18 percent packaging input, with Net ITC excluding input services and capital goods per Notification 14/2022 — and generate the two GST RFD-01 drafts monthly.
- **Config:** Brand master with brand code (Royal / Daawat / Devaaya), primary destination markets, and per-brand distributor register; buyer master with foreign buyer entity, address, country, AD bank of remittance, and Bill of Lading consignee; port master with Kandla / Mundra / Nhava Sheva / Kolkata / Vizag identifiers and per-port CHA (Customs House Agent) mapping; MEP schedule master with the four MEP windows (pre-August 2023 no-MEP; USD 1,200 25 August to 24 October 2023; USD 950 25 October 2023 to 12 September 2024; no-MEP from 13 September 2024) and per-shipment shipment-date lookup; RoDTEP Appendix 4R rate schedule keyed to HSN 1006 30 20 and 1006 30 90 with effective-date versioning; APEDA RCMC master with certificate number, validity, and scheduled-product coverage; AD Category-I bank master with e-BRC feed source, bank code, and EDPMS reconciliation identifier; foreign agent register with Section 195 TDS position (no-TDS with Form 15CA/15CB, or TDS deducted at applicable rate); Section 54(3) LUT refund workbook feed from GSTR-1 zero-rated supply and packaging input register.
- **Output:** A monthly and quarterly brand-wise basmati export reconciliation pack: brand-and-destination shipment log with contract-versus-invoice-versus-shipping-bill variance, MEP-window violation exceptions (during MEP windows), shipping-bill-to-e-BRC ageing bucket per AD bank, outstanding-realisation ageing at 3 / 6 / 8 / 9 months with early-warning trigger at 6 months, RoDTEP scrip receivable ledger closed per shipping bill against the ICEGATE credit, APEDA cess ledger reconciled against APEDA scheme reimbursement claims by claim window, foreign agent commission ledger with Section 195 TDS disposition and Form 15CA/15CB attachment, Section 54(3) LUT refund draft under Rule 89(4) for zero-rated export supplies, and a separate Section 54(3) inverted-duty refund draft under Rule 89(5) as amended by Notification 14/2022 for the domestic branded rice leg. Per-brand margin dashboard supports the exporter's brand-wise pricing review and the CFO's board reporting on export incentive receivable recovery cycle.

### Ludhiana Hosiery and Woollen Cluster Reconciliation

Source: https://www.terra-insight.com/insights/ludhiana-hosiery-woollen-cluster-reconciliation/

- **Problem:** A Ludhiana hosiery and woollen manufacturer running mid-tier winter production (illustratively ₹28 crore pre-winter yarn buy August–October, ₹42 crore dispatch peak October–January) must reconcile a bunched pre-winter yarn procurement window against MSME Section 43B(h) 45-day payment discipline at supplier level, a dyeing and finishing job-work leg under Section 143 CGST and TDS payment code 1023, a monthly stock-and-debtors statement to the working-capital banker for drawing-power computation, and a year-end inventory ageing test for unsold winter stock under Ind AS 2. Manual reconciliation typically fails on three vectors: MSME payment ageing not tracked by Udyam-flagged supplier; drawing-power submission not reconciled to the perpetual inventory cost basis; and closing-stock net realisable value test not run by season-tag and style code.
- **Logic:** Build a seasonal-cycle-aware reconciliation. Buy-side ledger flags every supplier as MSME (Udyam number on file) or non-MSME, and runs a Section 43B(h) ageing report daily during the September–October and December–January peak-payment windows. Job-work register keyed by Rule 55 challan captures worsted or carded yarn dispatched to the dyer, dye chemicals as free-issue, and returns as finished fabric, with Section 143 clock and TDS code 1023 attached at the challan level. Working-capital reconciliation ingests the perpetual inventory ledger at moving weighted average cost, applies the banker-agreed margin percentages by category (raw material 25 percent, stock in process 25–30 percent, finished goods 25–30 percent, debtors 30–40 percent), and produces the drawing-power statement matched to the sanctioned cash-credit or overdraft limit. Inventory ageing tracks every SKU by season-tag (evergreen, season-tied, fashion), style code, and dispatch-date lineage, and runs a rolling three-month NRV test on ageing stock.
- **Config:** Supplier master with MSME flag, Udyam Registration Number, valid-from and valid-to dates on the registration, payment cycle days agreed under written contract (default 45 days if written; 15 days if not), and MSME classification (micro or small — Section 43B(h) applies only to micro and small, not medium). Job-worker master with Section 8 Sl. 4 code 1023 configuration, TDS rate slab (1 percent Ind/HUF; 2 percent other resident), and job-work challan pair reference. Bank facility master with sanctioned CC/OD limit, margin percentages by inventory category, debtors ageing eligibility rule (typically 0–90 days eligible; 91+ excluded), and multiple-banking share split. Inventory master with season-tag (evergreen, season-tied, fashion), style code, cost basis (moving weighted average or FIFO per accounting policy), dispatch-date lineage, and NRV test threshold (typically write-down triggered if last three-month net dispatch price is below cost less margin).
- **Output:** A month-end Ludhiana hosiery reconciliation pack: MSME Section 43B(h) ageing report by supplier (invoice date, Udyam status, days-to-45-day-deadline, payment status, projected FY-of-deduction); stock-and-debtors statement to the banker with drawing power computed and reconciled to the physical stock take at every hop and to the debtors ageing report from the AR ledger; Section 143 job-work register showing worsted-yarn and dye-chemical dispatches, days-elapsed against the 1-year clock, and TDS code 1023 tally at deductee-job-worker PAN level ready for Form 26AS cross-check; and — at year-end — an inventory ageing and NRV test report by season-tag and style code with the recommended write-down amount for the audit committee.

### Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams

Source: https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements/

- **Problem:** High luxury spending relative to declared income in a bank statement indicates a lifestyle-income gap — the applicant's spending pattern is inconsistent with their stated financial profile. This inconsistency may indicate undisclosed income, informal borrowing, or savings drawdown that affects repayment capacity.
- **Logic:** Match transaction descriptions against 45+ luxury brand names spanning fashion, jewellery, hospitality, premium electronics, and beauty. Record transaction count, total debit, total credit, and top five matched terms. Compute luxury debits as a share of average monthly income to measure the lifestyle-income gap.
- **Config:** Enable for NBFC, HFC, and digital lending underwriting. Include Indian luxury brands (Tanishq, Taj, ITC Hotels) alongside international brands with Indian retail presence. Calibrate income-share threshold based on lender policy and loan product tier.
- **Output:** Luxury overspending risk section in the credit report with transaction count, total debit, top five matched brand names, and lifestyle-income gap assessment for credit officer review.

### Machine-Readable Evidence Trail: Reconciliation Audit Defensibility in India

Source: https://www.terra-insight.com/insights/machine-readable-evidence-trail-reconciliation-audit-defensibility/

- **Problem:** In most Indian finance operations, an auditor requesting evidence for a single reconciliation variance triggers a scavenger hunt that consumes 30 to 60 minutes per variance — searching for the bank statement in the shared drive, opening the ledger to find the reconciled entry, digging through email to identify who approved the classification, and reconstructing the reason code from an analyst's memory. Across a statutory audit sample of 40 tested variances, this is 20 to 40 audit hours of pure evidence hunting, which the audit firm bills back to the company. Worse, when the reconciliation cannot be defended with contemporaneous machine-readable evidence, the statutory auditor either accepts a narrative reconstruction (against SA 500 sufficient-appropriate-evidence discipline) or forces a top-side adjustment. Companies Act 2013 Rule 3(1) proviso, effective 1 April 2023, and the CARO 2020 audit-trail clause raised the compliance bar without giving finance teams a natural machine-readable place to store the reconciliation-side evidence.
- **Logic:** Every variance published in a TransactIG reconciliation run is a structured object carrying four evidence fields, not a narrative row on a spreadsheet. The source-file field references the raw feed the transaction was drawn from and is anchored by a cryptographic fingerprint of the file, computed at ingestion, so the same physical bytes are re-identifiable across the audit chain. The ledger-entry field references the exact voucher or invoice line the variance was measured against, drawn from the ERP feed. The classification-rule field references the specific rule that produced the reason code — partial payment under Section 15 valuation, timing difference across cut-off, credit-note netting under Section 34, TDS deducted at source under Section 393 of the Income Tax Act 2025 (the successor framework to the Chapter XVII-B sections in the 1961 Act), mismatched narration, and so on — with the rule reference embedded on the variance itself. The decision field is the ISO-8601 timestamp of classification, plus the reviewer identity and approval timestamp if a human took an action on the variance. The Recon Output Envelope binds all four fields together in a versioned, machine-readable output that can be re-generated deterministically.
- **Config:** Source-system feed configuration (bank statement parser per bank format, payment gateway settlement CSV parser, GSTR-2B/26AS extractor, ERP journal export); ingestion-time file fingerprinting; ledger reference resolution against the ERP voucher master; classification-rule library keyed by variance category (each rule carries a stable rule ID that gets stamped onto every variance it fires on); reviewer identity capture from the authenticated session at the moment of approval or override; envelope versioning aligned to industry preset versions and rule library versions; retention policy aligned to Section 128(5) of Companies Act 2013 (eight years) and CARO 2020 audit-trail preservation.
- **Output:** For every statutory audit cycle: an audit-ready envelope containing the fingerprinted source-file manifest, per-variance evidence rows with source file / ledger entry / classification rule / timestamped decision, a provenance walk from input file through classification to publication, and pre-computed CARO 2020 Clause 3(xi)(b) audit-trail compliance metadata for the reconciliation-derived population. The auditor's evidence request on any specific variance is already answered by the envelope. Re-running the same reconciliation later produces a byte-identical envelope if the inputs and rules have not changed, so audit evidence is stable across quarters.

### Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores

Source: https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india/

- **Problem:** Magento 2 and Adobe Commerce multi-vendor stores running Mirasvit or Webkul extensions with Razorpay Route or PayU SplitPay face a three-entity reconciliation chain — customer order, Magento sub-orders per vendor, and split payouts — and the gateway settlement report often loses the sub-order ID, forcing reconciliation to the parent order ID with per-vendor commission derived downstream.
- **Logic:** Match gateway payout to Magento order via invoice entity, then unpack to sub-orders in multi-vendor setups via the parent order ID. Derive commission per vendor per contract tier (typically 8–20%), deduct MDR (1.75–2.5% cards, 0–0.4% UPI) and GST on MDR, apply TDS Section 194O at 1% on gross sale value where the store is an e-commerce operator, and reverse refunds against the original sale period.
- **Config:** Magento connector with invoice and sub-order extraction, vendor commission tiers, Razorpay Route or PayU SplitPay linked account mapping, TDS 194O rule per vendor annual threshold (₹5 lakh), GST TCS Section 52 where applicable, and refund reversal logic tied to credit memo entity.
- **Output:** A per-order, per-vendor reconciled settlement with MDR, commission, TDS 194O, and GST TCS all attributed correctly, GSTR-1 filing aligned to marketplace vs single-seller posture, and a vendor payable ledger that clears against each vendor's linked-account payout.

### Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS

Source: https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation/

- **Problem:** Secondary aggregators like Magicpin and Dunzo run voucher and hyperlocal-delivery models with their own settlement formats, promo accounting, and platform-fee structures — and restaurants accepting them alongside Zomato and Swiggy must reconcile multiple aggregator types to a single revenue book without missing voucher fraud, cashback misallocation, or TCS credit.
- **Logic:** Match each aggregator order or voucher redemption to the outlet POS bill via the platform-issued reference ID. For Magicpin, key on voucher code redeemed in the POS tender table. For Dunzo and similar delivery platforms, key on order ID. Derive platform fee, GST on platform fee, and TCS at 0.5% from the settlement file. Book gross revenue with output GST, platform fee with ITC, TCS as a tax credit in GSTR-3B, and reconcile net to the bank credit batch.
- **Config:** Magicpin connector reading voucher redemption settlement file; Dunzo or equivalent hyperlocal connector reading order-level settlement; POS tender-type mapping per platform; TCS-aware GST ledger that posts the 0.5% credit by GSTIN and period; multi-platform consolidated reconciliation.
- **Output:** Per-platform reconciled revenue, voucher-fraud exception list, platform fee with ITC, TCS credits applied to GSTR-3B, and a unified aggregator ledger that ties Zomato, Swiggy, Magicpin, Dunzo, and any regional platform to a single chain-level revenue figure.

### Mahindra & Mahindra Supplier Payment and Debit-Note Handling for Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/mahindra-supplier-payment-debit-note-handling/

- **Problem:** Tier-1 suppliers to Mahindra & Mahindra operate inside a two-business commercial regime — Automotive Sector (SUVs at Chakan / Nashik / Haridwar) and Farm Equipment Sector (tractors at Nagpur / Rudrapur / Zaheerabad) — each with its own plant codes, FOMP running accounts, debit-note reason taxonomy and SUV-nameplate or tractor-platform commercial structure. A ₹180 crore annual M&M book across two plants demands business-keyed and programme-keyed settlement decomposition, Form 168 TDS reconciliation under Section 393(1) Sl. 6(i).D(b) code 1024, GST Section 34 credit-note timing per accepted debit, and Rule 37 ITC ageing on the contested book.
- **Logic:** Decompose each M&M settlement at the business level (Automotive Sector / Farm Equipment Sector) and plant-code level (Chakan / Nashik / Igatpuri / Haridwar / Nagpur / Rudrapur / Zaheerabad), tie each invoice and debit memo to the source SUV programme (XUV 3XO / XUV700 / XUV 9e / Scorpio Classic / Scorpio-N / Thar / Bolero / BE 6) or tractor platform (Arjun / Jivo / Yuvo / OJA / NOVO), classify debit reasons against the Mahindra-specific taxonomy with explicit line-stop coding, age each FOMP claim against the per-programme running account, calendar Section 34 GST credit notes per accepted debit, and reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i).D(b) code 1024 against the supplier's books.
- **Config:** Mahindra customer master with sub-records per business (Automotive Sector / Farm Equipment Sector) and per plant code, M&M Supplier Portal export mapping for daily call-off / ASN / GRN / settlement-statement / debit-memo parsing per business, debit-note reason taxonomy aligned to Mahindra Supplier Quality Manual codes with explicit line-stop reason, FOMP running account per SUV programme and per tractor platform, tooling cap and recovery rate per programme, Form 168 TDS register with Section 393(1) Sl. 6(i).D(b) code 1024 reconciliation, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-business, per-plant, per-programme M&M settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker per SUV nameplate or tractor platform with FOMP / tooling / quality penalty attribution, M&M Supplier Portal-sourced delivery-schedule reconciliation, Form 168 TDS register reconciled to books under Section 393(1) Sl. 6(i).D(b) code 1024, and Section 34 GST credit-note action queue keyed to approaching cutoff.

### Interest-Free Maintenance Deposit: Neither Revenue Nor Escrow

Source: https://www.terra-insight.com/insights/maintenance-deposit-real-estate-non-revenue-non-escrow-india/

- **Problem:** An Indian real estate developer collecting interest-free maintenance deposits (IFMD) at the point of possession — typically ₹50 per sq ft as a 24-month advance for maintenance — must correctly classify the receipt as a financial liability under Ind AS 32 rather than as revenue under Ind AS 115, distinguish it from the RERA Section 4(2)(l)(D) 70% escrow pool (which does not cover post-CC receipts), invoke the Companies (Acceptance of Deposits) Rules 2014 Rule 2(1)(c)(xii)(a)(ii) exemption to keep it outside the deposit-taking framework, book zero GST at collection but 18% on maintenance service as consumed under Notification 12/2017-CTR SL 77, and reconcile the possession-date IFMD receipt ledger against the GL liability and the monthly draw-down against actual maintenance expenditure — all in a way that produces a per-flat closing balance ready for handover to the resident welfare association.
- **Logic:** Tag every IFMD collection at possession per flat, per project, per date and per amount; classify the aggregate as Other Financial Liabilities on the balance sheet under Ind AS 32; keep the funds in a segregated bank account (voluntary governance, not a RERA escrow) tied to the project; book zero GST at receipt; run monthly maintenance service accounting with 18% GST on the applicable charge; draw down the IFMD liability against the maintenance expense as the service is rendered; reconcile the possession-date IFMD ledger to the bank deposit, to the GL liability, and to the cumulative draw-down; produce a per-flat closing balance signed off by the developer's CA at RWA handover.
- **Config:** Project master with total saleable area, possession dates per phase, IFMD rate per sq ft; flat master with buyer identifier, saleable area, possession date, IFMD receipt amount, receipt bank reference; segregated bank account per project for IFMD ring-fencing; maintenance expenditure ledger with per-month per-project actual cost; RWA handover master with target handover date and cumulative draw-down cap; reconciliation feeds — possession-date receipt ledger, bank statement, GL liability account, monthly maintenance revenue, RWA transfer confirmation.
- **Output:** A daily per-project IFMD position showing opening liability, receipts, monthly draw-down against maintenance expense, closing liability and forecast at RWA handover date; a per-flat IFMD balance ready for handover with cumulative maintenance draw-down and closing balance; a reconciliation exception report where IFMD receipts in the ledger do not tie to bank deposits, where draw-downs exceed maintenance expenditure booked, or where the per-flat sum does not tie to the GL aggregate; a handover-ready evidence pack per project containing per-flat opening receipts, monthly draw-down statements, actual maintenance expenditure with vendor invoices, CA-certified closing balance and the transfer confirmation from the RWA.

### MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment

Source: https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation/

- **Problem:** MakeMyTrip hotel settlements arrive net of commission, 18% GST on commission, and either 194-O TDS (e-commerce operator) or 194H TDS (commission agent) depending on booking type — while the hotel must recognise gross room revenue at the correct 12% or 18% GST slab and match each booking back to a PMS folio with cancellation, no-show, and MyBiz corporate variations all treated differently.
- **Logic:** Match MMT settlement file booking-by-booking to PMS folio: gross room rate, commission deducted, GST on commission, TDS section applied (194-O or 194H), and net payout. Gross up the net to true room revenue at the correct slab, claim 18% ITC on commission GST, reverse cancellations against the original sale period, and split B2C from MyBiz for correct place-of-supply on GSTR-1.
- **Config:** MMT settlement file connector keyed to booking ID; PMS folio adapter (Opera, IDS Next, eZee); GSTIN master with seller state and customer state; 194-O versus 194H decision rule per booking type; cancellation reversal logic by sale period.
- **Output:** A reconciled hotel ledger with each MMT booking matched to a PMS folio, gross room revenue at the correct GST slab, ITC on commission GST claimed, TDS reconciled to Form 26AS, and cancellation credit notes filed in the correct GSTR-1 period.

### Manpower Supply TDS: Why It Falls Under 194C, Not 194J

Source: https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india/

- **Problem:** CBDT confirms manpower supply (named-resource staffing under SoW) falls under Section 194C at 1% or 2%, not Section 194J at 10%. Incorrect deduction at 10% locks up working capital and forces a correction chain to recover the excess.
- **Logic:** Classify the contract — named-resource SoW with hourly or monthly billing points to 194C manpower supply, not 194J professional services. Check the client's certificate section code against the expected 1% (individual) or 2% (company) rate. If 10% was deducted under 194J, raise a correction request citing CBDT classification.
- **Config:** Vendor-master tag 'manpower supply = 194C' with hourly or monthly billing flag. Correction statement routed via TRACES. ITR-level fallback claim if the deductor correction fails.
- **Output:** Correctly classified vendor ledger, TDS refund recovery via deductor correction, protected ITR credit claim, and reconciled Form 26AS or Form 168 at year-end.

### Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams

Source: https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review/

- **Problem:** Manual bank statement review at scale produces inconsistent credit outcomes — signals missed on high-volume days, PSU bank formats skipped because they are unfamiliar, and NACH bounce patterns left unread due to truncated narration columns.
- **Logic:** Automated review uses a purpose-built Indian bank statement parser to extract 40+ signals from every file consistently — covering NACH return narrations, round-trip detection, income regularity, and PSU/co-operative bank format variants — regardless of analyst availability or statement quality.
- **Config:** The automated tool must be configured with Indian bank-specific OCR fallback, 300+ column variant mappings, and NACH return code normalisation to handle PSU and co-operative bank PDFs that generic tools reject.
- **Output:** A structured credit signal report produced in under 5 minutes per 12-month statement with a documented audit trail, replacing 90 minutes to 3 hours of manual extraction and enabling consistent outcomes across the full application volume.

### Manual vs Automated Reconciliation: The True Cost Comparison

Source: https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india/

- **Problem:** Spreadsheet-based reconciliation in India auto-matches only 51–65% of items, consumes 8–15 staff days per month for a mid-size company, and produces recurring errors in TDS rate application, GSTR-2B timing, and partial-payment allocation.
- **Logic:** Replace manual matching with deterministic multi-pass rules keyed on invoice, UTR, TAN, GSTIN, and settlement reference. Route the unmatched residue into a variance taxonomy so the team focuses only on genuine exceptions rather than re-keying matches. Benchmark matched rate uplift (target 88%) against the prior manual baseline to justify the spend.
- **Config:** Tolerance bands per reconciliation type, narration pattern library for NEFT/RTGS/UPI, Form 26AS and GSTR-2B connectors, and a parallel-run period for match-accuracy validation.
- **Output:** Close cycle compressed from 8–15 days to 1–2 days, documented ROI combining staff savings, recovered TDS and ITC credits, and a complete audit log of matches and approvals.

### Section 393(1) Sl. 8(ii) Purchase TDS for Manufacturing: Payment Code 1031, Legacy 194Q Cross-Era (FY 2026-27)

Source: https://www.terra-insight.com/insights/manufacturing-393-sl-8-ii-purchase-goods-reconciliation/

- **Problem:** From 1 April 2026, Indian manufacturers with prior-year turnover above ₹10 crore must deduct 0.1% TDS under Section 393(1) Sl. 8(ii) (replacing legacy Section 194Q, payment code 1031) on purchases from any resident vendor where aggregate purchase value in the financial year exceeds ₹50 lakh — while reconciling cross-era FY 2025-26 deductions filed under legacy 194Q. Section 206C(1H) (TCS on sale of goods on the seller side) is inapplicable since 1 April 2025; there is no successor TCS code for goods sale under the Income-tax Act 2025, so the historical buyer-TDS vs seller-TCS overlap no longer applies to new transactions.
- **Logic:** Build a per-vendor-PAN year-to-date purchase tracker that reads invoice value net of GST in posting sequence; trigger the 0.1% deduction flag from the invoice that takes cumulative purchase above ₹50 lakh; on every flagged invoice deduct 0.1% at credit-or-payment-whichever-is-earlier; deposit by the 7th of the following month under payment code 1031; obtain or issue the seller's Section 394 self-declaration to confirm precedence; reconcile monthly against Form 168 (buyer view) and quarterly against the seller's Form 26AS appearance.
- **Config:** Vendor master with PAN, prior-year buyer-turnover flag (above/below ₹10 crore), seller-turnover declaration (for Section 394 precedence determination), Section 393(1) Sl. 8(ii) threshold of ₹50 lakh per PAN per year reset on 1 April; payment code 1031 default for new deductions; legacy 194Q tag retained for cross-era references; correction-challan path via TRACES for both legacy and new tags.
- **Output:** A monthly Section 393(1) Sl. 8(ii) close pack showing per-vendor YTD purchase value, threshold-crossing date, deductions made under payment code 1031, deposits filed by the 7th of the next month, Form 168 buyer-view reconciliation status, seller GSTR-1 cross-tie on the underlying invoices, Section 394 seller-side precedence confirmations, and any cross-era 194Q items still open for FY 2025-26.

### AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%

Source: https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india/

- **Problem:** An Indian manufacturer's three-way match exception queue runs at 60-75% of invoices, ages into the 60-90+ day buckets, breaches MSME Section 43B(h) deadlines, and risks ITC claims crossing the Section 16(4) deadline — but the AP team cannot work the queue down because there is no priority routing, no tolerance configuration per vendor category, no escalation SLA, and no maker-checker on resolutions.
- **Logic:** Bucket every open exception by ageing (0-30, 31-60, 61-90, 90+) and by priority (Critical/High/Medium based on MSME flag, invoice value, ITC deadline proximity); apply per-vendor-category tolerance bands at the matching engine to reduce inflow; route exceptions by variance code to a documented owner with an SLA; require maker-checker sign-off on every resolution with value-banded approval thresholds; trigger weekly aged-exception escalation to the finance head.
- **Config:** Ageing buckets, priority tier rules (MSME, value, ITC deadline), variance-code-to-owner routing map, SLA per priority tier, maker-checker approval matrix by value band, write-off thresholds per variance code, and weekly escalation report to finance leadership.
- **Output:** A daily AP dashboard showing exceptions by bucket and priority, MSME 43B(h) breach alerts, ITC at-risk alerts, an owner accountability view, a write-off log with GL posting trail, and a monthly trend chart showing exception rate decline from 70% baseline toward sub-15% target.

### Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking

Source: https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation/

- **Problem:** Indian manufacturers commissioning multi-crore capital projects must claim ITC on capital goods invoices monthly as they appear in GSTR-2B, accumulate the underlying costs in CWIP until commissioning, transfer commissioned assets into the fixed asset register, exclude Section 17(5) blocked credits, and reverse part of the claimed ITC on any subsequent sale or disposal under the 60-month rule — and any drift between GSTR-2B, the CWIP ledger and the fixed asset register surfaces as a statutory audit finding with 18% interest exposure.
- **Logic:** Classify every capital invoice at receipt into eligible CG, Section 17(5) blocked, or input; claim eligible CG ITC in the GSTR-3B of the month the invoice appears in GSTR-2B; tag the underlying cost in CWIP with the originating GSTR-2B reference; on commissioning, transfer CWIP to the fixed asset register and propagate the GST reference; on disposal, retrieve the original ITC claim and compute the Rule 44 reversal at 5% per quarter of use against a 60-month useful life; compare with GST on disposal value and book the higher amount.
- **Config:** Capital goods invoice register tagged with HSN, GST rate, GSTR-2B match status, CWIP project code, Section 17(5) block flag, commissioning date placeholder, fixed asset register row reference; quarterly reconciliation between GSTR-2B inward CG total, CWIP movement and FAR additions; disposal trigger that retrieves original ITC and runs the 60-month reversal calculation.
- **Output:** A daily capital ITC dashboard showing GSTR-2B inward CG invoices by project and HSN, blocked-credit invoices held out with reason code, claimed-ITC totals tying to GSTR-3B Table 4(A)(5), CWIP balance reconciled to the sum of pending project codes, FAR additions reconciled to commissioned project costs, and a disposal queue showing Rule 44 reversal calculations with original ITC and quarters of use.

### Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching

Source: https://www.terra-insight.com/insights/manufacturing-reconciliation-india/

- **Problem:** Indian manufacturers run five distinct reconciliation rails simultaneously — procurement three-way matching, inventory and stock transfers, GST/TDS/TCS tax compliance, vendor payment runs, and Section 143 sub-contractor job-work — each with different data sources, exception types, and statutory timelines, producing AP exception rates of 60-75% when handled on spreadsheets.
- **Logic:** Run each rail with its own matching window and variance taxonomy: three-way PO-GRN-invoice with price (0-5%) and quantity (0-3%) tolerance bands; inventory by stock-transfer document and bin location; tax by Section 393/394 TDS code and GST ITC eligibility under Section 17(5); vendor payment by UTR-to-invoice match; Section 143 job-work by challan-to-return reconciliation with the 1-year (inputs) and 3-year (capital goods) return windows.
- **Config:** Vendor master with PAN, GSTIN, MSME status, TDS rate per Section 393 code, tolerance band per item category, GRN-to-invoice matching window in days, plant-wise GSTIN mapping, Section 143 job-work challan series, scrap TCS Section 394 collection ledger and AP exception ageing buckets (30/60/90+).
- **Output:** A daily AP close where matched invoices route to payment, exceptions route to the ageing queue by variance code (UNDER_INVOICED, OVER_INVOICED, PARTIAL_QTY, GST_MISMATCH, VENDOR_PAN_MISMATCH, RATE_VARIANCE), TDS deductions tie to the monthly 393 payment challan, scrap TCS ties to the quarterly 394 return, GST ITC ties to GSTR-2B with Section 17(5) blocked credits removed, and Section 143 job-work challans tie to their return within statutory windows.

### Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)

Source: https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394/

- **Problem:** Manufacturing scrap disposal creates a four-leg reconciliation: the scrap sale ledger (recognition of revenue), the TCS collected ledger (1% under Section 394 code 1071), the quarterly Form 27EQ return (which must include every buyer's PAN), and the bank receipt from the scrap buyer (which must include both the scrap value and the TCS amount) — plus a cross-era handling problem when FY 2025-26 sales under legacy Section 206C(1) are reconciled by buyers in FY 2026-27.
- **Logic:** Tag every scrap sale invoice with Section 394 code 1071 (FY 2026-27 onwards) or legacy 206C(1) reference (pre-1-April-2026); compute TCS at 1% on the scrap sale value (excluding GST); accrue collected TCS to a payable ledger; remit monthly through the TCS challan; file Form 27EQ quarterly with buyer PAN mapping; issue Form 27D from TRACES; reconcile bank credit to scrap sale plus TCS; on the buyer side, map Form 27D to Form 26AS and to the buyer's purchase ledger.
- **Config:** Scrap item master with HSN code, GST rate and TCS applicability flag; buyer master with PAN and GSTIN; Section 394 payment code 1071 with cross-era legacy 206C(1) reference; monthly TCS challan calendar (7th of following month); quarterly Form 27EQ filing window; bank receipt mapping rule (scrap value + TCS = expected credit).
- **Output:** A monthly close where every scrap invoice ties to a scrap sale entry, TCS collected ties to the monthly challan and quarterly Form 27EQ, bank credit reconciles to invoice + TCS, Form 27D is downloadable for every buyer, cross-era references (pre-Apr-2026 sales under 206C, post-Apr-2026 sales under 394) are visible side by side, and the buyer-side Form 26AS reconciliation closes within the quarterly cycle.

### Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports

Source: https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india/

- **Problem:** E-commerce sellers lose 2-3% of gross payment volume to undetected marketplace fee errors — wrong commission categories, weight overcharges, and unreversed return fees.
- **Logic:** Decompose each settlement into commission + shipping + TCS + TDS + returns. Compare commission rate against product category master. Validate volumetric weight against actual weight. Verify return fee reversals within 90-day SAFE-T window.
- **Config:** Commission rates 2-22% by category, volumetric weight formula L×W×H/5000, SAFE-T claim window 90 days, settlement report retention 90 days, TCS at 0.5% on net taxable supplies.
- **Output:** Fee variance report by error type, overcharge recovery claims with SAFE-T filing support, and monthly settlement reconciliation with order-level P&L.

### Section 9(5) GST Liability on Marketplaces for D2C Sellers: Who Pays Tax

Source: https://www.terra-insight.com/insights/marketplace-section-9-5-gst-d2c-india/

- **Problem:** D2C brands operating across multiple commercial models on marketplaces and eCommerce platforms must correctly classify each sale under Section 9(5) deemed-supplier rules, Section 52 TCS ordinary marketplace facilitation, Section 9(3) and 9(4) RCM on input services, or ordinary forward-charge B2B treatment, where mis-classification on cloud-kitchen and accommodation flows leads to double GST exposure and platform-settlement reconciliation errors that compound across months.
- **Logic:** Tag every sale by GST treatment regime at order ingestion — Section 9(5) (operator-as-deemed-supplier), Section 52 (ordinary marketplace with TCS), Section 9(3) or 9(4) RCM (on inward supplies), ordinary forward charge. Build separate GSTR-1 reporting buckets per regime. For Section 9(5) supplies, expect platform settlements net of commission and without GST element. For Section 52 supplies, expect TCS at 1 percent reflected in GSTR-2B via operator's GSTR-8.
- **Config:** Sale classification rules per platform per SKU per service category, Section 9(5) notified-category register with effective dates, Section 52 TCS rate and reporting calendar, RCM supplier categorisation per Section 9(3) and 9(4), GSTR-1 outward-supplies bucket mapping, and reconciliation rules per regime.
- **Output:** Sales correctly classified by GST regime per platform; GSTR-1 reporting cleanly split between Section 9(5), Section 52, and ordinary forward charge; double GST exposure eliminated on cloud-kitchen and accommodation flows; Section 52 TCS credit per platform reconciled to GSTR-2B; RCM liability and corresponding ITC tracked separately in GSTR-3B; board-ready net realisation view per platform per regime.

### Maruti e-Nagare for Delivery Schedule Reconciliation: A Finance Team Guide

Source: https://www.terra-insight.com/insights/maruti-e-nagare-delivery-reconciliation-india/

- **Problem:** Maruti Suzuki Tier-1 suppliers operate inside a daily e-Nagare delivery rhythm with rolling daily firm plus weekly forecast call-offs, JIS sequencing for line-side supply, plant-coded billing across Gurgaon / Manesar / Suzuki Motor Gujarat / Kharkhoda, fortnightly or monthly settlement, and vehicle-programme attribution across 12 active programmes. Finance teams that do not run a disciplined daily-extract-to-weekly-reconciliation routine carry CUM drift, ASN-vs-GRN gaps, debit-note backlog and Section 393 TDS reconciliation breaks into the month-end.
- **Logic:** Daily e-Nagare extract per plant — firm call-off, ASN log, GRN log. Weekly reconciliation routine per plant per scheduling agreement: SA-release-ASN-GRN with CUM-required vs CUM-shipped vs CUM-received four-way match, delivery-tolerance handling, JIS sequence-mismatch exception queue. Periodic GST e-invoice tied to OEM-confirmed received quantity, not raw ASN. Fortnightly or monthly settlement reconciliation: payment advice decomposed by debit reason, Section 393(1) Sl. 6(i).D(b) / 393(1) Sl. 8(ii) TDS deduction reconciled to Form 168 / Form 26AS. Programme-level cumulative margin tracked per vehicle programme.
- **Config:** Maruti customer master with plant-code sub-records (Gurgaon, Manesar A/B/C, SMG Hansalpur, Kharkhoda) and programme-code sub-records (Brezza, Swift, Baleno, Dzire, WagonR, S-Presso, Ertiga, Ciaz, Grand Vitara, Jimny, Fronx, Invicto). e-Nagare daily-extract templates (call-off CSV, ASN log, GRN confirm). Periodic GST e-invoice generator against confirmed-received quantity. Debit-note reason taxonomy per Maruti Supplier Quality Manual. Section 393(1) Sl. 6(i).D(b) and 393(1) Sl. 8(ii) TDS receivable registers. Section 34 GST credit-note calendar (30 November next FY).
- **Output:** A per-plant, per-programme Maruti reconciliation pack tying scheduling agreement to release to ASN to GRN to periodic invoice to payment advice. JIS sequence-mismatch exception queue at the operational layer. Programme-level cumulative margin tracker (parts shipped × per-part rate minus programme-attributable FOMP / tooling / PPM penalty). Section 393(1) Sl. 6(i).D(b) and 393(1) Sl. 8(ii) TDS deducted reconciled to Form 168 / Form 26AS. Year-end audit position defensible from e-Nagare archive plus IDoc trail.

### Maruti Suzuki Supplier Settlement Process: Payment Terms, Debit Notes, and Reconciliation

Source: https://www.terra-insight.com/insights/maruti-suzuki-supplier-settlement-process-india/

- **Problem:** Tier-1 suppliers to Maruti Suzuki operate inside a specific settlement regime — T+45 to T+60 payment cycle from GRN date, e-Nagare as the portal touchpoint, plant-coded billing across Gurgaon / Manesar / Suzuki Motor Gujarat Hansalpur / Kharkhoda, programme-specific debit-note formats and FOMP running accounts, rolling 12-month PPM thresholds with contractual penalty bands, and vehicle-programme-level margin tracking across the 12-programme passenger-car portfolio. The reconciliation engine must handle all five dimensions simultaneously for a ₹150 crore-annual Maruti book to close month-end on time.
- **Logic:** Decompose each Maruti settlement at the plant-code level (Gurgaon / Manesar / SMG Hansalpur / Kharkhoda), tie each invoice and debit memo to the source vehicle programme (Brezza / Swift / Baleno / etc), classify debit reasons against the Maruti taxonomy, age each FOMP claim against the per-programme running account, monitor PPM rolling 12-month per part against contractual threshold, calendar Section 34 GST credit notes per accepted debit, and compute programme-level cumulative margin from parts-shipped × per-part rate minus programme-attributable deductions.
- **Config:** Maruti customer master with sub-records per plant code and per vehicle programme, e-Nagare export-mapping for daily call-off / ASN / GRN / settlement-statement parsing, debit-note reason taxonomy aligned to Maruti's Supplier Quality Manual codes, FOMP running account per programme, PPM threshold matrix per part with rolling 12-month window, tooling cap and recovery rate per programme, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-plant, per-programme Maruti settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with FOMP / tooling / PPM penalty attribution, e-Nagare-sourced delivery-schedule reconciliation, rolling-PPM dashboard per part against threshold with breach alerts, and Section 34 GST credit-note action queue keyed to approaching cutoff.

### MAT/AMT vs PLI Textile Claim — Tax Treatment Reconciliation

Source: https://www.terra-insight.com/insights/mat-amt-pli-textile-claim-tax-treatment-reconciliation/

- **Problem:** A tier-1 or tier-2 Indian textile mill receiving a PLI Scheme for Textiles claim payout must simultaneously reconcile the receipt across four regulatory surfaces: the DPIIT / Ministry of Textiles claim file and Project Management Agency certification; the Ind AS 20 government-grant accounting policy (grant related to income versus grant related to an asset, and matching to cost period or asset useful life); the income-tax treatment as revenue receipt taxable under Section 145B or capital receipt with potential Section 43(1) explanation 10 reduction of depreciable asset base; and the Section 115JB MAT computation (or Section 115JC AMT for non-corporates) where book profit or adjusted total income flows through the accounting treatment. Divergent classification across the four surfaces produces MAT liability spikes, deferred tax exposure, and audit qualifications, and misalignment between the DPIIT claim register and the accounting register is a frequent Section 143(3) scrutiny finding.
- **Logic:** Build a PLI claim register keyed by claim year, base-year and current-year turnover on eligible MMF or technical textile products, and minimum investment threshold (₹100 crore or ₹300 crore). For each claim disbursement, record the accounting classification under Ind AS 20 — grant related to income with matched cost period, grant related to an asset with deferred income or asset cost reduction — and the amortisation schedule if applicable. Cross-reference to the fixed-asset register where any portion is attributed to specific plant and machinery for potential Section 43(1) explanation 10 reduction. Cross-reference to the income-tax computation where the revenue-nature portion is included under Section 145B in the year of receipt, or where the capital-nature position is taken with supporting legal opinion and disclosure. Cross-reference to the MAT computation where the P&L credit (whether current-year revenue recognition or annual amortisation of deferred income) enters book profit under Section 115JB Explanation 1. Track deferred tax on any timing difference between accounting and tax recognition.
- **Config:** PLI claim master with claim year, disbursement date, disbursed amount, PMA certification reference, incremental turnover on eligible products, minimum investment threshold applicability, and product-mix declaration. Ind AS 20 accounting policy setting: grant related to income (matched cost period) or grant related to an asset (deferred income versus asset cost reduction), with the matched period configured in months. Fixed-asset register linkage: mapping of PLI receipt (if any) to specific plant and machinery blocks for Section 43(1) explanation 10 depreciable-base reduction; depreciation recomputation under Section 32 on the reduced base. Income-tax classification setting: revenue receipt under Section 145B (default for turnover-linked PLI) or capital receipt (with legal opinion reference and appellate history); disclosure schedule. MAT computation: book profit build-up under Section 115JB with the accounting recognition flowing through; AMT computation under Section 115JC for non-corporates with Section 145B revenue flowing into adjusted total income. Deferred tax schedule for timing differences between accounting and tax recognition.
- **Output:** A year-end four-register crosswalk pack. Register one prints the DPIIT / PMA claim file with disbursement dates and certified quantities. Register two prints the Ind AS 20 accounting recognition — current-year P&L credit, deferred income roll-forward, or asset cost reduction — with policy disclosure text ready for the notes to accounts. Register three prints the income-tax computation with Section 145B inclusion (or Section 43(1) explanation 10 depreciable-base reduction if capital-receipt position) and the deferred tax working. Register four prints the Section 115JB MAT computation showing book profit, MAT liability at 15 percent plus surcharge and cess, and the credit under Section 115JAA, or the Section 115JC AMT computation for non-corporates. The pack surfaces MAT liability driven by PLI receipt, the deferred tax impact of any accounting-tax timing difference, and the audit-ready policy disclosure for the notes to accounts.

### MDR Charged on Zero-MDR UPI / RuPay Debit: The Most Common Leakage Pattern

Source: https://www.terra-insight.com/insights/mdr-charged-on-zero-mdr-upi-rupay-debit-leakage-india/

- **Problem:** Payment gateways routinely apply a flat platform percentage against UPI bank-account and RuPay debit volume where the network MDR is mandated zero, mis-label the resulting line as 'MDR' on settlement files, or both. For a UPI-heavy merchant this is the single largest fee-leakage class because the over-billed base is the largest volume cell in the method mix.
- **Logic:** Decompose every settlement line into instrument, network, network MDR, platform fee, and GST. Flag any non-zero network-MDR component on instrument equal to UPI (bank account) or network equal to RuPay debit. Reconcile the platform-fee line against the contracted enterprise rate per network, not against the headline gateway card.
- **Config:** Per-gateway, per-network MDR rule set with zero-MDR enforcement on UPI bank-account and RuPay-debit cells; instrument classifier that splits UPI into bank-account, RuPay-credit-on-UPI, and PPI-on-UPI; contracted-rate table per gateway separated from published-rate baseline; GST line isolator at 18% on fee only.
- **Output:** Per-network effective-rate report (fees divided by network volume) reconciled to contracted rate, a transaction-level exception list flagging every non-zero MDR on a zero-MDR instrument with rupee-quantified recovery, and a gateway-dispute pack the CFO or controller can hand to the gateway account manager with the regulatory citations.

### MDR fee reconciliation — verifying gateway charges against contracted rates

Source: https://www.terra-insight.com/insights/mdr-fee-reconciliation/

- **Problem:** MDR is not a flat rate — it varies by instrument (1.5-2.5% credit, 0.4-0.9% debit, 0% UPI under ₹2,000, 2.5-3.5% international, flat ₹10-25 net banking). A single mis-applied rate (credit rate on a debit transaction) silently accumulates material cost, while 18% GST on MDR is a recoverable ITC if matched to the gateway tax invoice.
- **Logic:** Matching recomputes the expected MDR per transaction using the instrument type, card BIN, domestic or international flag, and the merchant's rate card, then compares to the actual MDR deducted in the settlement. FEE_DEDUCTION variance is raised when the applied rate differs from the contracted rate. GST on MDR is cross-matched against the gateway's monthly GST invoice and GSTR-2B for ITC claim.
- **Config:** Rate-card engine keyed on instrument plus card network plus domestic or international, FEE_DEDUCTION tolerance threshold, and monthly GST-invoice matcher to GSTR-2B.
- **Output:** Per-transaction MDR variance report with recoverable over-charges, rate-dispute ticket list for gateway support, reconciled MDR expense book entry, and ITC-claim schedule for GST on MDR.

### MDR Not Reversed on Refunds and Chargebacks: The Compounding Cost

Source: https://www.terra-insight.com/insights/mdr-not-reversed-on-refunds-india/

- **Problem:** Indian merchants book gross GMV at the point of sale and lose MDR on every transaction; when the customer is refunded or charges back, the original MDR stays with the gateway and the loss is silent. Most ERP and finance stacks do not surface this as a discrete line — refunds reverse the sale and the MDR loss vanishes into general gateway expense, while chargebacks add a dispute fee that is usually netted off in the settlement without a contractual cross-check. For a subscription business with monthly cancellations the cost compounds across the subscriber lifetime.
- **Logic:** Refund-MDR reconciliation joins each refund event in the settlement file to the originating sale's MDR line and computes the retained MDR (full original MDR minus any partial rebate per the merchant's contract). Chargeback reconciliation matches each dispute event against the contracted per-dispute fee schedule keyed on network and scope (domestic / international), and separately tracks the transaction-value debit. A monthly aggregation surfaces the three variance classes (REFUND_MDR_LOSS, CHARGEBACK_DISPUTE_FEE, CHARGEBACK_TXN_LOSS) by gateway, network and SKU.
- **Config:** Refund-MDR retention flag per gateway rule (default: retain 100 percent; enterprise contracts may carry a partial rebate); per-dispute fee schedule per network and scope; chargeback variance classes (REFUND_MDR_LOSS, CHARGEBACK_DISPUTE_FEE, CHARGEBACK_TXN_LOSS); monthly aggregation report by SKU / subscription-tier for subscription businesses; GST-on-fee retention line for the 18 percent component that does not reverse with the sale.
- **Output:** A monthly refund-and-dispute cost dashboard with three discrete variance lines, a per-SKU and per-subscription-tier ranking of refund-MDR loss for the marketing and product teams, a chargeback dispute-fee reconciliation against the contracted rate card with overcharge flags, and an audit-ready trail of the retained MDR and the GST that did not reverse with the underlying sale.

### Medical Devices at 5%: HSN 9018–9022 Rate-Change Reconciliation

Source: https://www.terra-insight.com/insights/medical-device-hsn-9018-9022-18-to-5-percent-rate-change/

- **Problem:** A medical-device manufacturer with an approximately Rs 850 crore annual portfolio (illustrative) spanning surgical instruments under HSN 9018, diagnostic devices under HSN 9018 and 9022, and X-ray apparatus under HSN 9022 must re-invoice every SKU after the 56th GST Council rate change effective 22 September 2025 — output GST drops from 18 percent to 5 percent while stainless steel inputs under HSN Chapter 72, medical-grade plastics under HSN Chapter 39, imported in-vitro diagnostic reagents under HSN Chapter 38, and packaging and sterilisation services stay at 12 or 18 percent. Ceiling-price-controlled devices under DPCO 2013 (cardiac stents, orthopaedic implants per NPPA notification) require MRP recalculation to pass the price benefit to the end-consumer; non-price-controlled devices retain the margin. The reconciliation surfaces are a SKU-wise MRP recalculation register keyed to NPPA scheduled versus non-scheduled classification, a straddle-invoice register reconciling pre-versus-post-22-September dispatches under Section 12 CGST time-of-supply rules, a Rule 89(5) monthly Form RFD-01 refund workbook against the deepened inverted-duty accumulation, and a Section 15(3) treatment matrix for post-supply MRP-transition credit notes issued to distributors on pre-cutover channel inventory.
- **Logic:** Build a SKU master keyed to HSN code (9018, 9019, 9020, 9021, or 9022), NPPA scheduled/non-scheduled flag, pre-22-September MRP, ex-tax ceiling value (for scheduled SKUs), and post-22-September recomputed MRP. Run the MRP recalculation on scheduled SKUs mechanically — post-cutover MRP equals ex-tax ceiling plus 5 percent (versus pre-cutover ex-tax ceiling plus 18 percent). Extract the invoice register split by date of removal, date of invoice, date of e-way bill IRN, and date of e-invoice IRN; classify each invoice as pre-cutover 18 percent or post-cutover 5 percent by the earlier of invoice date and payment receipt date per Section 12 CGST. Compute the inverted-duty position monthly — output GST at 5 percent on eligible turnover minus input GST at 12 to 18 percent on stainless steel, medical-grade plastics, IVD reagents, packaging (HSN 3923/4819), and sterilisation services — and file Form GST RFD-01 under the Rule 89(5) amended formula with input services and capital goods excluded from Net ITC. Maintain a Section 15(3) matrix by distributor by SKU flagging whether any MRP-transition credit note is pre-cutover-agreement-linked (Section 15(3) tax-adjustment eligible) or secondary discount (Section 34 commercial-only).
- **Config:** SKU master with HSN heading (9018/9019/9020/9021/9022), NPPA scheduled flag, DPCO Schedule I reference, ceiling ex-tax value, pre-cutover MRP, post-cutover MRP; input master with HSN chapter (72 stainless steel, 39 medical-grade plastic, 38 IVD reagent, 4819 corrugated carton, 3923 polymer pouch) and applicable GST rate; sterilisation service vendor register with vendor GSTIN and HSN 9987; e-invoice IRN and e-way bill number feed keyed by date of removal, date of invoice, and date of payment receipt; Section 12 CGST cutover flag on every invoice; Rule 89(5) refund workbook with Net ITC segregation (goods eligible, services and capital goods excluded per Notification 14/2022 and Union of India v. VKC Footsteps); distributor master with pre-22-September channel inventory tally by SKU and lot; Section 15(3) treatment matrix per distributor per credit-note event; Circular 92/11/2019-GST reference on secondary discounts.
- **Output:** A monthly medical-device rate-transition reconciliation pack: SKU-wise MRP recalculation register per NPPA scheduled versus non-scheduled classification with pre- and post-cutover MRP columns; straddle-invoice register reconciling every dispatch across 21-22 September 2025 by time-of-supply anchor and GST rate applied; monthly Form GST RFD-01 refund draft under Rule 89(5) with Net ITC segregation and the Notification 14/2022 amended formula; per-distributor Section 15(3) credit-note matrix with tax-adjustment eligibility flag; and a distributor channel-inventory reconciliation on pre-22-September stock that ties the manufacturer's credit-note liability to the distributor's GSTR-2B reversal. Match rate improvement on the rate-transition reconciliation chain supports a clean audit trail against Section 65 GST audit on the transition period and expedited RFD-01 processing per the GST Council FAQ Q25 pledge.

### Medical Device Supplier Reconciliation for Indian Hospitals

Source: https://www.terra-insight.com/insights/medical-device-supplier-reconciliation-india/

- **Problem:** Medical device suppliers park high-value implant stock at Indian hospitals on consignment, billing only on consumption, but the supplier's stock register, the hospital's theatre usage log, and the hospital's purchase invoice drift apart every cycle, leaving variance that is part real leakage and part timing.
- **Logic:** Build a three-way match keyed on SKU code, batch number, and sterilisation expiry date. Reconcile supplier register against hospital theatre log to confirm consumption, then reconcile theatre log against purchase invoice to confirm billing, then close the loop on closing stock at SKU-batch level.
- **Config:** GST slabs 5/12/18 percent by device category, TDS Section 393(1) Sl. 8(ii) code 1031 at 0.1 percent on goods leg, Section 393(1) Sl. 6(iii).D(a) code 1026 on bundled technical service leg, e-invoicing applicable above ₹5 crore turnover, Schedule I exposure on stock unconsumed beyond six months.
- **Output:** Per-SKU consumption variance, expired-batch write-off register, consignment ageing report defending against Schedule I reclassification, GSTR-2B reconciliation log of credit blocked or available by slab, exception queue for theatre-pack short-billing.

### Medical Representative Settlement and Expense Reconciliation in Indian Pharma

Source: https://www.terra-insight.com/insights/medical-representative-mr-settlement-india/

- **Problem:** Indian pharma companies disburse ₹4-12 lakh per MR per year across fixed salary, variable per-doctor incentive, sample distribution at landed cost, travel and DA, and CME support — with Section 17(2)(vi) perquisite exposure on unaccounted samples, UCPMP 2024 sample and gifting caps, CSR-vs-marketing expense classification, and Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) on contractor MR engagements all overlapping on the same expense ledger.
- **Logic:** Reconcile MR-wise sample issuance against doctor-acknowledged consumption with the unaccounted balance pushed into Section 17(2)(vi) perquisite at year end, variable incentive computed against per-doctor coverage achievement and reconciled to field activity logs, expense claim approved against territory norms and CSR-coded entries segregated from marketing-coded entries, and contractor MR payments TDS-deducted under Section 393(1) Sl. 6(i) (code 1023 at 1% Ind/HUF, code 1024 at 2% other) with PAN-aggregated annual thresholds tracked.
- **Config:** MR master keyed by employee or contractor flag, territory tier and therapeutic area; doctor master with registration number and UCPMP interaction history; sample ledger with batch and expiry tracking per MR; expense norm matrix by territory; per-doctor coverage and incentive band table; CSR-vs-marketing expense classifier rules; Section 393(1) Sl. 6(i) vendor rate matrix (code 1023 Ind/HUF, code 1024 other) for contractor MR agencies; Section 392 code 1001 payroll perquisite line for unaccounted samples.
- **Output:** A monthly reconciled view per MR showing salary plus variable plus expense plus sample distribution totals against the budget band, an unaccounted-sample exposure pushed to payroll as Section 17(2)(vi) perquisite, UCPMP breach flags per doctor where sample or hospitality caps are exceeded, CSR-vs-marketing expense allocation per cost centre, and the monthly TDS challan tied to Section 393(1) Sl. 6(i) contractor codes (1023/1024) on contractor MR agency payments.

### Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions

Source: https://www.terra-insight.com/insights/meesho-seller-reconciliation/

- **Problem:** Meesho advertises 0% commission but charges ₹30-80 forward plus return logistics per shipment and 1% Section 52 TCS on gross forward sales. In 30-40% return-rate fashion categories, return deductions plus return logistics create negative settlements carried into the next week, while TCS already booked in GSTR-2B requires a GSTR-8 reversal trail.
- **Logic:** Two parallel reconciliations run in lock-step. The cash-flow track matches Meesho settlement amount to bank credit and handles carry-forward negative balances without booking them as current-period expense. The tax track reconciles TCS deducted on gross forward sales against GSTR-2B Part II, then captures Meesho's revised GSTR-8 entries that reverse TCS on returned orders.
- **Config:** Logistics rate-card matcher by weight and zone, negative-settlement carry-forward ledger, Section 52 TCS reversal tracker for revised GSTR-8, and Form 26AS Part F cross-check.
- **Output:** Cash-accurate seller AR with carry-forward visibility, reconciled TCS credit net of return reversals, weight-dispute exception list for seller support, and revenue journal tied to forward and return orders.

### Medical Tourism Foreign Patient Revenue Reconciliation for Indian Hospitals

Source: https://www.terra-insight.com/insights/medical-tourism-foreign-patient-reconciliation-india/

- **Problem:** Foreign patient receipts arrive in foreign currency three to seven days after INR billing, with FX margins, SWIFT charges, and FIRC documentation gaps creating a multi-dimensional reconciliation that touches FEMA, GST exemption documentation, and Ind AS 21 FX accounting.
- **Logic:** Ingest HIS INR billing register, bank foreign-currency receipt feed, FIRC issuance register, and SWIFT MT103 narration; match by patient ID and invoice reference; compute FX gain/loss at transaction date vs receipt date; flag missing FIRCs against P0301 purpose code; segregate clinical services (GST-exempt) from ancillary services (GST-taxable) for each invoice line.
- **Config:** RBI purpose code P0301 medical treatment, GST Notification 12/2017 entry 74 healthcare exemption, FEMA Master Direction inward remittance reporting, Ind AS 21 FX treatment, AD-Category-I bank e-FIRC issuance window.
- **Output:** Per-patient FX gain/loss register, FIRC-pending ageing report, GST exemption documentation file by invoice, SWIFT-charge variance log, and a clinical-vs-ancillary revenue split for GST returns.

### MEIS Legacy Claim Reconciliation for Textile Exporters

Source: https://www.terra-insight.com/insights/meis-legacy-claim-reconciliation-textile-export/

- **Problem:** Textile exporters that ran MEIS claims through the six years to 2020 carry a legacy reconciliation surface — pre-January-2021 shipping bills, DGFT-issued scrips, BCD-utilisation records against imports through 2022-2023, and residual scrip balances — that has to close cleanly against a scheme that no longer accepts new filings and sits under a WTO SCM Panel Report finding. Undrawn MEIS eligibility on shipping bills that missed the 12-month filing window is permanently forfeit. Un-utilised scrips past 24-month validity expire and must be written off. Any post-audit denial by DGFT on ITC(HS) classification, FOB overstatement, or realisation shortfall triggers a scrip clawback plus interest that hits the P&L years after the original export. Manual tracking of the four legacy ledgers — shipping bill register, scrip issuance ledger, utilisation ledger, e-BRC realisation register — typically loses trace across ledger crossings and cannot support a DGFT post-audit at short notice.
- **Logic:** Freeze the pre-January-2021 shipping-bill register as of the sunset date with every shipping bill tagged by ITC(HS) code, FOB value in free foreign exchange, LEO date, MEIS reward country group (historical A/B/C), applicable MEIS rate under Appendix 3B, and computed MEIS entitlement. Map each shipping bill to its Form ANF-3A filing on the DGFT portal, capturing scrip number, scrip issue date, scrip amount, and 24-month validity end. Ingest the scrip utilisation ledger from customs Bills of Entry — every BoE with an MEIS scrip debit flag joins the utilisation register with scrip number, BoE reference, BCD amount debited, and residual scrip balance. Reconcile against the DGFT scrip-balance extract on a cut-off basis. Track e-BRC realisation for every shipping bill in the register against the FOB value — realisation shortfall risks partial scrip clawback under the whichever-is-less rule. Age residual scrip balances against 24-month validity and write off expired balances with statutory audit disclosure.
- **Config:** Legacy shipping-bill register cut-off — LEO date on or before 31 December 2020 (universal MEIS sunset for all product categories transitioned to RoDTEP). ITC(HS) code master with applicable MEIS rate under Appendix 3B and reward country group; MEIS scrip register with scrip number, DGFT issue date, scrip amount, 24-month validity end; Bill of Entry register with import date, BoE reference, ITC(HS) code, BCD amount, MEIS scrip debit flag with scrip number reference; e-BRC register from the export banker with SB number, realised FOB in INR and USD, realisation date; DGFT scrip-balance extract on a monthly cut-off; WTO DS541 audit-risk flag on scrips issued after 1 October 2020 (highest post-issuance audit intensity zone); write-off policy for un-utilised scrips past 24-month validity.
- **Output:** A closed-perimeter legacy MEIS reconciliation pack: pre-2021 shipping-bill register with computed entitlement, ANF-3A filing status per shipping bill, scrip issuance ledger with residual balance, scrip utilisation register mapped to Bills of Entry, e-BRC realisation status per shipping bill, and an expiry ageing report showing scrip balances approaching or past 24-month validity. Post-audit response pack — for any DGFT enquiry, the platform can produce the shipping bill, ITC(HS) classification support, FOB verification, e-BRC realisation proof, and scrip utilisation trail for any legacy claim within one working day. Write-off schedule for un-utilised residual scrip balances feeds the statutory audit disclosure and the tax return.

### Metal Kitchenware FMCG GST 2.0 Reconciliation (stainless steel, aluminium, copper)

Source: https://www.terra-insight.com/insights/metal-kitchenware-fmcg-gst-2-0-reconciliation/

- **Problem:** Metal kitchenware brands manufacturing stainless steel (HSN 7323), aluminium (HSN 7615), and copper (HSN 7418) cookware saw output GST consolidate from 18% to 5% under CBIC Notifications 09-16/2025-CTR effective 22 September 2025. The reconciliation surface fans out across three levels — manufacturer, distributor, and retailer — with a Rule 42 ITC reversal required on 22 September closing stock where inputs were procured at 18%, a scheme-reimbursement straddle where pre-transition invoices settle months later at the original 18% rate, and a persistent boundary confusion at the distributor DMS level between metal cookware at 5% and plastic kitchenware (HSN 3924) that remained at 18%.
- **Logic:** Build a rate-effective-date register keyed by HSN and effective from 22 September 2025; every SKU carries the correct 8-digit HSN from the brand master; every invoice line resolves output GST from HSN plus supply date. Run a Rule 42 reversal engine against the 22 September closing stock report — reversal formula compares ITC on inputs consumed in stock against output tax at the new 5%. Match scheme accruals to payouts by scheme code, distributor GSTIN, and original invoice reference; enforce that credit notes cite the invoice's original tax rate, not the current tariff. Cross-check distributor DMS SKU-to-HSN mapping monthly to catch metal-vs-plastic mis-classification before the GSTR-1 cycle.
- **Config:** SKU master with 8-digit HSN, effective-date range, and composite-article flag for combo boxes; input master with GST rate at time of procurement; scheme master with Section 15(2) treatment flag and rate-effective-date; closing-stock report at 21 September 2025 EOD (final day of old regime); Rule 42 reversal formula; distributor DMS HSN sync report; credit-note engine with rate-lookup against original invoice; job-work contractor master with PAN classification for Section 393(1) Sl. 4 (1001 vs 1023) TDS.
- **Output:** A GST 2.0 reconciliation pack for metal kitchenware: closing-stock ITC reversal amount posted in September 2025 GSTR-3B; a pre/post-22-September accrual register with scheme payouts routed to the correct rate; distributor DMS HSN classification exceptions surfaced with SKU-level remediation; a plastic-vs-metal boundary audit report on composite products; and a fabricator-TDS reconciliation to Form 26AS at PAN level using the new Section 393(1) Sl. 4 codes.

### Gold Metal Loan Reconciliation: Price Fixation on Delivery vs Invoice Day

Source: https://www.terra-insight.com/insights/metal-loan-gold-price-fixation-delivery-day-vs-invoice-day-india/

- **Problem:** Indian jewellery manufacturers borrow physical gold on loan basis from RBI-nominated banks and designated bullion dealers under Master Direction FED.36 for production runs. The price of the borrowed gold is fixed on the actual delivery day to the manufacturer's vault, not the loan sanction day or the invoice-booking day — a rule imposed by RBI to prevent price arbitrage between sanction and delivery. Finance teams that book the loan liability at the sanction-day rate for GL neatness create a systematic price gap that pollutes manufacturing cost accounting for the entire production run, distorts gross margin at jewellery sale, and surfaces as an unreconciled MTM at loan repayment. Layer on the GST treatment ambiguity of GML interest, forward-hedge accounting under Ind AS 109, and CARO 2020 disclosure on year-end outstanding, and the metal loan reconciliation becomes the largest working-capital control point in the jewellery category.
- **Logic:** Build a per-GML-lot register keyed by loan sanction reference, nominated-bank counterparty, sanction date, delivery date, gold weight in grams, delivery-day price per gram, and rupee liability at delivery. Book the inventory receipt and the corresponding gold-loan payable at the delivery-day price with a Section 15(2) note on interest treatment. For every GML lot, link the matching forward or futures hedge (MCX contract number, notional, hedge documentation reference) and the manufacturing job cards it funds. At each month-end, mark the outstanding GML lots to the closing gold reference price and post the MTM movement to OCI (if hedge-accounted) or P&L (if not). At loan repayment or roll-over, close the loop on the delivery-day price versus repayment-day price and reconcile the interest invoice against the taxable-versus-exempt treatment agreed with the nominated bank. At year-end, run a CARO 2020 reconciliation of gold weight held under GML, vault physical count, and outstanding GML liability.
- **Config:** GML lot master with sanction reference, nominated-bank counterparty (with GSTIN and PAN), sanction date, delivery date, gold weight in grams, delivery-day price per gram from RBI/Ahmedabad reference or LBMA reference, rupee liability at delivery, and interest rate per annum; forward-hedge master with MCX/OTC contract number, notional, contract date, expiry, hedge documentation reference, and effectiveness test method; job-card master linking GML lot to manufacturing run and finished jewellery SKU; interest-invoice register with GSTIN, taxable value, GST rate flag (taxable at 18% under SAC 9971 or exempt under Serial 27), and ITC claim status; month-end MTM reference price feed; Section 393(1) Sl. 8 (194Q) TDS trigger for cash-settlement payment legs on gold purchase above threshold.
- **Output:** A month-end GML reconciliation pack: opening gold-loan liability in kilograms and rupees, period sanctions with delivery-day prices, period repayments with repayment-day prices, closing liability, month-end MTM movement (split by OCI-eligible cash-flow hedge and non-hedge P&L), and per-lot ageing to loan maturity. A hedge-effectiveness register per Ind AS 109 covering documentation, effectiveness test result, and any hedge de-designation. A GST interest-invoice register showing the taxable-versus-exempt determination per nominated-bank counterparty. A CARO 2020 year-end pack reconciling vault physical count, GML outstanding weight, and inventory ownership disclosure. A manufacturing-cost trace linking each finished jewellery SKU back to the GML lot that supplied its gold, resolving the gross-margin distortion that would otherwise sit in a bulk cost-of-goods-sold journal.

### Metro Cash & Carry FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/metro-cash-carry-fmcg-settlement-german-cnc/

- **Problem:** Metro Cash & Carry's settlement file inherits Metro AG's German-GAAP-derived format — separate Wareneingang and Rechnungseingang line types, EUR-convention rounding, and CnC-specific Sondervergütung/membership-margin columns — even after the 2023 Reliance Retail acquisition aligned the payment cycle to the Reliance Smart 10-day window. Brands must reconcile three independent legs: the brand's tax invoice, Metro CnC's GRN (physical receipt + fiscal receipt as two distinct settlement-file lines), and the van-tally distributor's dock-acceptance sheet. Without a three-way match aligned to the new RRVL cadence, brands either over-recognise revenue on rejected goods or fail to recover Section 15(2) GST relief on membership-margin reimbursements within the Section 34 credit-note window.
- **Logic:** Build a daily Metro CnC reconciliation engine that ingests three feeds: brand dispatch invoices keyed by Metro PO number, GSTIN, HSN, and quantity; Metro CnC settlement file parsed to separate Wareneingang (goods-receipt) lines from Rechnungseingang (invoice-receipt) lines, with Sondervergütung and Membership Allowance deduction lines tagged separately; van-tally distributor dock-acceptance sheets keyed by truck number, delivery date, and dock acknowledgement. Cross-match all three on Metro PO + dispatch invoice number. Classify each deduction line as Section 15(2) qualifying (membership margin with prior agreement and ITC reversal certificate), Section 15(2) non-qualifying (post-dispatch deduction without prior agreement), or short-supply recovery (quantity gap between dispatch invoice and Wareneingang line). Drive Section 34 credit-note issuance from the qualifying bucket within the 30 November window.
- **Config:** Metro CnC vendor master with GSTIN, store/DC code, RRVL alignment date, settlement cadence (10 days post-RRVL), and rate-effective dates per HSN spanning the 22 September 2025 GST 2.0 transition; brand-invoice schema with Metro PO + dispatch invoice + GSTR-1 cross-reference; Wareneingang/Rechnungseingang line-type parser; Sondervergütung and Membership Allowance deduction code map with Section 15(2) treatment flag per scheme; van-tally distributor master with PAN, GSTIN, dock-acceptance template, and Section 393(1) Sl. 18 (legacy 194H) commission TDS rate; three-way match tolerance bands (typically 0.5% on quantity, 0.1% on value to absorb EUR-convention rounding); 10-day cycle close cadence aligned to RRVL settlement window.
- **Output:** A 10-day rolling Metro CnC settlement reconciliation pack: per-PO three-way match status (closed clean / short-supply gap / over-invoice gap / pending van-tally), Wareneingang vs Rechnungseingang variance per PO with contingent-recovery flag, Sondervergütung and Membership Allowance deduction register split by Section 15(2) treatment, GSTR-1 credit-note schedule for qualifying deductions within the Section 34 window, van-tally distributor TDS register for Section 393(1) Sl. 18 commission, and a dispute escalation queue for gaps not resolved within the 10-day RRVL cycle.

### Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation

Source: https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india/

- **Problem:** Microsoft Dynamics 365 Business Central (v23+) and Finance & Operations (10.0.34+) ship with Indian localisation for GST tax determination, TDS deduction, and e-invoice IRP integration but do not pull GSTR-2B from the GST portal, do not match Form 26AS against TDS receivable, and do not disaggregate NACH batch credits from NPCI response files.
- **Logic:** Bolt an external reconciliation layer via one of three integration patterns: OData REST API for standard entities (VendInvoice, GeneralJournalAccountEntry, BankStatementLine) with OAuth 2.0, Data Management Framework (DMF) for batched CSV/Excel export and import through the DMF job scheduler, or Dataverse integration for Business Central feeding Power Automate and external tools.
- **Config:** D365 connector with OData endpoint registry, DMF export templates for GL, AP, AR, bank statement entities, OAuth 2.0 credentials, Dataverse entity mapping for BC, and GSTR-2B JSON, Form 26AS, and NACH NPCI file adapters on the external side with writeback to D365 via DMF import.
- **Output:** A reconciled D365 ledger with statutory (26AS, GSTR-2B) and NACH variances all matched externally and cleared back into BC or F&O — TDS receivable, ITC, and customer receivables reliable at close across Indian entities on Microsoft's ERP stack.

### Mid-Month MDR Rate Renegotiation: Two Rates Both Correct

Source: https://www.terra-insight.com/insights/mid-month-mdr-rate-renegotiation-streaming-payment-gateway-india/

- **Problem:** An MDR renegotiation with the payment aggregator that lands mid-month produces one settlement file with two correct MDR rates. A reconciliation that applies a single flat rate across the month either under-deducts (recording higher net revenue than reality) or over-deducts (booking a false shortfall against the gateway). The variance is not real — both rates are contractually correct within their effective windows — but a finance team that flags every transaction against a single reference rate will spend the month investigating differences that will never resolve.
- **Logic:** Store MDR rates in a rate-schedule table keyed by effective-from date, not as a single monthly constant. For each transaction on the settlement file, select the rate whose effective-from is the greatest date less than or equal to the transaction capture timestamp. Compute expected MDR as gross value × selected rate + applicable input GST on MDR, and match against the deduction reported on the settlement file within a tolerance that absorbs rounding differences at the paisa level.
- **Config:** Rate-schedule table with effective-from date, MDR percentage, and applicable card/instrument scope; capture-timestamp field on every settlement row; tolerance threshold for paisa-level rounding; separate branches for zero-MDR instruments (UPI and RuPay Debit under the 30 December 2019 zero-MDR notification) so no rate is applied at all; input GST rate on MDR (18% CGST + SGST or IGST) applied on top of the base MDR.
- **Output:** MDR variance report split into old-rate transactions and new-rate transactions with reconciled totals per bucket; capture-vs-settlement date split for cross-window transactions; matched-within-tolerance count and unmatched-outside-tolerance count; audit-ready evidence pack showing that the settlement file matches the rate schedule.

### Milestone Billing Reconciliation for IT Services Companies in India

Source: https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services/

- **Problem:** IT services companies with 40+ active fixed-price contracts have 120+ open milestones at any time, and revenue recognition depends on deliverable sign-off dates that lag invoice dates by weeks.
- **Logic:** Match milestone sign-off to invoice generation, track partial payments against milestone value, reconcile TDS deducted by client against Form 26AS credits, validate revenue recognition timing.
- **Config:** Section 194J at 10% or 194C at 1-2% depending on contract classification, milestone sign-off as revenue trigger, Form 26AS quarterly reconciliation window.
- **Output:** Milestone-to-cash tracker, TDS receivable register by client, revenue recognition schedule aligned to sign-off dates, and contract-wise profitability report.

### Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts

Source: https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india/

- **Problem:** Indian EPC engineering companies executing ₹50-500 crore long-cycle contracts must recognise revenue under Ind AS 115 / Ind AS 11 percentage-of-completion over time, raise 8-15 RA (Running Account) bills with mobilisation advance recovery and retention deduction layered in, trigger GST liability on each RA bill date and on advance receipts under Section 13 of the CGST Act, navigate the certified-vs-uncertified gap creating unbilled revenue on the balance sheet, deduct contractor TDS on RA bills under Section 393(1) Sl. 6(i) (payment codes 1023 / 1024) at 1% or 2%, and satisfy CARO 2020 reporting on long-cycle revenue recognition.
- **Logic:** Recognise revenue under Ind AS 115 over time using a cost-incurred input method or milestone output method; raise an RA bill for each period showing gross value of work done less previous cumulative bills less advance recovery less retention; trigger output GST on the RA bill date in GSTR-3B; treat advance receipts under Section 31(3) receipt voucher with GST in month of receipt and adjustment at next RA bill; bridge certified value, uncertified value, revenue recognised, RA bills raised and customer receipts in a monthly working showing unbilled revenue separately; deduct Section 393(1) Sl. 6(i) TDS at 1%/2% on RA bills and reconcile against Form 168.
- **Config:** EPC project master with contract value, RA bill schedule (8-15 bills with target dates), mobilisation advance percentage (typically 10-20%) and recovery curve (pro-rated or front-loaded), retention percentage (5-10%) and warranty release date, Ind AS 115 cost-incurred or milestone-output completion method per project, Section 13 CGST time-of-supply trigger on RA bill date, Section 31(3) receipt voucher for advances, Section 393(1) Sl. 6(i) codes 1023 / 1024 TDS map by contractor entity type, CARO 2020 long-cycle revenue disclosure roll-up.
- **Output:** A monthly EPC close where every RA bill ties to certified work value, mobilisation advance recovery, retention deduction, GST output and TDS deducted; the percentage-of-completion bridge ties certified value, uncertified value, cumulative revenue recognised, cumulative RA bills and customer receipts with unbilled revenue separately disclosed; advance receipts are linked to RA bills with GST adjusted; Section 393(1) Sl. 6(i) TDS deductions match Form 168; and CARO 2020 disclosures roll up cleanly.

### Modern Trade Channel Reconciliation for D2C Brands in India: DMart, Reliance Smart, More

Source: https://www.terra-insight.com/insights/modern-trade-channel-reconciliation-d2c-india/

- **Problem:** D2C brands entering Indian modern trade face a multi-layered commercial reconciliation problem — wholesale invoice at MRP minus trade margin per SKU per cluster, slab-based listing fees, slotting fees per shelf position, in-store promotion claims, volume rebates, and Section 393 TDS deductions, all settled through deductions against running payables on T+30 to T+90 cycles, where a 1 percent margin or claim drift across 200 stores compounds to lakhs of receivable leakage per quarter.
- **Logic:** Build a retailer-chain ledger per GSTIN with PO-to-invoice-to-payment-advice matching at SKU and store-cluster level. Decompose each deduction into trade margin, listing fee, slotting fee, promotion claim, return, volume rebate, and Section 393 TDS — book each to its own GL account. Enforce MRP-effective-date logic at SKU level so price changes flow correctly into wholesale price. Match promotion claims to the originating promo PO and in-store execution evidence before approving the deduction.
- **Config:** Modern trade retailer adapters with PO and payment-advice parsers, SKU master with MRP history and trade-margin schedule per retailer cluster, listing fee and slotting fee schedules per cluster, promotion PO ledger with execution evidence link, Section 393 TDS threshold tracking per buyer GSTIN, and a deduction-classification rule set.
- **Output:** A reconciled modern trade receivable ledger per retailer chain with SKU-level margin drift isolated, slotting and listing fee leakage quantified per cluster, promotion claim variance versus agreed PO surfaced per campaign, Section 393 TDS credit tracked in Form 26AS, and a board-ready net realisation view per SKU per chain.

### Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering

Source: https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india/

- **Problem:** Indian EPC and engineering contractors receive 10-20% mobilisation advance upfront against an advance bank guarantee, recover it through deduction on each RA bill (proportional or front-loaded), trigger GST liability on advance receipt under Section 13 of the CGST Act with a Section 31(3) receipt voucher (and the customer-side ITC claim that follows), maintain an advance ledger per contract showing running balance and cumulative GST adjustment, navigate the BG renewal cycle (annual or contract-end) with renewal cost, handle refunds on contract termination through Section 34 credit notes, and manage the early-stage cash position where advance plus retention together can leave net cash negative.
- **Logic:** On every advance receipt, issue a receipt voucher under Section 31(3) of the CGST Act in the same month, pay GST at 18% (composite works contract rate) in GSTR-3B; build an advance ledger per contract with original advance, cumulative recovery and balance outstanding; recover the advance on each RA bill per the agreed schedule (pro-rated or front-loaded); on every RA bill adjust the GST already paid on the corresponding advance portion to avoid double liability; track the advance bank guarantee expiry and renewal; on contract termination, freeze the advance ledger, issue a Section 34 credit note for the GST on unrecovered advance and coordinate refund with the customer; reconcile the early-stage net cash position layering advance, retention and BG cost.
- **Config:** EPC project master with mobilisation advance percentage, recovery curve (pro-rated or front-loaded), advance bank guarantee details (issuing bank, instrument number, validity, BG cost rate); Section 31(3) receipt voucher template; Section 13 CGST time-of-supply trigger on advance receipt; per-contract advance ledger with running balance; GST adjustment table linking advance receipts to RA bill recoveries; Section 34 credit note path for refunds; BG renewal calendar; early-stage cash bridge layering advance, retention and BG cost.
- **Output:** A monthly EPC close where every advance receipt has a Section 31(3) receipt voucher posted in the same month with 18% GST paid; the advance ledger per contract shows original advance, cumulative recovery and balance outstanding tying to the BG; each RA bill carries the correct advance recovery with the matching GST adjustment; advance BGs are tracked by expiry with renewal alerts; any contract termination is processed through Section 34 credit notes with BG refund coordinated; and the early-stage net cash position is visible across the contract portfolio.

### Modern Trade Settlement Variance Reconciliation for FMCG India

Source: https://www.terra-insight.com/insights/modern-trade-settlement-variance-fmcg-india/

- **Problem:** An Indian FMCG brand selling into modern trade has the same SKU flowing to seven national and regional chains — DMart on a 7-day settlement cycle, Reliance Smart / RRVL on 10 days, More on 14 days, Spencer's, Star Bazaar (Trent), Walmart Best Price and Metro Cash & Carry on their own cadences — and each chain generates a settlement file in its own format with its own GRN-vs-invoice tolerance, listing-fee debit treatment, BTL-marketing offset, QC-reject debit-note style and BOGO reimbursement mechanic. Receivables drift, the chain's deductions are absorbed without challenge, and a 3 to 5 percent net settlement variance against the gross invoice book — invisible at the GL level — compounds into 1.5 to 3 percent of annual revenue stuck inside seven sets of chain receivables.
- **Logic:** Build a per-chain settlement-file ingestion layer that normalises each chain's column structure into a canonical line-level register keyed by chain, invoice number, dispatch date, GRN date, SKU, quantity invoiced, quantity received, gross taxable value, listing-fee debit, slotting-fee debit, BTL-marketing offset, QC-reject debit, BOGO reimbursement, prompt-payment discount, TCS deduction, TDS deduction, net amount payable, payment date. Reconcile each settlement line against the supplier's tax invoice (Section 15 valuation), the supplier's GSTR-1 (outward), the chain's debit notes in supplier's GSTR-2B (Section 16 ITC eligibility), and the bank credit. Classify variances into within-tolerance write-off, above-tolerance debit (with chain-side reason code), valid scheme reimbursement, valid fee debit (ITC-claimable), invalid fee debit (challenge-back), and timing variance (cycle-end straddle). Age all unresolved variances 0-30 / 31-60 / 61-90 / 90+ days from settlement date.
- **Config:** Per-chain settlement file format definition (DMart, RSL, More, Spencer's, Trent Star Bazaar, Walmart Best Price, Metro CnC); chain master with payment cycle (7 / 10 / 14 days), prompt-payment discount rate, GRN-vs-invoice tolerance band per category; debit-note style mapping per chain (in-line vs separate file); Section 15(2) discount-treatment rule per scheme per chain JBP; Rule 46 invoice-template gate; GSTR-2B feed for chain debit notes; ageing buckets (0-30 / 31-60 / 61-90 / 90+) from settlement date; pre-22-September 2025 versus post-22-September 2025 rate switch on affected HSNs; Section 393(1) Sl. 18 (194H) TDS code mapping for chain commission flows.
- **Output:** A per-chain settlement reconciliation pack: line-level register of dispatch invoices versus received GRN versus chain settlement versus bank credit, with each variance line classified and aged; consolidated net settlement variance percentage per chain; recovery pipeline (above-tolerance debits, unverified QC rejects, listing-fee debits without GSTR-2B match, BTL offsets without business-purpose nexus); GST credit-note linkage to GSTR-1 amendment cycle; ITC posture on chain debit notes against GSTR-2B; CARO 2020 disclosure feed for material chain-receivable balances; and a monthly leakage report that surfaces the cash recovery opportunity to the FMCG CFO.

### Month-End Close Reconciliation Checklist for Indian Finance Teams

Source: https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india/

- **Problem:** Indian month-end close has four parallel reconciliation workstreams (bank, TDS, GST, platform settlements) with conflicting cut-offs: bank recon by day 3, GSTR-2B recon by the 15th (for GSTR-3B on the 20th), and platform settlements that straddle month boundaries with T+1 to T+3 lag.
- **Logic:** Sequence the close so bank recon clears by day 3, TDS receivable matches Form 26AS by TAN and section by day 7, GSTR-2B versus purchase register by day 15, and platform settlements disaggregated by UTR before sign-off. Route exceptions to an SLA-tracked queue so they do not carry into next month.
- **Config:** Calendar-driven workflow with deductor-level TDS mapping, GSTIN invoice-level matching, gateway-specific settlement parsers (Razorpay, PayU, Cashfree), and a suspense account SLA of 5 days.
- **Output:** Signed month-end close with separate bank, TDS, GST, and settlement reconciliation certificates, a materiality-classified exception register, and a sign-off audit trail ready for statutory review.

### More Retail FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/more-retail-fmcg-settlement-reconciliation/

- **Problem:** An FMCG brand owner sells a monthly bulk volume of biscuits, snacks or staples into More Retail's distribution centres; More issues a per-PO settlement file at T+14 carrying a GRN-tolerance debit on weight variance, a QC reject debit with photo evidence per case, a listing fee debit per SKU, a BTL marketing debit per scheme and a net settlement amount — and the supplier's AR controller has to reconcile every debit line against the primary-sales invoice ledger, the trade-promotion accrual register and the supplier's own QA records before posting the receivable as collected.
- **Logic:** Ingest the More settlement file at PO level on the T+14 cycle; reconcile GRN quantity against invoice quantity per line; recognise the GRN-tolerance debit as the excess-over-tolerance percentage on the affected cases; reconcile the QC reject debit against the supplier's QA photo-evidence file and convert accepted debits into Section 34 credit notes linked to the original invoice (GSTR-1 Table 9B); reconcile listing fee and BTL marketing debits against the trade-promotion accrual register; tie the net settlement amount to bank receipt; age unreconciled debits 0-15 / 16-30 / 31-60 / 61+ days from credit-advice date.
- **Config:** Per-PO GRN reconciliation rule with More's GRN-tolerance percentage on weight; QC reject evidence audit rule cross-referencing supplier QA photo log against More's per-case debit; More-specific settlement file ingestion mapping More columns to the internal debit-line taxonomy; Section 34 credit-note generation rule for accepted QC reject debits with linked-invoice flag; listing fee and BTL debit cross-reconciliation against trade-spend GL; ageing buckets 0-15 / 16-30 / 31-60 / 61+ days against credit-advice date; cross-account view aligning DMart 7-day, RSL 10-day and More 14-day cycles on the same primary-sales invoice ledger.
- **Output:** A per-PO More Retail settlement pack: invoice value, GRN quantity vs invoice quantity, GRN-tolerance debit with weight-variance ratio, QC reject debit with photo-evidence link, listing fee debit by SKU, BTL marketing debit by scheme, gross deduction sum, net settlement amount, credit-advice date, bank-receipt tie-out, Section 34 credit notes raised against accepted debits, ageing report on unreconciled lines, and a cross-account settlement-cycle view for the AR controller to compare More against DMart and Reliance Smart on the same SKU.

### Mother Dairy Cooperative Settlement Reconciliation for Milk Producers

Source: https://www.terra-insight.com/insights/mother-dairy-cooperative-settlement-reconciliation/

- **Problem:** An NCR-focused dairy procuring approximately 4.5 lakh litres of raw milk daily across 47 route sessions spanning Ghaziabad-Gurgaon-Sonipat-Meerut belt must reconcile route-level session accruals to a weekly union settlement invoice, apply the Delhi Government notified retail milk price cycle to downstream booth commission at Section 194H payment code 1015, close a quarterly cooperative bonus true-up tied to aggregate procurement and margin trigger, and remit Section 194C code 1002 TDS on tanker transporter contracts — all while the Delhi state-notified retail price may revise mid-week and mis-price the booth-commission accrual. Manual reconciliation across sub-ledgers, weekly invoices, quarterly bonus computations and TDS returns loses session counts to weather-cancelled routes, mis-carries re-tested fat/SNF at the chilling centre, and typically under-reports Section 43B(h) MSME payment ageing on the village-cooperative and transporter payable legs.
- **Logic:** Ingest the daily route-level session ledger from the dairy management system (route-code, session-timestamp, dock-location, litreage, fat percent, SNF percent, chilling-centre re-test flag). Aggregate to a per-union weekly settlement expected-payable using the union procurement price schedule. Match against the union settlement invoice on route-code, week-ending date, and volume; surface variances by session-count, re-test difference, and rate-boundary. Roll up quarterly to compute cooperative bonus per the union bye-law formula (aggregate procurement times quality-weighted bonus rate, gated on the margin trigger). Apply the Delhi Government notified retail price schedule to the booth-sales ledger; compute per-booth commission at the applicable percent-of-MRP; apply Section 194H code 1015 TDS at the prevailing rate (5 percent pre-1-October-2024, 2 percent from 1-October-2024); reconcile against Form 26AS at the booth operator's PAN. Flag payables aged past Section 43B(h) 45-day boundary against Udyam-registered village societies and transporters; flag transporter freight invoices for Section 194C code 1002 TDS reconciliation against the transporter PAN.
- **Config:** Route master with route-code, dock sequence, expected litreage band, and normal fat/SNF window; union master with union-code, procurement price schedule (band by fat/SNF), settlement frequency (typically weekly or ten-day), bonus formula and margin trigger; chilling centre re-test master with tolerance thresholds for fat and SNF drift; Delhi Government retail price schedule keyed by effective date and grade (toned/double-toned/standardised/full-cream); booth master with booth-code, franchisee PAN, Udyam status, and applicable commission percent; transporter master with transporter PAN, Udyam status, Section 194C payment code (1001 Ind/HUF or 1002 other), and TDS rate slab; Section 43B(h) MSME ageing alert threshold at day 30, 40 and 45 from invoice date; TDS return calendar for monthly deposit and quarterly filing (Form 26Q for domestic residents).
- **Output:** A month-end cooperative settlement pack: route-level session accrual reconciled to union settlement invoice by week, variance breakdown by session-count, fat/SNF re-test and rate-boundary; quarterly cooperative bonus computation with aggregate procurement, quality-weighted rate and margin-trigger status; booth-commission ledger tied to the Delhi retail price cycle with TDS accrual under Section 194H code 1015 and Form 26AS reconciliation at booth-operator PAN; transporter freight ledger with TDS accrual under Section 194C code 1001/1002 and Form 26AS reconciliation at transporter PAN; Section 43B(h) MSME ageing report highlighting payables past 30, 40 and 45 days against Udyam-registered village societies and transporters; audit-ready trail linking every rupee of union settlement, bonus true-up and booth commission back to the underlying route session.

### MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)

Source: https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker/

- **Problem:** Section 43B(h) disallows deduction for any MSME payable unpaid beyond 15 days (no written agreement) or 45 days (with agreement). A company with 150 MSME vendors and 450–1,200 invoices per month cannot track compliance reliably in spreadsheets, risking year-end disallowance on every breached invoice.
- **Logic:** Tag every vendor with MSME status and agreement type at invoice entry, calculate due date as acceptance date + 15 or 45 days, and age each invoice against that date. Match the NEFT/RTGS UTR bank debit back to the invoice to confirm payment date. Alert AP at 10 and 35 days outstanding to prevent breach and calculate year-end disallowance at invoice level.
- **Config:** Vendor master MSME flag plus agreement-type tag, invoice-level age bucket linked to 15/45-day rule, UTR-keyed bank match, and automated 10-day/35-day alerts.
- **Output:** Complete Section 43B(h) compliance trail, zero avoidable disallowance at year-end, evidence-backed dispute pack for MSME Samadhaan, and an AP workflow that protects deductibility every invoice cycle.

### MSME Credit Assessment Without Audited Financials: The Bank Statement Approach

Source: https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india/

- **Problem:** India's MSME credit gap — estimated at ₹65 trillion by SIDBI — is partly structural: most MSMEs cannot produce the audited financials that traditional underwriting requires, leading to rejection or under-lending that constrains business growth.
- **Logic:** Bank statement analysis produces a decisioning-grade financial view (synthetic P&L, balance sheet proxy, cash flow analysis) from the bank statement — a document that nearly every MSME has and that reflects actual business activity. The output is not auditor-certified, but it is documented, reproducible, and consented — meeting RBI Digital Lending Guideline requirements for underwriting data quality.
- **Config:** Analysis depth is configurable per product type: working capital loans prioritise operating cash flow and DSCR; term loans require the balance sheet proxy for net worth assessment; microloans can use a simplified income adequacy check. Minimum statement period: 3 months (minimum viable) to 12 months (recommended for seasonal businesses).
- **Output:** Credit file package: synthetic P&L, synthetic balance sheet (current items only), three-component cash flow, DSCR calculation, 40+ credit signals, and a risk classification summary. Output labelled as bank-data-derived, not auditor-certified, with methodology note for inclusion in the credit file.

### Constructing a Synthetic P&L for MSMEs from Bank Transaction Data

Source: https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india/

- **Problem:** Most MSME borrowers do not maintain P&L accounts, making income assessment for credit underwriting dependent on either costly CA estimates or inaccurate surrogate income proxies.
- **Logic:** Business inflows from the bank statement (after personal transaction exclusion) are classified by channel and counterparty type to approximate revenue. Recurring and identifiable outflows are mapped to operating cost categories — cost of goods, staff, overheads, tax obligations, debt service — to produce a structured income and expenditure view.
- **Config:** Revenue classification rules vary by industry segment (trading: high-frequency moderate-value inflows; services: lower-frequency higher-value inflows; manufacturing: bulk NEFT/RTGS from distributors). Cost classification can be configured to exclude or include owner withdrawals from the operating cost total.
- **Output:** Synthetic P&L showing estimated gross revenue, estimated operating costs by category, estimated EBITDA proxy, and debt service coverage ratio (DSCR) derived from actual EMI outflows vs business inflow.

### MSME Gold Loan Priority Sector Lending Classification for NBFCs

Source: https://www.terra-insight.com/insights/msme-gold-loan-priority-sector-lending-classification-nbfc-india/

- **Problem:** Gold loans to Udyam-registered micro and small enterprises can qualify as Priority Sector Lending, allowing the NBFC to sell the receivables to a scheduled commercial bank at a rate below wholesale funding cost or trade PSL flags through PSLCs. The classification requires Udyam validation, certified end-use, an LTV within the 75% RBI cap, and a defensible PSL-tagged loan book that reconciles to monthly RBI Form II reporting.
- **Logic:** Tag each loan at origination with the borrower's Udyam Registration Number, certified end-use category, enterprise size classification (micro/small/medium), pledged gold value, and LTV. Verify Udyam status against the Ministry of MSME portal at disbursement and re-verify at each renewal. Move accounts out of the PSL register when Udyam lapses, enterprise category upgrades, LTV breaches, or end-use changes to non-business use. Reconcile the PSL register to the general ledger, the loan management system, and the monthly Form II report.
- **Config:** PSL classification parameter set — Udyam category rules (micro/small/medium thresholds by investment and turnover), LTV cap (75%), eligible end-use categories, PSL sub-category mapping (PSL-Micro, PSL-Small, PSL-Agri-allied). Udyam portal verification integration. RBI Form II template mapped to the loan management system's PSL tag. Direct assignment master template and PSLC trading register.
- **Output:** Loan-account-level PSL register reconciled monthly to the general ledger and to RBI Form II, audit-ready end-use and Udyam evidence per account, timely exit of ineligible accounts, and a direct-assignment or PSLC-ready book that can be sold to a partner bank without a documentation gap.

### MSME Working Capital Assessment from Bank Statement Analysis

Source: https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement/

- **Problem:** Working capital loan sizing for MSMEs requires a view of the borrower's cash conversion cycle and peak cash deficit — information typically derived from audited accounts that most MSMEs do not maintain.
- **Logic:** Bank statement payment timing analysis maps average days between supplier payments and customer receipts. Peak cash deficit is identified as the maximum negative net cash position across the analysis period. Seasonal working capital needs are derived from month-over-month operating cash flow variance across a 12-month window.
- **Config:** Cash conversion cycle calculation window is configurable (6 or 12 months). Industry segment presets adjust expected cycle length thresholds (manufacturing: 60–90 days; trading: 15–45 days; services: 15–30 days). Peak deficit calculation excludes identified one-time financing inflows or outflows.
- **Output:** Estimated cash conversion cycle in days. Identified peak working capital requirement (₹ amount and calendar month). Month-over-month operating cash flow showing seasonal pattern. Recommended working capital facility size and drawdown structure.

### MSP-Linked Procurement Reconciliation for Indian Food Processing

Source: https://www.terra-insight.com/insights/msp-procurement-reconciliation-india/

- **Problem:** Food processors procuring under MSP must reconcile FCI / NAFED / state agency settlement cycles, direct farmer DBT payments under the PM-KISAN ecosystem and PSS, MSP gap subsidy where market price falls below MSP, the APMC mandi route vs e-NAM direct procurement vs cross-state movement, and Section 393(1) Sl. 6(i) codes 1023 / 1024 TDS on arhatiya commission — across multiple states with different procurement agency arrangements.
- **Logic:** Hold a farmer master with Aadhaar, IFSC, account number and land record; reconcile per-quintal payment against declared MSP for the rabi or kharif season; tie weighbridge slip and mandi gate-pass to the DBT bank credit confirmation; tag each transaction as mandi-arhatiya, e-NAM, or direct PSS; deduct Section 393(1) Sl. 6(i) codes 1023 / 1024 on arhatiya commission lines; map IGST treatment on inter-state movement of procured commodity to processor plant.
- **Config:** Procurement configuration with commodity master tagged to MSP-eligible status per season; farmer master with Aadhaar / land record / IFSC; arhatiya vendor master with PAN, Section 393(1) Sl. 6(i) flag and commission rate; mandi master with state cess regime; DBT confirmation ingestion against farmer payment register; cross-state movement flag for IGST handling on commodity transfer.
- **Output:** A monthly procurement close showing MSP-linked farmer payments DBT-confirmed per quintal against declared MSP, arhatiya commission deductions tied to Section 393(1) Sl. 6(i) challan, e-NAM settlement file reconciled to procurement ledger, MSP gap subsidy registrations tracked per farmer where applicable, and cross-state IGST on commodity movement reconciled against GSTR-2B.

### MT940 Bank Statement Format in India: How It Enables Automated Reconciliation

Source: https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india/

- **Problem:** CSV and PDF bank downloads lose narration structure to truncation and free-text columns, driving 30-50% more mismatches than structured SWIFT MT940. MT940 delivers UTR, value date, debit or credit indicator, and counterparty in fixed tags (:60F: opening, :61: transaction, :86: narration, :62F: closing) — but only if parsers correctly interpret the bank-specific :86: prefix.
- **Logic:** Parser consumes each MT940 file by tag, reading :61: for structured transaction fields and :86: for narration with bank-specific prefix handling (HDFC /INF/, ICICI /TXT/). UTR is extracted from :86: by pattern; amount and value date are taken directly from :61:. Intraday MT942 files are merged with the end-of-day MT940 without double-counting.
- **Config:** Bank-specific :86: prefix library, SFTP ingestion for HDFC CMS, ICICI CIB, Axis CMS, Kotak CMS, and SBI Corporate, and MT942 intraday merge rules.
- **Output:** Structured transaction ledger with zero narration-parsing fallback, faster reconciliation cycle from intraday feeds, audit-ready opening and closing balance proofs from :60F: and :62F:, and exception log for malformed tags.

### MT940 vs CAMT.053 vs MT942: Format Comparison for Indian Bank Statement Reconciliation

Source: https://www.terra-insight.com/insights/mt940-vs-camt-053-vs-mt942-india/

- **Problem:** Indian treasury teams running multi-bank reconciliation face a moving target: some banks deliver MT940 end-of-day, some offer MT942 intraday, and ISO 20022 CAMT.053 is rolling out unevenly across banks following the November 2025 CBPR+ cutover. A reconciliation parser built only for MT940 misses intraday visibility and is on borrowed time as banks migrate to CAMT.053. A parser built only for CAMT.053 cannot consume the MT940 files still being delivered by most domestic accounts.
- **Logic:** A format-aware ingestion layer accepts MT940, MT942, and CAMT.053 on the same SFTP or API drop, detects the format by file header or extension, and routes each file to the right parser. End-of-day statement of record is MT940 or CAMT.053. Intraday MT942 files are merged into a running position view but do not trigger reconciliation close. CAMT.053 structured remittance fields are mapped directly to match keys; MT940 :86: free text is parsed with narration-pattern regex per bank profile.
- **Config:** Format detection by header (CAMT XML namespace versus SWIFT block 1), per-bank format inventory (which banks deliver which formats and at which cadence), MT940 narration pattern library, CAMT.053 structured field mapping, MT942 intraday merge logic that excludes closing-balance computation.
- **Output:** Single canonical statement model populated from any of the three formats, with end-of-day closure on MT940 or CAMT.053 and intraday updates from MT942, ready for downstream auto-matching against the sub-ledger.

### Multi-ASN Single Invoice Consolidation: GST Compliance for Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/multi-asn-single-invoice-consolidation-auto-india/

- **Problem:** Auto-component suppliers dispatching 8-15 ASNs in a week to the same OEM plant cannot raise 14 separate tax invoices — OEM billing cycles, e-invoice IRN administration and GSTR-1 line counts all force consolidation. But Section 31 of the CGST Act fixes the latest legal moment for invoice issue, and the 7-day non-continuous-supply window is the binding constraint. Suppliers that consolidate beyond the window without documented continuous-supply contractual basis face Section 122 penalties and GSTR-3B mistiming, and break ASN-to-invoice linkage for downstream Section 34 credit-note treatment.
- **Logic:** Determine whether the contract legally constitutes continuous supply (rare for JIS) or non-continuous periodic supply (the norm). For non-continuous, set billing-window length within 7 days from first dispatch; issue one consolidated e-invoice (IRN) with document date equal to close of billing window, generated within 24 hours of that date. Maintain an ASN-to-invoice register linking each ASN reference to the consolidated invoice IRN. For Section 34 returned goods, raise credit notes against the consolidated invoice IRN, not the originating ASN. Match billing-cycle close to OEM billing cycle (Tata weekly, Maruti monthly under continuous-supply contract, Bosch fortnightly).
- **Config:** Per-OEM-plant billing-cycle master with cycle length, close-of-window day and continuous-supply contractual flag; ASN-to-invoice consolidation register keyed by consolidated invoice IRN; e-invoice generation routine with document-date locking to close-of-window date; Section 34 credit-note workflow with consolidated-invoice IRN reference; GSTR-1 line aggregation per consolidated invoice; OEM-side consolidation log for receivables reconciliation.
- **Output:** A per-OEM-plant periodic-invoicing pack with billing-window calendar, ASN-to-IRN consolidation register, Section 31 timing-of-supply audit trail, and reconciliation between supplier-issued consolidated invoices and OEM-side consolidation receipts. Downstream support for Section 34 credit-note linkage and GSTR-1 / GSTR-2B alignment at the OEM.

### Multi-Bank Cash Position Reconciliation for Indian Treasury Teams

Source: https://www.terra-insight.com/insights/multi-bank-cash-position-reconciliation-india/

- **Problem:** A treasury team running 8 to 12 banks pulls statements from a mix of MT940, MT942, CMS reports, NetBanking CSVs, and virtual account collection files. Without a unified cash position view, sweep failures go undetected, virtual account credits stay unallocated, and idle balances at PSU and cooperative banks earn savings-rate interest instead of being concentrated.
- **Logic:** Channel-aware ingestion routes MT942 intraday, MT940 end-of-day, CMS collection reports, and NetBanking CSVs to a single position table. Each account row carries opening balance, booked credits, booked debits, expected sweep movement, projected closing balance, and target balance variance. Virtual account credits are exploded against the CMS collection breakdown to the customer level. Sweep movements are confirmed by matching the debit at the operating account against the credit at the concentration account on the same value date.
- **Config:** Bank-by-bank ingestion calendar (MT942 hourly, MT940 end-of-day, CMS collection post-batch, NetBanking CSV fallback), target balance per account, sweep counterparty pairing, virtual account namespace per collection account, and idle balance threshold per account class.
- **Output:** Live multi-bank position table refreshed on the agreed cadence, sweep confirmation status per account, virtual account credit allocation to customer ledger, and a daily idle balance report ranked by recoverable yield.

### Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts

Source: https://www.terra-insight.com/insights/multi-bank-reconciliation-india/

- **Problem:** Mid-to-large Indian companies run 5–15 bank accounts (operating, NACH collection, salary, CC limits, escrow, export proceeds) and reconcile each independently. Inter-bank transfers and pool sweeps show as unmatched items on both sides, inflating exception queues and hiding the true consolidated cash position.
- **Logic:** Ingest all bank accounts through APIs or MT940 into a single ledger, then run cross-account matching on the UTR: a transfer appears as a debit in account A and credit in account B with the same UTR, so it self-matches. Sweep and pool transactions follow the same rule, scaling to 15–30 sweeps per day.
- **Config:** Bank API or MT940 connectors per bank, UTR-keyed inter-account matching rule, pool and sweep templates, and consolidated cash dashboard.
- **Output:** A unified multi-bank reconciliation with inter-account transfers auto-matched, cleaner exception queues, and a real-time consolidated cash position across the full account estate.

### Multi-Currency Reconciliation for Indian IT Services Companies

Source: https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india/

- **Problem:** Indian IT companies invoice in USD/EUR/GBP but receive INR after bank forex conversion, creating exchange rate variances between invoice date, receipt date, and booking date that must be classified under Ind AS 21.
- **Logic:** Match FIRC to invoice by remittance reference, calculate forex gain/loss as difference between invoice exchange rate and settlement exchange rate, reconcile against bank credit in INR.
- **Config:** Ind AS 21 for forex recognition, RBI FEMA regulations, FIRC as proof document, AD bank conversion rates, SOFTEX filing for STPI units, 9-month realization window.
- **Output:** Invoice-to-FIRC reconciliation, forex gain/loss register by currency pair, FEMA compliance report, and unrealized forex position for open invoices.

### Multi-Currency Revenue Recognition for IT Services under Ind AS 115

Source: https://www.terra-insight.com/insights/multi-currency-revenue-recognition-it-services-ind-as-115/

- **Problem:** Indian IT services firms running T&M, fixed-bid, and milestone contracts in USD, EUR, and GBP simultaneously face three distinct revenue recognition profiles under Ind AS 115, layered with Ind AS 21 forex revaluation, optional Ind AS 109 hedge accounting, and a FIRC realisation chain that often lags the revenue period.
- **Logic:** Classify each contract by performance obligation pattern (T&M hours-billed, fixed-bid cost-to-cost, milestone deliverable), translate at invoice-date spot rate under Ind AS 21, revalue receivables at closing rate, designate cash-flow hedges where derivatives are used, and reconcile revenue, billing, AR, and FIRC ledgers monthly.
- **Config:** Ind AS 115 five-step model, performance obligations over time, output and input measures of progress, Ind AS 21 spot rate at transaction date, closing rate at reporting date, Ind AS 109 hedge accounting designation and effectiveness testing, FIRC realisation against invoice.
- **Output:** Revenue recognition schedule per contract, unbilled receivable and deferred revenue ledgers, forex gain or loss split between realised and unrealised, OCI hedge reserve roll-forward, and a four-ledger month-end reconciliation.

### Multi-Hop Job Work in Auto Components: Challan Tracking Across 3-4 Vendors Without Section 143 Default

Source: https://www.terra-insight.com/insights/multi-hop-job-work-challan-tracking-auto-india/

- **Problem:** Auto-component job-work chains rarely sit at a single vendor — a forging routes through forge to CNC to heat-treat to zinc-nickel plate to return-leg, typically three to four hops, each with its own Rule 55 inter-job-worker challan and its own ITC-04 Table 5C disclosure; the Section 143 one-year input clock and three-year capital-goods clock run from the original principal-dispatch date and do NOT restart at any hop, so a forging that has spent eight months across three job-workers has only four months of window remaining regardless of how recently it arrived at the current vendor; a Tier-1 with disciplined single-hop tracking but no multi-hop visibility carries the entire Table 5C surface as an audit-time blind spot; on a typical engine-block cohort of 2,400 castings dispatched annually to a 3-hop chain even a 2% inter-hop documentation gap can crystallise ₹8-12 lakh of deemed-supply liability at Section 65 audit.
- **Logic:** Stamp every Rule 55 principal-dispatch challan with original-dispatch date, statutory clock (1 year inputs, 3 years capital), part programme code and job-worker GSTIN; for every inter-job-worker movement issue a Rule 55 inter-vendor challan that references the original-dispatch challan number as the linked reference and is keyed to ITC-04 Table 5C; track the single original clock across all hops without resetting; surface the days-to-deemed-supply countdown per part-cohort per current-vendor; alert 60 and 30 days before the original clock expires regardless of how many hops the goods have travelled; reconcile the principal's Rule 55 register to the ITC-04 Table 5C disclosure to the receiving job-workers' inward records at every quarter-end.
- **Config:** Job-worker master with GSTIN, PAN, process type (forge, machine, heat-treat, plate, paint, assembly), registration status; Rule 55 challan series per principal plant per movement type (principal-to-JW, JW-to-JW, JW-to-principal); part-programme master with intended routing graph (forge → machine → heat-treat → plate → principal); original-dispatch clock policy (1 year inputs, 3 years capital goods, no clock for jigs/fixtures/moulds/dies); Table 5C inter-vendor challan template with linked reference field; quarterly ITC-04 build with Tables 4, 5A, 5B and 5C reconciled to register.
- **Output:** An open-balance position per original-dispatch challan tracked through every hop with current-vendor, days-since-original-dispatch and days-to-deemed-supply countdown; the Table 5C inter-vendor challan register tying each hop to the original dispatch; the ITC-04 pre-filing pack with the original-dispatch clock intact and a Table 5C trail that matches the principal's Rule 55 register; the multi-hop deemed-supply provisional accrual at the 30-day band; and a board-visible Section 143 multi-hop dashboard.

### Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work

Source: https://www.terra-insight.com/insights/multi-statement-upload-reconciliation/

- **Problem:** Lenders receiving multiple overlapping bank statement PDFs for the same account cannot simply process each one independently. Doing so inflates income totals, double-counts EMI obligations, and produces unreliable FOIR calculations — because the same transactions appear more than once across the uploaded files.
- **Logic:** Parse each uploaded PDF independently to extract its transaction table. Assess sort order for each statement and flip reverse-chronological files to ascending order. Merge all transaction tables into a single list. Deduplicate by matching on the combination of transaction date, amount (debit or credit), and closing balance — treating rows that match all three as the same transaction regardless of narration truncation differences. Sort the merged list chronologically and verify the balance chain end to end.
- **Config:** Upload all statement PDFs for the same account in a single batch. The system automatically identifies the account holder from statement headers and rejects PDFs from different accounts in the same batch. No manual period specification is required — the system infers the date range from the extracted transactions.
- **Output:** Single merged transaction list in chronological order, deduplicated, with balance chain verified. Used as the input for all downstream analysis: income classification, FOIR calculation, NACH EMI tracking, and fraud signal generation. Duplicate count and sort-order correction status are reported in the processing summary.

### Multi-Hop Job-Work Reconciliation for Textile Manufacturing in India

Source: https://www.terra-insight.com/insights/multi-hop-job-work-reconciliation-textile-india/

- **Problem:** A Tiruppur or Karur knitwear exporter running a 5-hop job-work chain from yarn to finished garment must reconcile at least six Rule 55 delivery challans, four job-workers' return-inward registers, one ITC-04 quarterly filing, and the Section 143 CGST 1-year clock — all keyed to the original yarn dispatch date — for every export order. A stuck hop (a slow dyer, a bottlenecked stitching unit, a rejected batch that lingers at the last-hop QC) that pushes the return-inward past the 1-year mark retro-triggers deemed-supply GST on the entire original yarn value, plus interest from the dispatch date. Manual challan tracking across five hops loses documents, mis-chains hop-to-hop movements to the wrong dispatch, and typically over-reports closing balance on ITC-04 — leaving the principal exposed to Section 73/74 GST notices at year-end audit.
- **Logic:** Build a job-work dispatch register keyed by original principal-to-hop-1 challan reference; expand each dispatch into a chain of expected inter-hop movements based on the standard hop sequence for the SKU (yarn to weaver to dyer to cutting to stitching to QC and packing). Ingest each Rule 55 delivery challan pair (outbound and return-inward) at every hop and match by challan reference, quantity, and HSN back to the parent dispatch. Track the days-elapsed clock against Section 143 — flag any dispatch approaching 300 days without closure. Feed the ITC-04 filing cycle from the register: dispatches in the period, returns in the period, direct supplies from job-worker premises in the period, and closing balance still with job workers at period-end. Cross-foot the closing balance to the physical stock take at every hop before the ITC-04 filing deadline.
- **Config:** Job-worker master with GSTIN, PAN, TDS payment code (1023 for principal-supplied material, standard textile chain), and TDS rate slab (1 percent Individual/HUF, 2 percent other); SKU-to-hop-sequence master defining the standard conversion chain per garment category (knitwear versus woven; export versus domestic); challan register with sender GSTIN, receiver GSTIN, HSN, quantity, declared taxable value, and challan pair reference; the Section 143 1-year clock configuration with alert thresholds at 270, 300, and 330 days from original dispatch; ITC-04 filing frequency setting (half-yearly for principals above ₹5 crore aggregate turnover; annually below); RoDTEP scheme flag per SKU (Appendix 4R for DTA exports; Appendix 4RE for Advance Authorisation, EOU, or SEZ exports); e-BRC reconciliation feed from the banker for export realisation.
- **Output:** A month-end multi-hop reconciliation pack: opening balance of goods with each job worker by hop, period dispatches (with challan references), period returns (with challan references), period direct-from-hop supplies (typical for export shipments), period rejections, and closing balance by job worker by SKU. Per-dispatch ageing against the Section 143 1-year clock highlights dispatches at risk of deemed-supply trigger. Job-worker TDS payment code 1023 tally feeds the TDS return cycle and cross-checks Form 26AS at deductee-job-worker PAN level. ITC-04 filing draft populates in the correct three-part format (dispatches, returns, direct supplies) with the closing balance reconciled to physical stock take at every hop.

### Myntra, Ajio, Flipkart Fashion Apparel Settlement Reconciliation

Source: https://www.terra-insight.com/insights/myntra-ajio-flipkart-fashion-apparel-settlement-reconciliation/

- **Problem:** A branded apparel principal selling across Myntra, Ajio, and Flipkart Fashion faces three settlement files with three different commission grids (15-20% Myntra, 12-18% Ajio, 12-16% Flipkart Fashion), three payout cadences (T+15, T+7 to T+10, T+7), three return-handling models (dedicated bucket, integrated netting, separate adjustment schedule), and one Section 52 TCS aggregation at 0.5% into GSTR-8. The brand's own books must reflect a Section 9(1) normal supply (not 9(5) deemed supply — apparel is not notified), issue a Section 34 credit note for every return before the 30 November following FY cut-off, deduct 5% TDS under Section 194H on platform commission (payment code 1015), and claim 194-O credit at 1% deducted by the platform (payment code 1058). Manual per-platform reconciliation loses commission-invoice matches, mis-applies TCS to the wrong month, and mis-classes late returns — resulting in output GST over-payment, ITC leakage, and Section 73/74 notice exposure.
- **Logic:** Ingest each platform's settlement file at native cadence (Myntra T+15, Ajio T+7 to T+10, Flipkart Fashion T+7) and decompose every row into six components — gross taxable, platform commission (Section 194H TDS at 5%), logistics or shipping charge, returns adjustment, Section 194-O TDS (1%) at source, and Section 52 TCS (0.5%) at source. Match every gross taxable entry to the brand's own sales register by order ID; match every commission line to the platform's tax invoice and the brand's TDS working; match every returns adjustment to a Section 34 credit note issued by the brand within the 30 November cut-off. Aggregate all three platforms' Section 52 TCS into a single quarterly ledger and reconcile against GSTR-2A after the platform files GSTR-8. Trace net-cash-in from each platform to the specific bank credit line in the brand's statement.
- **Config:** Platform master with settlement cadence (T+15 Myntra, T+7 to T+10 Ajio, T+7 Flipkart Fashion), commission grid ranges by SKU category, returns-handling model (bucket, integrated, or separate), and Section 194-O deducting-agent PAN; SKU-to-category master mapping brand SKUs to platform commission tiers; Section 52 TCS rate (0.5% per Notification 15/2024-CT); Section 34 credit-note deadline enforcement (30 November of following FY); Section 194H TDS payment code 1015 (5%) for commission bill deductions; Section 194-O TDS payment code 1058 (1%) reconciliation for platform-side deductions; GSTR-8 reconciliation window (platform files by 10th of following month; GSTR-2A visibility follows); bank statement narration patterns for identifying Myntra, Ajio, and Flipkart Fashion settlement credits.
- **Output:** A per-quarter three-platform reconciliation pack: platform-wise gross taxable, commission (with 194H TDS reconciled to Form 26AS at platform PAN), logistics, returns (with Section 34 credit-note tally against the 30 November cut-off), 194-O credit at the brand's PAN, Section 52 TCS aggregate against GSTR-2A, and net cash-in traced to the brand's bank statement. Per-order match rate across settlement file and internal sales register. GSTR-8 to GSTR-2A synchronisation health check. Alert list of returns booked by any platform after 30 November of the following FY that cannot recover output GST. Commission-invoice ITC claim reconciled to the platform's GSTR-1 filing at the platform's GSTIN.

### NACH Bounce Recovery and Section 43B(h) MSME Compliance for Indian Finance Teams

Source: https://www.terra-insight.com/insights/nach-bounce-recovery-43b-h-msme-india/

- **Problem:** Indian finance teams that process NACH collections at scale and buy from a long tail of Udyam-registered MSE suppliers carry two leakage exposures that rarely show up on a single dashboard. NACH bounce charges aggregate quietly on the bank statement and erode the working-capital line. Section 43B(h) ageing on MSE supplier payables converts to a hard FY-end income-tax disallowance. Both are invisible without a structured per-code and per-supplier register. Both are recoverable with a defined operating cadence. Neither gets the audit-committee attention it deserves because the data sits in fragmented systems.
- **Logic:** Decompose NACH bounce volume by return code with retry economics per code (probability of recovery and cost of retry against the leakage rupee). Run mandate hygiene as a monthly cycle to keep the active-mandate base aligned with the sponsor bank. Operate a monthly bounce dashboard with code-category cuts and a recovery-rate trend. For 43B(h), maintain a MSE-registered supplier subset with payable ageing, compute exposure at each month-end, escalate at the 30-day and 40-day pre-window warning, and produce a quarterly exposure pack with a hard quarter-four pre-FY-end cut. Combine both into the audit-committee leakage agenda.
- **Config:** NACH return-code dictionary with per-code recovery probability and cost-of-retry assumption. Mandate-master reconciliation against sponsor-bank active list, monthly. Bounce-code dashboard schema: total presented value, bounce rate by category, charge-line trend, top-counterparty bounce frequency. MSE-registered supplier flag in the supplier master driven from Udyam number capture. Payable ageing with statutory or contractual window per supplier. 43B(h) exposure summary with disallowance forecast at the marginal corporate rate. Monthly bounce review cadence and quarterly 43B(h) exposure-pack cadence.
- **Output:** A monthly NACH bounce dashboard with code-category recovery and charge-line trend. A weekly mandate-revival operating queue for codes 21 and 24. A quarterly Section 43B(h) MSE exposure pack with payable ageing, exposure summary, payment-acceleration recommendation, and residual disallowance forecast. A consolidated audit-committee leakage view that ties the NACH charge-line and 43B(h) exposure into the broader Seven Classes recovery program.

### NACH Credit Payout Reconciliation: Payroll and Vendor Settlement at Scale

Source: https://www.terra-insight.com/insights/nach-credit-payouts-payroll-vendor-india/

- **Problem:** A corporate paying ₹38 crore monthly payroll for 4,200 employees via NACH-Credit reconciles against the gross bank debit only. Failed credits are surfaced days later when employees raise tickets, statutory return-file exceptions go untracked, and vendor NACH-Credit failures push payments outside the Section 43B(h) MSME window.
- **Logic:** Join the credit instruction file (per-beneficiary), the bank debit advice (gross), and the NACH return file (per-beneficiary failure with reason code) on the batch ID and the beneficiary key. The settled value equals gross debit minus return value. Each return-file row triggers a repost workflow via NEFT or RTGS with same-day SLA.
- **Config:** Batch ID and beneficiary master, NACH return-code library for credit-side returns, gross-debit minus return-value reconciliation rule, repost-via-NEFT workflow, exception MIS to payroll and accounts payable, and a 43B(h) and TDS-deposit timing rule.
- **Output:** Same-day visibility of failed credits, employee and vendor tickets prevented because the corporate acted first, statutory payment timing preserved, and a defensible audit trail showing every credit either landed or was reposted.

### NACH EMI Reconciliation for NBFCs: Daily MIS, Return Codes, Penalty Recovery

Source: https://www.terra-insight.com/insights/nach-emi-reconciliation-nbfc-india/

- **Problem:** An NBFC with 38,000 monthly EMI NACH mandates that reconciles weekly understates DPD by five to seven days per failed mandate, loses up to a third of bounce-charge recovery because the LMS bills late, and remits the partner bank's co-lending share days behind the contractual SLA.
- **Logic:** Disaggregate every NACH batch credit into mandate-level outcomes keyed on UMRN, post success or failure with the NPCI return code to the LMS the same business day, classify each return code into retriable, non-retriable, or dispute, and emit a separate bounce-charge billing event for each retriable failure.
- **Config:** UMRN-to-loan-account master, NPCI return-code library (codes 01 through 99) classified by action, same-day LMS posting SLA, two-retry cap per cycle, bounce-charge billing rule respecting the RBI October 2023 fair-lending limits, and a co-lending partner remittance rule.
- **Output:** A daily collections MIS with bouncing-borrower segmentation, accurate DPD and NPA classification under IRAC norms, recovered bounce charges billed within one cycle, and contractually compliant co-lending remittance to partner banks.

### NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations

Source: https://www.terra-insight.com/insights/nach-mandate-management-reconciliation/

- **Problem:** An internal mandate register drifts 5–10% from NPCI reality over a year as borrowers cancel mandates directly with their banks, amend accounts, or let mandates expire. Presenting cancelled mandates (code 25) or expired mandates generates avoidable returns and understates effective collection rates.
- **Logic:** Reconcile the internal mandate register to NPCI at least weekly using UMRN as the primary key. Flag mandates showing Cancelled or Inactive at NPCI while still Active internally, and block them from the next batch. For at-risk mandates (prior code 01 or code 27), run daily pre-batch status checks.
- **Config:** Weekly UMRN reconciliation against NPCI, pre-batch cancellation check 48 hours before submission, mandate amendment workflow (cancel-and-reregister with 5–7 day NPCI processing buffer), and at-risk watch list.
- **Output:** A clean mandate register, fewer code 25 and code 20 returns, higher batch success rate, and a regulator-ready mandate audit log.

### NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates

Source: https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation/

- **Problem:** NBFCs with 10,000+ active NACH mandates that reconcile batches weekly understate DPD by 5–7 days per failed EMI, delaying NPA classification by 15–21 days across three cycles. Under RBI IRACP norms, DPD must start from contractual due date, not batch processing date.
- **Logic:** Disaggregate each NACH batch credit into mandate-level outcomes keyed on UMRN, post success or failure (with return code) to the LMS same-day, and anchor DPD counting on the contractual due date. For partial settlements, post the actual amount and continue DPD on the unpaid balance.
- **Config:** Mandate-level batch disaggregation, UMRN-to-loan-account master, same-day LMS posting SLA, partial-settlement handling, and return code classification (retriable vs non-retriable).
- **Output:** Accurate DPD counters, correct NPA classification and IRACP provisioning, RBI-reportable PAR figures (NBS-7, NBS-9), and a defensible collections audit trail per mandate.

### NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams

Source: https://www.terra-insight.com/insights/nach-return-codes-india/

- **Problem:** NACH returns arrive T+1 or T+2 with a 2-digit NPCI reason code that determines whether the debit can be retried (code 01 Insufficient Funds), whether the mandate is still valid (code 20 Account Closed, code 25 Mandate Cancelled), or whether a dispute is active (code 27 Stop Payment). Processing every return identically causes retry of non-retriable mandates and delays DPD reporting.
- **Logic:** Parse the NPCI return file by UMRN, map the return code to a retriable vs non-retriable classification, and route each code to its resolution workflow (retry, mandate re-registration, collections contact, dispute). Stop DPD counting from the original presentation date, not the retry date, for accurate NBFC risk reporting.
- **Config:** NPCI return code library, retriable vs non-retriable mapping, UMRN keyed matching to the LMS, retry SLA (3–5 business days, max 2 attempts), and DPD anchor rules.
- **Output:** Every return code routed to the right workflow same-day, accurate DPD figures in the LMS, reduced false retries, and a regulator-ready collections audit trail.

### NBFC Borrower Tier Classification under RBI Scale-Based Regulation (SBR)

Source: https://www.terra-insight.com/insights/nbfc-borrower-tier-classification-rbi-sbr-india/

- **Problem:** RBI Scale-Based Regulation places every NBFC in one of four layers — Base, Middle, Upper, Top — based on size, activity, and systemic interconnectedness. Each layer applies a different capital, governance, and disclosure regime. Asset classification turns NPA at 90 DPD across all layers. Borrower-level tagging discipline is the single source of truth that drives capital, exposure, classification, and disclosure simultaneously.
- **Logic:** Tag every loan account at the borrower level with category, product, sanction, tenor, outstanding, DPD, classification stage, provisioning, and connected-party flag. Refresh tagging on every disbursement, prepayment, restructuring, and at day-end. Compute NPA at 90 DPD overdue. Aggregate borrower exposures across products to enforce single-counterparty and group caps. Produce layer-specific reports — capital adequacy, large exposures, concentration, related-party — from this tagged dataset.
- **Config:** SBR layer parameter for the entity (Base, Middle, Upper, Top) driving threshold rules. Borrower master with category, sanction limit, and group code. DPD classification matrix mapped to provisioning percentage. Connected-party register feeding the related-party report.
- **Output:** Daily DPD classification flow into asset-classification register, layer-specific quarterly returns (concentration, large exposure, capital adequacy), audit-ready borrower-level tag history, and synchronised provisioning movements.

### NBFC Collection Reconciliation under RBI Co-Lending Guidelines for Indian Lenders

Source: https://www.terra-insight.com/insights/nbfc-collection-reconciliation-co-lending-india/

- **Problem:** Co-lent loans under the RBI Co-Lending Model carry an 80:20 economic share between a bank and an NBFC. Every collection must split correctly between the partners by category — principal, interest, penal interest, bounce charge, GST on penal interest — and the resulting DPD bucket must flow through to both books on the same day to keep NPA classification synchronised.
- **Logic:** Tag each collection event by loan account, instalment, and category. Compute the 80:20 split on principal and interest, the 100:0 split on penal interest where servicing income is retained by the NBFC, and the agreed share on bounce charges plus GST. Sweep the bank's share to its nostro within the master-agreement cut-off. Transmit DPD bucket movements to the bank in the daily partner file so asset classification is synchronised.
- **Config:** Co-lending master agreement parameter set — share percentages by category, escrow cut-off windows, servicing fee formula. Loan-account-level DPD register feeding both NBFC and partner-bank classification engines. Partner-bank acknowledgement file format for settlement-day reconciliation.
- **Output:** Daily 80:20 settlement file accepted by the partner bank, synchronised NPA classification on the same DPD trigger, audit-ready category-wise split log, and clean quarter-end portfolio reconciliation against the bank's ledger.

### NBFC Expected Credit Loss (ECL) Reconciliation under Ind AS 109 and RBI Master Direction

Source: https://www.terra-insight.com/insights/nbfc-ecl-expected-credit-loss-reconciliation-india/

- **Problem:** Ind AS 109 ECL on the NBFC book runs a three-stage model — performing, significantly deteriorated, credit-impaired — with PD, LGD, EAD inputs per stage. RBI requires the Ind AS ECL to be no lower than IRACP provisioning, with the shortfall held in a non-distributable Impairment Reserve. Monthly reconciliation across the model, the staging, and the overlay is what makes the ECL number audit-defensible and regulator-defensible.
- **Logic:** Refresh DPD and stage assignment per account at each reporting date. Apply the documented significant-increase-in-credit-risk trigger to move accounts between Stage 1 and Stage 2. Re-compute PD, LGD, EAD using current book and macroeconomic data, and discount at original EIR. Compare aggregate ECL to IRACP minimum; if ECL is lower, appropriate the shortfall to Impairment Reserve. Produce the stage migration matrix and the month-on-month ECL walk.
- **Config:** Significant-increase-in-credit-risk policy parameter set — 30 DPD rebuttable trigger, PD movement thresholds, watchlist and restructured flags. PD, LGD, EAD model library calibrated by product and segment. IRACP comparison engine producing per-account minimum. Impairment Reserve register tied to retained earnings appropriation.
- **Output:** Monthly stage migration matrix, ECL allowance computation with PD/LGD/EAD walk, RBI minimum overlay comparison, Impairment Reserve movement journal, and audit-ready evidence chain for the stage-assignment policy, model governance, and reconciliation discipline.

### NBFC Corporate Tax under Section 115BA (Income Tax Act 2025): Concessional Regime and Trade-Offs

Source: https://www.terra-insight.com/insights/nbfc-corporate-tax-section-115ba-india/

- **Problem:** The Income Tax Act 2025 carries forward the concessional corporate tax regime as Section 115BA. NBFCs face a structural decision: opt in at a 22% headline rate (effective 25.17% with surcharge and cess) and lose MAT credit, additional depreciation, and most Section 80 deductions, or stay in the regular regime at 30% but retain those benefits. The decision is irrevocable and must be made against a multi-year forecast that includes credit-cycle scenarios.
- **Logic:** Model taxable profit under both regimes for the next three to five years. Value unutilised MAT credit at present value of expected utilisation. Stress-test under credit-cycle scenarios where Stage 2 and Stage 3 ECL movements depress taxable profit and trigger MAT under the regular regime. Inventory deductions the regime forgoes — Section 80IA, 80IB, additional depreciation, SEZ — and quantify the foregone benefit. Compute net present value differential between regimes.
- **Config:** Tax-regime parameter at the entity level driving downstream computation. Brought-forward loss pool tagged by source (regular business loss, deduction-attributable loss). MAT credit register with vintage and utilisation timeline. Deduction inventory by Section reference.
- **Output:** Regime-choice decision pack with NPV differential, scenario analysis under credit-cycle stress, MAT credit value foregone, and irrevocable opt-in declaration record. Subsequent annual tax computation aligned to the elected regime with audit-traceable adjustments.

### FLDG (First Loss Default Guarantee) Accounting and Reconciliation for Indian NBFC-Fintech Partnerships

Source: https://www.terra-insight.com/insights/nbfc-fldg-first-loss-default-guarantee-recon-india/

- **Problem:** RBI's June 2023 guidelines cap FLDG cover at 5% of the loan portfolio and require documented contractual structure. NBFCs running multiple LSP partnerships must reconcile, every month, per-partnership FLDG corpus, invocations linked to write-offs, replenishments, and recoveries net of partnership tagging — and prove the 5% cap is respected on the live portfolio.
- **Logic:** Tag every loan account to its originating LSP partnership at disbursement. Compute monthly partnership-level loss as write-off plus NPA provisioning movement minus recovery. Invoke the FLDG corpus up to the contractual threshold and recognise the offset in the NBFC's profit and loss account. Track replenishment within the contracted timeline and recompute corpus as a percentage of live portfolio outstanding to monitor the 5% cap.
- **Config:** LSP partnership master with FLDG percentage, form of holding (cash, BG, FD), invocation and replenishment timelines, and recovery netting rules. Partnership tag on every loan account driving collection routing. Monthly write-off register tied to partnership for invocation source-of-truth.
- **Output:** Monthly per-partnership FLDG reconciliation tying invocations to write-offs, replenishments to bank evidence, recoveries to source accounts; closing corpus position and 5% cap compliance check; audit-ready evidence chain for both NBFC and LSP auditors.

### NBFC Securitisation and Pass-Through Certificate Reconciliation under RBI Master Direction 2021

Source: https://www.terra-insight.com/insights/nbfc-securitisation-pass-through-reconciliation-india/

- **Problem:** An NBFC securitisation under the RBI September 2021 Master Direction transfers a pool of standard assets to an SPV and issues PTCs to investors. The originator stays as servicer and must, every month, reconcile pool collections against the contractual cash-flow waterfall, prove True-Sale and Minimum Retention Requirement compliance, and deliver an audit and rating-agency evidence pack — all without breaking the senior-tranche payout window.
- **Logic:** Capture pool-level collections daily and aggregate at month-end. Apply the cash-flow waterfall in trust-deed order — senior expenses, senior interest, senior principal, mezzanine, credit-enhancement replenishment, originator excess spread. Compute and verify MRR retention. Generate the trustee, investor, and rating-agency reports from the same data lineage.
- **Config:** SPV trust-deed parameter set — tranche definitions, waterfall order, credit-enhancement structure, MRR percentage, payout date. Pool master with seasoning, original tenor, and asset class. Trustee account mapping for remittance reconciliation.
- **Output:** Monthly trustee remittance file accepted on the payout date, waterfall sign-off pack, MRR retention proof, True-Sale confirmation log, and audit-ready evidence chain for statutory auditors and rating agencies.

### Nestle India Dairy Whitener Supply Chain Reconciliation

Source: https://www.terra-insight.com/insights/nestle-india-dairy-whitener-supply-chain-reconciliation/

- **Problem:** A large Indian dairy processor running a Punjab dairy whitener plant with approximately 11 lakh litres of daily raw milk inflow — split 60 percent direct-farmer procurement across thousands of Bulk Milk Chillers and 40 percent cooperative-federation supply — must reconcile per-farmer 24-hour settlement runs, plant-level GRNs in SAP MM, vendor invoices from cooperative federations, Section 194Q code 1031 TDS aggregation at PAN level, Section 143 CGST job-work movements to a co-packer network, and Rule 89(5) inverted-duty refund claims driven by 5 percent output GST on HSN 0402 against 18 percent input GST on HSN 3923 packaging. Manual reconciliation across the fat/SNF-graded settlement register, the MIGO/MIRO postings in SAP MM, the co-packer challan chain, and the Form GST RFD-01 refund file loses PAN-level aggregation, over-states the closing balance at co-packers on ITC-04, and leaves the processor exposed to a Section 143(3) deemed-supply trigger on a stuck co-packer batch and a Section 73/74 GST notice on a mis-computed inverted-duty refund.
- **Logic:** Build a per-day, per-plant, per-source reconciliation register keyed by three axes — the BMC/route settlement, the SAP MM GRN, and the vendor invoice — with the fat/SNF profile carried as an attribute at every stage. Aggregate purchase value at supplier PAN level and cross the Section 194Q ₹50 lakh threshold flag transparently for cooperative federations and packaging vendors, with the payment code 1031 deduction switched on the moment the threshold is crossed. Track every plant-to-co-packer Rule 55 delivery challan pair (outbound and return-inward) and run the Section 143 1-year clock against the original dispatch; alert the operations team at 270, 300, and 330 days. Compute Rule 89(5) inverted-duty refund on a rolling monthly basis with the amended-formula Net ITC excluding input services and capital goods per Notification 14/2022-CT. Feed the ITC-04 half-yearly filing from the challan register and cross-foot against the co-packer physical stock take at period-end.
- **Config:** Vendor master with GSTIN, PAN, section-390-TDS-eligibility flag (agriculturist under Section 40 Sl. 1(f) exempt versus cooperative federation and packaging vendor above ₹50 lakh threshold under Section 393 Sl. 8 code 1031); BMC/route master with the fat/SNF grid effective date and per-litre rate; SAP MM integration to pull MIGO/MIRO daily; co-packer master with GSTIN, TDS payment code 1023 (principal-supplied material) and rate slab (1 percent Ind/HUF or 2 percent other resident); Section 143 CGST 1-year clock configuration with alert thresholds at 270/300/330 days; ITC-04 filing frequency setting (half-yearly for above ₹5 crore aggregate turnover); Rule 89(5) refund cycle configuration with the amended-formula Net ITC exclusion for input services and capital goods (Notification 14/2022-CT); GST rate table for HSN 0402 output (5 percent) and HSN 3923 packaging input (18 percent); NEFT/RTGS/IMPS payment-file reconciliation feed from the bank.
- **Output:** A day-end and month-end reconciliation pack: (a) BMC-level fat/SNF settlement register reconciled to plant-lab re-test, with adjustment queue; (b) per-farmer PAN aggregate against the Section 194Q ₹50 lakh threshold with code 1031 deduction flag; (c) SAP MM MIGO/MIRO posting cross-tied to vendor invoice with variance queue; (d) per-day plant-to-co-packer Rule 55 challan register with Section 143 clock ageing; (e) Rule 89(5) inverted-duty refund draft under the amended formula with Statement-1A supporting; (f) ITC-04 half-yearly draft with three-column split (dispatches, returns, direct-supply-from-co-packer) and closing balance reconciled to co-packer physical stock take; (g) NEFT/RTGS return-file reconciliation with rejected-leg exception queue for the 24-hour re-route commitment.

### Net Banking MDR: Flat Fee vs Percentage for Indian Merchants

Source: https://www.terra-insight.com/insights/net-banking-mdr-flat-fee-vs-percentage-india/

- **Problem:** Indian finance teams accept the gateway's default net banking structure — flat ₹7-20 per transaction or 1.8% to 2% percentage — without computing the break-even ticket size against the merchant's own transaction distribution. A high-ticket utility, B2B, or travel merchant on a flat fee structure pays multiples of what percentage would cost on the same volume, and a low-ticket D2C or food merchant on a percentage structure pays multiples of what flat would cost. The structural choice is treated as a gateway default rather than a negotiation variable, and the leakage compounds month after month under a line item that finance teams glance past as 'net banking, ₹X lakh'.
- **Logic:** Reconciliation computes the break-even ticket size between the flat fee F and the percentage P as F divided by P (for example, ₹12 divided by 1.8% equals ₹666.67), and segments the merchant's net banking transaction distribution into below-break-even and above-break-even buckets. Where the dominant bucket is above break-even (high-ticket cohorts), the expected-rate table favours percentage; where the dominant bucket is below break-even, the table favours flat. The engine then computes the actual deduction per transaction against the contracted structure and flags variances, separating contracted-structure deviation (gateway billing percentage on a flat contract or vice versa) from corridor-routing variance (mis-priced bank corridor) and from refund-non-reversal (MDR or flat fee retained on a refunded order).
- **Config:** Net banking sub-method split on the gateway parent fee line; ticket-size bucketing rule at the contracted break-even (default ₹500-700 band, parametrised on flat-fee value and percentage value); bank corridor column on each net banking transaction; expected-rate table keyed on contracted structure (flat versus percentage), per-corridor rate where corridor-specific contracted; NETBANKING_STRUCTURE_VARIANCE class for contracted-structure deviation; NETBANKING_CORRIDOR_VARIANCE class for mis-priced corridor; refund-fee-retention check class; 18% GST line matcher to GSTR-2B for the Input Tax Credit claim.
- **Output:** A per-transaction net banking variance report split by ticket band and bank corridor; a structure-choice analysis showing what the merchant's monthly net banking cost would be under each of flat-₹7, flat-₹12, flat-₹20, 1.8%, and 2% pricing on the actual transaction distribution; a corridor-mix dashboard for negotiating corridor-specific rates with the gateway; a refund-fee-retention exception list for gateway support; an Input Tax Credit claim schedule for the 18% GST on legitimate net banking fees.

### Netting Reconciliation in India: How to Handle Net Payments Between Counterparties

Source: https://www.terra-insight.com/insights/netting-reconciliation-india/

- **Problem:** Netting compresses multiple gross receivables and payables into a single bank settlement. The bank shows the net, but GST invoices, ITC, and TDS all operate on the gross — creating a matching gap between net cash and gross accounting entries.
- **Logic:** Keep gross invoices on both sides of the netting pair with full GST, then reconcile the net cash settlement against the sum of gross entries. For group netting, maintain a formal netting statement per month and tie the statement to individual counterparty ledgers; for marketplace platform netting, reconcile gross GMV, platform commission, and net payout separately.
- **Config:** Netting agreement library, group and counterparty-level gross-to-net mapping, GST invoice integrity rule (no net-of-offset invoicing), and marketplace commission parser.
- **Output:** Audit-evidenced netting statements, preserved gross GST and TDS positions, and a bank reconciliation that explains each net settlement by its underlying gross pairs.

### Net ITC Exclusion of Input Services and Capital Goods — Rule 89(5) Textile

Source: https://www.terra-insight.com/insights/net-itc-input-services-capital-goods-exclusion-rule-89-5-textile/

- **Problem:** A capital-intensive textile manufacturer running heavy spinning or dyeing machinery — a Surat synthetic yarn plant, a Bhilwara suiting mill, a Panipat home-textiles dyeing house — must apply the Rule 89(5) inverted-duty refund formula post Notification 14/2022 using a Net ITC that includes only input-goods ITC and excludes input services and capital goods. A monthly ITC ledger that mixes yarn purchases, PTA-MEG chemical inputs, job-work conversion charges, machinery maintenance AMCs, and plant capex must be split into three named buckets, reconciled to GSTR-2B invoice-by-invoice, and only Bucket 1 (input goods) enters the refund numerator. The exclusion can turn the Rule 89(5) formula output negative — no refund claimable — for capital-intensive operators even when input tax paid materially exceeds output tax collected.
- **Logic:** Build a split-ITC ledger keyed to GSTR-2B invoice reference; classify each invoice as input goods (Chapters 27/28/29/39/55/56 raw materials, packing, stores), input services (Chapter 99 SAC codes for job-work, freight, security, maintenance, audit, legal), or capital goods (plant, machinery, capitalised spares under Section 16(3)). Reconcile the three-bucket sum to Table 4A ITC availed in GSTR-3B for the month. Compute Rule 89(5) Net ITC = Bucket 1 only. Apply the formula: Max Refund = (Turnover of inverted-rated supply × Net ITC ÷ Adjusted Total Turnover) − Tax payable on inverted-rated supply. If output positive, file RFD-01 for the tax period with Statement 1A. If output zero or negative, do not file — carry the input-goods ITC accumulation forward to the next month. Track the 2-year time-limit under Section 54(14) end-of-month rule per tax period.
- **Config:** GSTR-2B ingestion feed with invoice-level HSN and SAC; input-goods master (HSN codes tagged as input for textile: yarn 5205-5510, chemicals 2905/2917/2941/3907, packing 4819/3923, stores and consumables); input-services master (SAC 998821 job-work of textile fabrics, SAC 996511 transport, SAC 998531 security, SAC 998714 maintenance and repair, SAC 998221 legal, SAC 998222 accounting); capital-goods flag on ERP asset-master invoices where capitalisation entry runs against fixed-asset ledger; monthly outward supply register with inverted-rated turnover flag (fabric HSN 5208-5212 at 5 percent output versus yarn HSN 5205 at 12 percent input, for example); Adjusted Total Turnover computation excluding turnover of nil-rated and exempt supplies; RFD-01 monthly filing calendar with tax period, refund amount, and 2-year expiry date.
- **Output:** A monthly Rule 89(5) worksheet: total ITC availed, split by input goods, input services, capital goods (three buckets, reconciled to GSTR-3B Table 4A); Net ITC (Bucket 1 only) as the refund numerator; turnover of inverted-rated supply and Adjusted Total Turnover as the refund denominator components; tax payable on inverted-rated supply as the subtractor; formula output as the Maximum Refund. A traffic-light view — green for positive refund periods (file RFD-01), amber for zero or borderline periods (defer), red for negative periods (do not file, carry accumulation). A 2-year expiry register per tax period so periods approaching write-off are surfaced 60 days before the end-of-month clock closes.

### New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams

Source: https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping/

- **Problem:** From April 1, 2026, every TDS challan, Form 131 (16A), and 26Q/27Q return must reference new Chapter XX section codes — Section 194C becomes 393(1) Sl. 6(i), 194J becomes 393(1) Sl. 6(iii), 194H becomes 393(1) Sl. 1(ii) — and ERPs still pointing to the 1961 Act codes will produce TRACES validation failures from day one.
- **Logic:** Maintain a dual-code mapping master that links every legacy section (192–206CE) to its 2025 Act equivalent and the associated four-digit payment code. Classify each TDS transaction by deduction date — legacy codes for deductions up to March 31, 2026, new codes from April 1, 2026 — and apply the matching side's code set during reconciliation against Form 26AS (now Form 168) and deductor certificates.
- **Config:** Section mapping master with old code, new Section 393 sub-clause, payment code 1001–1092, and effective-date metadata. Cross-year matching mode (legacy, new, or dual) selected by transaction date.
- **Output:** Challans and returns that validate on the updated TRACES portal from day one, cross-year Form 26AS matching that handles both code sets simultaneously, and a clean audit trail showing each transaction against the section code in force on its deduction date.

### New TDS and TCS Provisions FY 2026-27: What Indian Auto-Component Suppliers Must Reconfigure

Source: https://www.terra-insight.com/insights/new-tds-tcs-provisions-fy-2026-27-auto-component-india/

- **Problem:** A ₹400 crore Indian Tier-1 auto-component supplier transitioning from the Income Tax Act 1961 to the Income Tax Act 2025 on 1 April 2026 must remap nine distinct TDS / TCS payment streams from legacy 194x / 195 / 206C section references to new Sections 393 and 394 with payment codes 1001 to 1092 — across inbound freight (1023/1024), conversion charges (1023/1024), buyer-side raw-material purchase (1031), seller-side scrap TCS under §394, professional fees (1027), technical services (1026), forwarder commission (1006), rent (1009/1008), foreign-agent commission (1057), and interest (1022). The ERP and Tally chart of accounts, deductee masters, return-output templates, deposit calendars, deductee-credit reconciliation, and cross-era handling through FY 2026-27 all need a coordinated reset before 1 April 2026, with Form 168 / 131 / 141 replacing Form 26AS / 26Q / 27EQ.
- **Logic:** Build a code-mapping master that pairs every legacy 194x / 195 / 206C section with its new Section 393 / 394 counterpart and the new payment code, applying it consistently across ERP, Tally, deductee masters and return templates. Drive each payment stream through (a) the section determination, (b) the rate matrix, (c) the threshold logic per deductee per FY, (d) the form output (168 for deductee credit, 131 for deductor non-salary statement, 141 for collector TCS statement). Run a parallel cross-era reconciliation register from Q4 FY 2025-26 through Q1 FY 2026-27, holding legacy 194x deductions on legacy 26AS / 26Q lineage and new 393 / 394 deductions on new 168 / 131 / 141 lineage without netting. Verify ERP and Tally code masters point to the new codes by 31 March 2026 and to the legacy codes for all pre-1-April-2026 entries.
- **Config:** Code-mapping master with legacy-to-new pairs across nine auto-component payment streams, ERP and Tally chart-of-accounts update calendar, deductee master refresh with section code and rate per PAN, monthly TDS challan calendar (7th), monthly TCS challan calendar (7th), quarterly Form 168 / 131 / 141 calendar, cross-era reconciliation register, deposit-and-deductee-credit reconciliation per payment code, and a controller-level dashboard of remapping completeness pre-1-April-2026.
- **Output:** A nine-stream remapping dashboard showing pre-1-April-2026 readiness, code-mapping master integrity, ERP and Tally configuration verification, deductee master section-code coverage, monthly deposit and form-output completeness through FY 2026-27, cross-era reconciliation register running Q4 FY 2025-26 alongside Q1 FY 2026-27, and an audit-defensible trail of the transition.

### Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses

Source: https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india/

- **Problem:** Payment aggregator nodal accounts (T+1/T+2 merchant settlement) and RERA 70% escrow accounts are regulator-reviewed. Nodal balance above the unsettled obligation is commingling; below it is a settlement failure. RERA withdrawals without architect certification breach Section 4(2)(l)(D).
- **Logic:** Run daily nodal reconciliation where nodal balance equals sum of collected-but-unsettled buyer transactions. For RERA escrow, match every deposit (70% of each flat payment) and every withdrawal (against architect certificates and approved project expenses) to the RERA portal's registered escrow balance.
- **Config:** Nodal buyer-to-merchant ledger, T+1 and T+2 settlement SLA, RERA 70% deposit rule, withdrawal approval workflow tied to architect certificates, and interest income split (Section 194A TDS).
- **Output:** Regulator-ready audit trail for RBI payment aggregator reviews and RERA authority queries, daily nodal balance confirmation, and a withdrawal register that survives project audit.

### Chapter 27 Solvents Blocked: Notification 09/2022 for Pharma Refund Teams

Source: https://www.terra-insight.com/insights/notification-09-2022-chapter-27-solvents-blocked-refund-pharma/

- **Problem:** A Tier-2 India API-centric integrated pharma manufacturer running a principal Chapter 29 active pharmaceutical ingredient unit at Vishakhapatnam in Andhra Pradesh purchases hexane, isopropyl alcohol, methanol, toluene and methyl ethyl ketone at 18 percent GST at monthly aggregate of the order of Rs 24 crore, generating Rs 4.32 crore of Chapter 27-adjacent solvent ITC per tax period. Under CBIC Notification 09/2022-Central Tax (Rate) dated 13 July 2022, effective 18 July 2022, the direct statutory refund bar sits on the output side for Chapter 15 and Chapter 27 goods manufacturers — a Chapter 29 API output is not directly barred — but field-level scrutiny by proper officers has broadened the notification's practical footprint onto the buyer's Net ITC composition. The refund team must decide whether to include the Chapter 27 solvent leg in the Rule 89(5) Net ITC numerator (defensible legal position, exposes to deficiency-memo cycle) or to segregate it into a blocked-refund bucket (conservative position, projects Rs 40 to 55 crore annual working-capital lock-up per major refiner). The reconciliation must run invoice-level segregation from month one so both positions are held in the workbook, the refund claim discloses the Chapter 27 solvent leg transparently on Statement 1A, and the eventual management-judgement write-off decision on the segregated bucket has an auditable trail.
- **Logic:** Build a per-tax-period solvent purchase register keyed to the plant's state GSTIN, with each invoice tagged by HSN chapter (2710 hexane, 2905.11 methanol, 2905.12 isopropyl alcohol, 2902.30 toluene, 2914.12 methyl ethyl ketone) and by process-use context (extraction, crystallisation wash, azeotropic distillation, final purification, cleaning). Extract the aggregate solvent ITC from GSTR-2B and reconcile against the plant's accounting ledger. Hold two parallel Net ITC composition computations for the Rule 89(5) formula — a base-case (Chapter 27 solvent included, defensible legal position) and a carved-out case (Chapter 27 solvent segregated, conservative Notification 09/2022 field-level position). Prepare the Statement 1A invoice-level annexure with the Chapter 27 solvent leg disclosed as a distinct line. File Form GST RFD-01 monthly on the GST portal within two years of the relevant date. Track the solvent-recovery cycle separately — the recovery is internal captive use with no incremental ITC; the utilities driving the recovery sit in the general Net ITC pool, not in the segregated bucket. Project the annualised segregation lock-up into a working-capital plan; at the 12 to 18 month mark, apply the management-judgement write-off test against the electronic credit ledger utilisation prospects and, if negative, write off the segregated bucket through the profit and loss account with the auditable trail intact.
- **Config:** Plant master with GSTIN, state, Chapter 29 API output heading (2941 antibiotics, other Chapter 29 organic chemicals) and monthly outward supply capacity; solvent input HSN register anchored to Chapter 27 (2710 hexane) and Chapter 29 solvent headings (2902.30 toluene, 2905.11 methanol, 2905.12 isopropyl alcohol, 2914.12 methyl ethyl ketone); process-use tagging (extraction, crystallisation wash, reactor flush, azeotropic distillation, final purification, cleaning) on each solvent invoice line; per-tax-period Net ITC composition workbook with base-case and carved-out parallel computation; Statement 1A invoice-level annexure builder with the Chapter 27 solvent leg on a distinct line; solvent-recovery cycle register with recovery efficiency by solvent and by process step; utilities ITC bucket separated from the segregated Chapter 27 bucket; working-capital lock-up projection updated per tax period; management-judgement write-off decision framework with 12 to 18 month trigger point; deficiency-memo Form GST RFD-03 response templates for both positions.
- **Output:** A month-end refund pack per Chapter 29 API unit per GSTIN — Turnover of inverted-rated Chapter 29 output supply, Adjusted Total Turnover, Net ITC decomposed by input HSN chapter with the Chapter 27 solvent leg disclosed as a distinct line (both base-case and carved-out), input-services and capital-goods ITC identified and held aside from the Rule 89(5) numerator, the Notification 14/2022 amended-formula maximum refund computation under both positions, the Statement 1A invoice-level annexure, and the Form GST RFD-01 draft ready for portal submission. A parallel working-capital projection register aggregates the segregated Chapter 27 solvent bucket by tax period and by financial year, holding the year-end write-off decision framework against the electronic credit ledger utilisation trajectory. A solvent-recovery cycle register aggregates the recovered solvent volumes by primary solvent and by process step, tying back to the environmental-compliance filings under state pollution control board hazardous waste rules — the ITC treatment is fully carved out because the recovery is internal captive use with no supply.

### Notification 14/2022: How Net-ITC Reshaped Pharma Refund Math

Source: https://www.terra-insight.com/insights/notification-14-2022-net-itc-formula-amendment-pharma/

- **Problem:** A Tier-1 integrated pharma active pharmaceutical ingredient plant at Ankleshwar in Gujarat, filing quarterly Section 54(3) refunds against accumulated inverted-duty input tax credit, must apply the Notification 14/2022-Central Tax amended Rule 89(5) formula to every refund application filed on or after 5 July 2022. The amendment codified the exclusion of input services and capital goods from the Net ITC numerator — a position already confirmed by the Supreme Court in Union of India v. VKC Footsteps India Pvt Ltd (2021) 10 SCC 674 — and produces a permanent recurring reduction in refund quantum against pre-amendment claim benchmarks. For a plant with a normal quarterly Net ITC composition of roughly 25 to 35 percent non-goods (input services plus capital goods), the reduction is of the order of Rs 3 to 4 crore per quarter or Rs 12 to 16 crore per year, and the plant's Statement 1A invoice-level annexure to Form GST RFD-01 must disclose the Net ITC composition without the input-services and capital-goods legs even where those legs sit as ordinary ITC in the electronic credit ledger.
- **Logic:** Build a per-invoice input classification register that tags every inward supply from GSTR-2B and the plant's own purchase ledger as goods (Net ITC eligible), input services (excluded from Net ITC) or capital goods (excluded from Net ITC), anchored to the vendor invoice HSN chapter and the accounting treatment in the plant's books. Build a Net-ITC composition workbook per tax period per GSTIN that decomposes the eligible-goods leg by HSN chapter — active pharmaceutical ingredient intermediates, key starting materials, packaging, excipients — and holds the input-services and capital-goods legs in separate parallel ledgers that feed the electronic credit ledger but not the Net ITC numerator. Apply the Notification 14/2022 amended Rule 89(5) formula: Maximum Refund = (Turnover of inverted-rated supply × Net ITC / Adjusted Total Turnover) minus (Tax payable on inverted-rated supply × Net ITC / ITC availed on inputs and input services). Generate the Statement 1A annexure line-for-line matched to the composition workbook. File Form GST RFD-01 quarterly. Maintain a pre-versus-post 5 July 2022 refund quantum trend chart for treasury projection and board reporting.
- **Config:** Per-invoice input classification register with three tags — goods, input services, capital goods — anchored to HSN chapter and accounting treatment; Net-ITC composition workbook per plant GSTIN per tax period; input-services ledger held separate (freight, external analytical laboratory, quality-control AMC, engineering consulting, plant maintenance); capital-goods ledger held separate (reactors, granulators, compression machines, packaging lines, HVAC additions); Notification 14/2022 amended Rule 89(5) formula computation; Statement 1A invoice-level annexure builder line-matched to the composition workbook; Form GST RFD-01 electronic filing feed; pre-versus-post 5 July 2022 refund quantum trend chart for permanent-recurring-reduction quantification; treasury projection against RFD-04 provisional refund receipt and RFD-06 final sanction timing; two-year filing window monitor under Section 54.
- **Output:** A quarterly refund pack per plant per GSTIN: input classification register with per-invoice goods-services-capital-goods tagging; Net-ITC composition workbook decomposing the eligible-goods leg by HSN chapter; input-services and capital-goods ledgers held separate and excluded from the Net ITC numerator; Notification 14/2022 amended Rule 89(5) formula computation showing the maximum refund; Statement 1A invoice-level annexure ready for portal submission; Form GST RFD-01 draft filed electronically; pre-versus-post 5 July 2022 refund quantum trend chart quantifying the permanent recurring reduction against legacy benchmark; and a rolling treasury projection matching each filed RFD-01 to expected RFD-04 provisional receipt within seven days and RFD-06 final sanction post scrutiny, sized to the post-amendment refund quantum rather than the pre-amendment claim base.

### NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing

Source: https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india/

- **Problem:** Pharmaceutical manufacturers in India operate under NPPA price ceilings on scheduled formulations under DPCO 2013 — annual WPI-linked ceiling revision, the 10% annual MRP-increase cap on non-scheduled formulations, trade margin caps between manufacturer-stockist-retailer including Trade Margin Rationalisation on notified drugs, Form V overcharging certificate workflow, and SKU-level MRP compliance across multiple pack sizes and dosage strengths.
- **Logic:** Tag every SKU as scheduled or non-scheduled at master setup with the active NPPA ceiling per unit; back-calculate MRP-permissible from ceiling × units per pack + GST; verify monthly that actual MRP and invoice price-to-stockist stay within ceiling × pack-size + permitted trade margin; apply WPI-linked annual ceiling update on the cutover date; track 10% YoY MRP-increase dashboard for non-scheduled SKUs; feed Form V certification workflow on any overcharging variance.
- **Config:** SKU master with scheduled / non-scheduled flag, active NPPA ceiling per unit, pack-size and dosage strength, MRP history with effective dates, trade-margin envelope per channel partner, Trade Margin Rationalisation flag for notified drugs, WPI annual update workflow, Form V variance computation.
- **Output:** A monthly NPPA compliance close where every scheduled-formulation SKU has MRP within (ceiling × pack-size + GST), invoice-to-stockist stays within permitted trade margin, non-scheduled SKUs report YoY MRP increase against the 10% cap, the WPI annual update flows cleanly across all scheduled SKUs at the cutover, and any overcharging variance feeds a Form V certification draft with interest computation.

### NRI Property Seller TDS: Section 195 (Not 194IA) — the Highest-Cost Compliance Trap

Source: https://www.terra-insight.com/insights/nri-property-seller-tds-section-195-vs-194ia-india/

- **Problem:** A buyer purchasing residential or commercial property in India from an NRI seller must withhold under Section 195 (not Section 194IA), which requires the buyer to hold a TAN, deduct at the rate applicable to the seller's capital gain (LTCG at 20% plus surcharge 10-37% plus 4% cess, or STCG at the seller's slab rate), deposit via ITNS 281 and file quarterly Form 27Q. The seller must furnish Form 15CA and Form 15CB before the authorised dealer bank will remit the net sale consideration to the seller's foreign account. Misclassification as Section 194IA at 1% leaves the buyer with a Section 201(1) shortfall of ~90% of the correct withholding plus Section 201(1A) interest and Section 234E fee — for a ₹1.8 crore sale with ₹90 lakh LTCG the shortfall is around ₹19.7 lakh crystallising as buyer liability, before interest and fees.
- **Logic:** Determine seller residency under Section 6 of the Income Tax Act at the date of transfer — Section 195 applies to any seller who is non-resident on that date, regardless of citizenship. Compute the seller's capital gain: for a holding period above 24 months apply indexation using the Cost Inflation Index of the acquisition year and the transfer year, arriving at long-term capital gain taxed under Section 112 at 20%; for a holding period at or below 24 months treat as short-term capital gain taxed at the seller's applicable slab rate. Layer surcharge on the tax based on the gain size (10% above ₹50 lakh, 15% above ₹1 crore, 25% above ₹2 crore, 37% above ₹5 crore) and 4% health and education cess on the tax plus surcharge. Deduct the resulting amount from the gross consideration payable to the seller. Where the seller has obtained a Section 197 lower-deduction certificate, apply the certified rate instead. File Form 27Q for the quarter of deduction, issue Form 16A to the seller, and reconcile against seller's Form 26AS and the CA-issued Form 15CB used by the bank for remittance.
- **Config:** Transaction master with buyer PAN, seller PAN, seller residential status at date of transfer (based on Section 6 test — physical presence in India in the previous year); acquisition date and acquisition cost for the seller (for indexation and holding period); Cost Inflation Index table by year for the LTCG computation; Section 112 rate table (20% LTCG on immovable property) and STCG slab rate mapping; surcharge slab table keyed to gain amount; buyer's TAN registration status (Form 49B if pending); banking channel used for consideration payment; Form 27Q filing calendar keyed to buyer's TAN; Form 15CA / 15CB tracker keyed to the outward remittance to the seller's foreign account; Section 197 lower-deduction certificate registry.
- **Output:** A per-transaction withholding computation showing gross consideration, holding period, indexed cost, capital gain, applicable rate (Section 112 LTCG or slab STCG), surcharge percentage, cess, net withholding amount, and net remittance to seller; a Form 27Q quarterly filing pack tying deductions to the buyer's TAN with challan references (ITNS 281); a Form 16A issued to the seller with the CA-issued Form 15CB attached to the bank remittance file; an audit-ready evidence trail proving seller's residential status at transfer date, the indexation basis, and the surcharge bracketing so a subsequent scrutiny can be closed on the buyer's side without a Section 201(1) exposure.

### Ocean Freight and Container Tracking Reconciliation for Indian Exporters

Source: https://www.terra-insight.com/insights/ocean-freight-container-tracking-reconciliation-india/

- **Problem:** An Indian exporter running 240 FCL containers annually across Nhava Sheva, Mundra, Chennai and Visakhapatnam ports reconciles a five-leg ocean export shipment with per-container traceability through factory → ICD → port → vessel → destination, demurrage and detention computation at each origin and destination free-period clock, RoDTEP/RoSCTL post-shipment claim per shipping bill against expected and actual scrip credit, FEMA + EDPMS export-realisation discipline within the nine-month prescribed period, and a Section 16 IGST zero-rated supply position with either LUT-without-IGST or IGST-paid-with-refund election. Failure on any leg cascades — unrealised exports disqualify RoDTEP claims, demurrage misallocation distorts landed cost, and GST classification errors break the zero-rated refund.
- **Logic:** Build a per-container master keyed by shipping-bill number with origin factory, ICD route, gateway port, container number, BL number, vessel name, sailing date, destination port and consignee. Track the demurrage and detention clock per container at origin (gate-in to vessel-loading) and at destination (vessel-arrival to gate-out) against contracted free period and published tariff. Compute RoDTEP/RoSCTL claim per shipping-bill using HSN rate × quantum × FOB; age against actual scrip credit in ICEGATE. Maintain EDPMS-side per-shipping-bill realisation status against the nine-month FEMA deadline. Classify ocean-freight GST per shipment under Section 16 zero-rated rule with LUT or IGST-paid election. Recover demurrage and detention where third-party-attributable through carrier or consignee claim.
- **Config:** Container master keyed by shipping-bill number with origin, ICD, port, BL, vessel, sailing date, destination and consignee; demurrage and detention clock per container per leg with port and shipping-line tariffs; RoDTEP/RoSCTL HSN-rate matrix with expected-credit calculator; ICEGATE scrip-credit ingest; EDPMS realisation status per shipping-bill against nine-month FEMA deadline; FIRC/BRC register per export realisation; GST classification engine for Section 16 zero-rated with LUT-vs-IGST-paid election flag; ITC refund computation per period; demurrage recovery register with third-party-attribution flag.
- **Output:** A per-shipping-bill reconciliation pack with five-leg movement, demurrage and detention computation, RoDTEP/RoSCTL expected vs actual claim, EDPMS realisation status against FEMA deadline, Section 16 zero-rated election with refund route, demurrage recovery register with ageing 30/60/90; quarterly RoDTEP/RoSCTL scrip-credit reconciliation; monthly ITC-refund computation for LUT-route exports; annual FEMA realisation compliance log for AD-bank reporting.

### OEKO-TEX, GOTS Compliance Reconciliation for Textile India

Source: https://www.terra-insight.com/insights/oeko-tex-gots-compliance-reconciliation-textile-india/

- **Problem:** An Indian home-textile or garment exporter running an OEKO-TEX Standard 100 chemical-safety programme across its product portfolio and a GOTS-certified organic cotton line must reconcile certification cost registers, classify each cost line as capital versus revenue under Ind AS 38 recognition criteria, amortise capitalised initial certifications over the estimated three-year market-access period, expense annual renewals under Section 37(1) of the Income-tax Act 2025, maintain a Transaction Certificate traceability register chaining every certified quantity from farm through gin, spin, weave, dye, finish, cut, stitch to finished export shipment, and compute the deferred tax impact of the book-versus-tax amortisation difference — all against a certification cost pool the statutory auditor tests at year-end and the buyer sustainability auditor tests at the shipment level.
- **Logic:** Build a certification cost register keyed by certification body invoice reference, with cost lines classified as (a) initial certification (capital under Ind AS 38, amortise over three-year useful life on straight-line basis), (b) annual renewal (revenue under Section 37(1), expense in year of incurrence), (c) unit-level testing (revenue), and (d) transaction certificate issuance fees (revenue). Maintain a per-unit and per-product-class allocation table so that OEKO-TEX Class I baby-article certification cost is not pooled with Class II bedding certification. Chain every GOTS Transaction Certificate to the originating farm certificate and cross-verify the certified quantity carried through every hop against the physical dispatch register from cotton bale through ginner, spinner, weaver, dyer, finisher, and cutting-stitching unit. Post monthly amortisation on capitalised certifications; compute the deferred tax impact of the book-versus-tax amortisation difference under Ind AS 12; and produce the year-end certification cost pack for statutory audit and the shipment-level traceability pack for buyer sustainability audit.
- **Config:** Certification body master with accreditation reference, scope of certification (OEKO-TEX Class I to IV; GOTS scope certificate), and unit-and-product-class mapping; Ind AS 38 classification rules per cost category (initial certification capital, annual renewal revenue, testing revenue, Transaction Certificate revenue); amortisation schedule with useful-life setting (default three years for GOTS initial, one year for OEKO-TEX renewal treated as opex); Transaction Certificate register with certificate number, issuing body, issuing party, receiving party, certified quantity, and reference to the upstream Transaction Certificate; deferred tax computation for the book-versus-tax difference (straight-line versus written-down-value); and audit-ready output templates for statutory audit certification note and buyer sustainability audit shipment-level pack.
- **Output:** A year-end certification cost pack: opening intangible asset balance for capitalised certifications, additions in the year at unit and product level, amortisation charge for the year, closing net book value, and roll-forward across three years; annual renewal expense schedule with Section 37(1) deduction claim; per-shipment Transaction Certificate traceability chain from farm to finished product; deferred tax computation under Ind AS 12 covering the amortisation timing difference; and a discrepancy log flagging any Transaction Certificate chain break, missing certification body invoice, mis-classified cost line, or amortisation posting gap.

### Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths

Source: https://www.terra-insight.com/insights/odoo-reconciliation-india/

- **Problem:** Odoo's India localisation (l10n_in, l10n_in_gst, l10n_in_edi) covers GST tax determination, e-invoice IRN, and GSTR-1/3B return generation in Enterprise, but no native GSTR-2B matching against the purchase register, no Form 26AS reconciliation, and no TDS on vendor payments under 194C/194J without Studio customisation or partner modules — leaving Indian SMEs on Odoo to reconcile externally above 300 purchase invoices per month.
- **Logic:** Add an external reconciliation layer via Odoo XML-RPC at /xmlrpc/2/object (or JSON-RPC), pulling account.move, account.move.line, account.bank.statement.line, and res.partner models. Authenticate via API key (Odoo 14+). Ingest GSTR-2B, Form 26AS, and bank MT940 externally, run multi-pass matching with variance taxonomy, and post cleared status back by creating account.payment and reconciliation records via XML-RPC.
- **Config:** Odoo connector with XML-RPC/JSON-RPC endpoints, API key authentication, model registry (account.move, account.move.line, account.bank.statement.line, res.partner), rate-limit-aware batch scheduler (Odoo.sh caps 100 req/min), GSTR-2B JSON adapter, Form 26AS parser, and writeback job creating payment and reconciliation records.
- **Output:** An Indian Odoo deployment (Community or Enterprise) reconciled beyond the native GSTR-1/3B layer — GSTR-2B invoice-level matching, Form 26AS TDS receivable matching, bank reconciliation at scale, and cleared status written back to Odoo's native UI for CA and auditor review.

### OEM Debit Note Dispute Recovery for Indian Tier-1 Manufacturers

Source: https://www.terra-insight.com/insights/oem-debit-note-dispute-recovery-india/

- **Problem:** Indian Tier-1 component manufacturers carry significant unrecovered tail of OEM debit notes on their books each quarter. The debit notes arrive in distinct operational classes — quality reject, quantity short, raw-material price variance pending, fitment or modification pending, line-stop penalty, tooling amortisation — but get pooled into a single dispute queue, routed to the wrong OEM counterparty, evidenced with the wrong documents, and aged past the dispute window. The result is that disputable debit notes harden into write-offs, the Section 34 credit-note window closes leaving tax-neutral settlement impossible, and the finance team accepts a structurally lossy operating equilibrium where 60 to 80 per cent of debit-note rupees are simply absorbed.
- **Logic:** Build a five-class classification matrix that names each OEM debit-note type with its evidence requirement, dispute window, and owner. Maintain a dispute documentation library so every class has the right artefacts attached at filing time. Operate a four-tier escalation route from SQA to plant finance to corporate AP to the CFO office with SLAs at each tier. Issue Section 34 GST credit notes within the GSTR-1 amendment window for any commercially conceded debit note. Track disputes in four ageing buckets with class-weighted recovery probabilities. Feed the OEM debit-note sub-register into the broader Discovered Money register and the quarterly audit-committee leakage pack.
- **Config:** Five-class classification matrix (quality, quantity, RMPV-pending, FOMP, line-stop, tooling amortisation) with evidence list, dispute window, and OEM-side owner per class. Dispute documentation library per class (rejection slip, QC report, ASN, GRN, weighbridge slip, line-stop notification, RMPV registration, engineering change order, tooling amortisation schedule). Four-tier escalation route (SQA, plant finance, corporate AP, CFO office) with SLAs at each tier. Section 34 GST credit-note workflow with GSTR-1 amendment cycle. Four ageing buckets (0-30, 30-60, 60-90, 90-plus) with class-weighted recovery probabilities. OEM debit-note sub-register feeding the broader Discovered Money register.
- **Output:** A live OEM debit-note dispute register with class, OEM counterparty, evidence status, dispute tier, ageing bucket, Section 34 credit-note status, and recovery state. A monthly recovery-rate report by class and by OEM. A quarterly OEM debit-note pack for the audit committee covering disputed value at start of quarter, rupees recovered, rupees moved to write-off, and trend versus prior quarters. An annual class-mix review that drives engineering change-order discipline, RMPV registration hygiene, and tooling amortisation contracting practice.

### OEM Debit Note Disputes: When to Accept, When to Contest (Indian Auto Components)

Source: https://www.terra-insight.com/insights/oem-debit-note-dispute-accept-vs-contest-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers face 5-12% of monthly OEM billing as debit notes across seven categories (FOMP, JIT shortage, quality penalty, line-stop, tooling, transport, technical service). Each debit triggers an accept-or-contest decision against a 30-60 day contractual dispute window, an overlay Section 34 GST credit-note cutoff at 30 November of the next FY, evidence requirements specific to the debit category, and a relationship-cost weighting against the OEM's supplier rating.
- **Logic:** For each posted debit, classify by reason code, identify the contractual basis (PO clause, master supply agreement, quality manual), assess evidence strength (claim ID, rejection slip, batch traceability, 8D response), check the dispute-window expiry, overlay the Section 34 GST cutoff, weigh relationship cost on the OEM rating, and route to accept-and-credit-note, accept-without-credit-note, or contest-with-documented-response based on the decision matrix per category.
- **Config:** Debit-reason taxonomy with claim-ID-to-source mapping, contractual basis register per OEM (PO clause, MSA clause, quality manual reference), evidence checklist per debit category, dispute-window calendar with 30/45/60-day reminders by OEM, Section 34 GST calendar trigger, relationship-cost weight by OEM and trailing contest rate, accept-vs-contest decision matrix per reason code with principal-amount and evidence-strength thresholds.
- **Output:** A debit-note action queue per OEM showing each posted debit with classification, evidence strength score, contractual basis, dispute-window timer, Section 34 GST cutoff timer, recommended action (accept / accept-no-credit / contest), and relationship-cost flag. A monthly contested-debits ledger with response-letter status. A win-rate trend by debit category and by OEM.

### OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers

Source: https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india/

- **Problem:** Indian OEMs run JIT/JIS supply through rolling scheduling agreements transmitted by EDI — 830 planning schedules, 862 firm call-offs, 856 ASNs — or via portals (Maruti e-Nagare, Tata Motors supplier portal, Bosch SupplyOn). Quantities are cumulative (CUM), not discrete, so a single dropped ASN permanently drifts the supplier CUM-shipped from the OEM CUM-received, while GST e-invoice and e-way bill ride alongside the ASN and a supplier may invoice many ASNs as one periodic tax invoice.
- **Logic:** Reconcile four-way on a cumulative basis per part and ship-to: 830 scheduled forecast (planning only) is excluded from invoiceable quantity; 862 firm call-off sets the authorised dispatch; 856 ASN CUM-shipped is matched against OEM GRN CUM-received within the part-level delivery tolerance; periodic GST tax invoice quantity is reconciled to confirmed received quantity for the billing window; CUM drift between supplier-shipped and OEM-received is surfaced as a standing exception until both sides agree the cumulative.
- **Config:** Part master keyed by OEM plant code, ship-to point (line vs store) and scheduling-agreement number, with over/under delivery tolerance band per part; EDI map for 830 (forecast horizon), 862 (firm-from date, CUM-required), 856 (ASN, CUM-shipped, pack/SNP structure); GRN feed carrying OEM CUM-received; e-invoice IRN and e-way bill number linked to each consolidated tax invoice; CUM reset markers (year-start / model-start) per agreement.
- **Output:** A per-part cumulative reconciliation showing 862 CUM-required vs 856 CUM-shipped vs GRN CUM-received with open-requirement and CUM-drift flags, ASN-to-GRN match status inside tolerance, a many-ASN-to-one-invoice quantity reconciliation per billing window with e-invoice and e-way bill linkage, and an exception queue for forecast-vs-firm gaps, over/under-delivery beyond tolerance, missing-ASN cascades, and CUM drift awaiting joint correction.

### How Indian Auto Component Suppliers Handle OEM Short-Pays: A Finance Team Guide

Source: https://www.terra-insight.com/insights/oem-short-pay-handling-auto-component-india/

- **Problem:** Indian auto-component suppliers face structural OEM short-pay of 5-12% of monthly billing through auto-debit mechanisms, with seven debit-reason categories spanning FOMP, JIT shortage, quality penalty, line-stop, tooling adjustment, technical service, and transport recovery. Each debit must be tied to the source invoice via claim ID, classified by reason, decided as accept or contest within a 30-day window, issued a Section 34 GST credit note if accepted before 30 November of the next FY, aged against the 180-day Rule 37 ITC reversal clock, and tracked through the Tier-2 passthrough register.
- **Logic:** Decompose each OEM payment advice into base invoice net plus n discrete debit memos, link each debit memo to its source invoice through the claim ID or rejection slip, classify by reason taxonomy (FOMP / JIT shortage / quality / line-stop / tooling / technical service / transport), route to the accept-or-contest workflow based on evidence strength, issue the GST credit note within Section 34's 30 November cutoff if accepted, age unpaid short-pays in 60 / 90 / 150 / 180-day buckets against Rule 37, and trigger the Tier-2 passthrough entry where the root cause is sub-vendor attributable.
- **Config:** OEM customer master keyed by plant code and vehicle programme, debit-memo reason taxonomy with claim-ID-to-invoice mapping, FOMP running account per OEM keyed to warranty claim ID, GST credit-note workflow with Section 34 30-November calendar trigger, Rule 37 ageing buckets at 60 / 90 / 150 / 180 days, accept-vs-contest decision matrix per reason code, Tier-2 passthrough register linking each accepted OEM debit to a Tier-2 back-charge candidate.
- **Output:** A daily OEM short-pay decomposition view showing billed vs paid vs reason-coded debit variance per customer, a Section 34 GST credit-note action queue keyed by approaching cutoff, a Rule 37 ITC-reversal risk register by short-pay age band, a Tier-2 passthrough debit register matched to each accepted OEM back-charge, and a contested-debit queue with evidence trail and dispute-window timer.

### OEM Short-Pay Leakage for Indian Manufacturers: Decomposition and Recovery

Source: https://www.terra-insight.com/insights/oem-short-pay-leakage-manufacturer-india/

- **Problem:** Indian Tier-1 and Tier-2 manufacturers supplying automotive, capital goods, and appliances OEMs absorb 2-4% annual leakage on their OEM receivables because the OEM applies short-pay deductions at month-end aggregated cash settlement without per-invoice debit-note traceability. Standard deduction categories — Raw Material Price Variance pending, quality debit, line-stop, FOMP, freight-on-own-account, advance-recovery — are contractually valid in principle but applied at incorrect rupee values in practice. Without an ageing workflow that surfaces the cash-credit variance per invoice within the dispute window, more than half of disputable short-pay ages out of recovery.
- **Logic:** Maintain an OEM receivable ledger keyed by invoice number, taxable value, GST split, expected payment date per OEM contract, actual credit date, actual credited value, and computed cash variance. On every OEM cash credit, auto-allocate to oldest open invoices first, surfacing the residual short-pay per invoice. Match the residuals against the OEM's debit-note register by month — invoices with a matching debit note enter the disputable-or-accepted queue; invoices without a debit note enter the structural-short-pay queue. Age each queue in 60 / 90 / 150 / 180-day buckets keyed to invoice date. Flag short-paid invoices for Section 34 credit-note generation if dispute is abandoned.
- **Config:** OEM receivable ledger with invoice-level granularity. Cash-credit allocation engine on oldest-open-first or contract-specified order. Debit-note reconciliation pipeline by OEM by month. Short-pay decomposition classifier with categories RMPV pending, quality debit, line-stop, FOMP, freight-on-own-account, advance-recovery, structural. Ageing buckets 60 / 90 / 150 / 180 days with bucket-specific dispute action. Section 34 credit-note generator for accepted short-pays within window. Audit trail of every dispute filed, accepted, rejected, settled.
- **Output:** A daily OEM short-pay dashboard by OEM and invoice with rupee variance, age, debit-note status, and dispute window remaining. A weekly dispute pack ready to send to OEM AR-AP desk. A monthly Section 34 credit-note queue with arithmetic prepared. A quarterly OEM-wise leakage trend feeding the Discovered Money register on partial-payment and unexplained-variance classes. A standing recovery register tracking disputable vs structural classifications and recovery rates.

### OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components

Source: https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india/

- **Problem:** Indian Tier 1 auto-component suppliers face structural short-pays of 5-12% of monthly OEM billing through auto-debit mechanisms — FOMP warranty back-charges at 1-3% of billing, quality penalty deductions, JIT delivery shortage debits, line-stop charges, and tooling adjustments. GST credit-note timing under Section 34, Rule 37 ITC reversal at 180 days, and Section 393(1) Sl. 6(i) contractor TDS on subcontract job-work all overlay the settlement cycle, and a single OEM debit memo can hit four ledgers.
- **Logic:** Reconcile every OEM payment against the cumulative billing run net of debit memos, classify each debit by reason code (FOMP, JIT shortage, quality penalty, line-stop, tooling, transport), tie each debit to the originating claim ID and underlying invoice, decide GST credit-note action within the Section 34 window, age unpaid short-pays against the 180-day Rule 37 ITC reversal clock, deduct Section 393(1) Sl. 6(i) codes 1023/1024 on subcontract job-work invoices, and maintain a Tier 1 to Tier 2 back-charge passthrough register so quality recoveries flow down the chain.
- **Config:** OEM customer master keyed by plant code and vehicle programme, debit-memo reason taxonomy with claim ID and link to source invoice, FOMP running account per OEM, GST credit-note workflow keyed to Section 34 30-November cutoff, Rule 37 ageing buckets at 60/90/150/180 days, Section 393(1) Sl. 6(i) vendor rate matrix with codes 1023/1024 default, JIT call-off schedule by part number with shortage tracking.
- **Output:** A daily OEM settlement view per Tier 1 customer showing billed vs paid vs debited amount with reason-coded variance, FOMP exposure aged by claim ID, GST credit-note action queue by approaching Section 34 cutoff, Rule 37 ITC-reversal risk register by short-pay age, monthly Section 393(1) Sl. 6(i) TDS challan tied to subcontract payments, and Tier 2 passthrough debit register linking each OEM back-charge to the recovery raised on the sub-tier supplier.

### OEM Vendor Audit Preparation for Auto-Component Suppliers: Maruti, Tata, Mahindra, Bosch

Source: https://www.terra-insight.com/insights/oem-vendor-audit-preparation-auto-supplier-india/

- **Problem:** OEM vendor audits — Maruti SVA, Tata SQUA, Bosch BVDA, Mahindra MGE — have a finance dimension that is the one most Tier 1 controllers underprepare for. Each OEM tests a slightly different document pack: Maruti emphasises SA-to-bank-receipt trail and debit-note resolution ageing, Tata emphasises GST and ITC-04 hygiene plus Form 26AS three-way match, Bosch emphasises Section 393/394 deposit timeliness and SupplyOn portal compliance, Mahindra emphasises Section 143(3)(i) internal-financial-controls evidence and Tier 2 sub-supplier development. A combined SVA plus BVDA audit at a supplier serving both OEMs requires the union of all four document packs prepared in a 90-day window.
- **Logic:** Maintain a perpetual document pack covering: SA register per OEM with version control, dispatch-to-GRN-to-invoice-to-payment trail per OEM, debit-note resolution log per OEM with ageing, RMPV claim file with constraint-policy tier, ITC-04 quarterly filings for free-issue steel, Form 26AS three-way match working updated monthly, Section 393/394 deposit ledger and quarterly Form 26Q / 27EQ returns, quality reserve / FOMP provision walk, Section 143(3)(i) internal-financial-controls evidence pack, Tier 2 sub-supplier development log. Run a 90-day preparation schedule when an audit window is confirmed.
- **Config:** Audit-readiness register tagging each document pack item to OEM (Maruti / Tata / Bosch / Mahindra), source system (ERP / OEM portal / GST portal / TRACES), refresh frequency (daily / monthly / quarterly), and last-refresh date. OEM-audit-checklist library per OEM updated annually from OEM vendor development team. Anticipated-finding register with management response template. Materiality threshold for reconciliation deltas. Mock-interview question library for senior team brief.
- **Output:** An audit-day binder per OEM with the requested document pack indexed and traceable, an internal-walk-through report showing pre-audit exception resolution, a management response file for anticipated findings, a 0-finding or low-finding audit outcome that maintains the supplier's preferred-supplier status, and a post-audit corrective-action plan for any remaining findings ready for the next audit cycle.

### Old-Gold Exchange Against New Jewellery Purchase: Rule 32(5) Valuation

Source: https://www.terra-insight.com/insights/old-gold-exchange-new-purchase-reconciliation-section-194ia-india/

- **Problem:** Indian jewellers routinely accept old gold jewellery in exchange against new purchases — a national retail practice worth an estimated 25 to 30 percent of urban jewellery revenue by value. The transaction structure appears simple (new price minus old trade-in equals net invoice), but the GST treatment is a two-supply construct, not a one-supply construct: the new-jewellery leg attracts 3% GST on the full value plus 5% on making charges (or 3% consolidated on composite supply), while the old-gold leg either sits outside GST (unregistered customer) or attracts Rule 32(5) margin-scheme valuation on later resale as second-hand goods. Jewellers that intuitively charge GST on the net invoice trigger undervaluation notices under Section 73/74. Compounding the confusion, retail customers and even some accountants apply Section 194-IA (TDS on immovable property) to the transaction — this is an outright misreading of the statute, since 194-IA covers only land and buildings, not jewellery.
- **Logic:** Treat the old-gold-in and the new-jewellery-out as two separate flows on every invoice. Determine the customer's registration status: if unregistered (retail individual selling personal-use jewellery), the old-gold-in leg is not a taxable supply, no reverse-charge liability arises for the jeweller under the current suspension, and the incoming gold is inventoried at the negotiated buy-back rate. Charge GST on the new-jewellery-out leg at 3% on the gold value plus 5% on making charges (or 3% on composite supply per CBIC Circular 47/21/2018-GST), computed on the full value of the new jewellery — not on the net after trade-in. Show the trade-in credit as a below-the-tax-line adjustment to the payable amount, not as a value reduction to the taxable base. Book the incoming gold to inventory at cost; when later resold as-is, apply Rule 32(5) margin-scheme (3% on the margin between resale price and buy-back cost); when remade into new stock, treat the remade item as a new taxable supply at full transaction value. Separately track Section 206C(1F) 1% TCS on cash jewellery sales above ₹5 lakh (a seller obligation on cash consideration, not TDS on the buyer). Never invoke Section 194-IA — it does not apply to jewellery.
- **Config:** Two-line invoice template — Line 1 (new jewellery, HSN 7113, 3% GST on full gold value, 5% on making charges); Line 2 (trade-in credit at negotiated buy-back rate, no GST, shown as payable reduction below the tax total). Purity-assay register linked to each incoming trade-in (weight, karat, buy-back rate, customer PAN if consideration exceeds Section 269ST threshold). Inventory-flow tag on incoming gold — 'resale-as-second-hand' or 'melt-remake' — determined at intake and enforced through the manufacturing traceability chain. Rule 32(5) sub-ledger tracking margin-scheme resales separately from full-value new-jewellery sales. Section 206C(1F) TCS register on cash sales above ₹5 lakh with 1% collection posted in Form 27EQ. Section 269ST cash-receipt monitoring at ₹2 lakh threshold. Karigar labour bill reconciliation to Section 393(1) Sl. 4 (legacy 194C) TDS at code 1001 or 1023 depending on karigar constitution.
- **Output:** A monthly jewellery exchange reconciliation pack: opening old-gold inventory (weight, karat, cost), incoming trade-ins by customer segment (registered / unregistered), outflows split by resale-as-second-hand (Rule 32(5)) versus melt-remake (new supply at full value), and closing inventory. The new-jewellery sales register cross-foots to the GSTR-1 taxable value on HSN 7113 at 3% and the making-charges line at 5%. The Rule 32(5) sub-ledger separately reports margin-scheme value for second-hand-resale supplies. Section 206C(1F) TCS collection on cash jewellery sales above ₹5 lakh reconciles to Form 27EQ. Trade-in credits below the tax line reconcile to the customer receipt (bank / UPI / cash-with-269ST-check). No Section 194-IA line ever appears on the pack — the section does not apply.

### One Engine, 24 Industry Presets: Multi-Tenant Reconciliation Architecture for Indian Businesses

Source: https://www.terra-insight.com/insights/one-engine-24-industry-presets-reconciliation-architecture-india/

- **Problem:** Indian groups increasingly operate across multiple industries — a lending holding company with an NBFC arm, a rental-property arm, and a fintech subsidiary; a hospital chain that also runs a pharmacy retail business; a diversified conglomerate that touches jewellery retail, real estate, streaming media, and healthcare. Each industry has statutory rules that differ materially: GST composite-supply for hospitals versus mixed-slab pricing for jewellers, RERA escrow for developers versus PG settlement for OTT platforms, Section 194IA on property transfer versus Section 194O on marketplace commissions. Running a separate reconciliation system per industry doubles the audit training burden, multiplies the integration cost, fragments the audit trail across formats the CFO's auditor cannot compare, and blocks Ind AS 108 segment consolidation because the reconciling items across segments no longer share a common taxonomy.
- **Logic:** Build a single reconciliation engine — the matching primitives, the accounting-identity checks, the paise-exact rounding, the audit-trail recorder — and express every industry-specific rule as a configuration bundle loaded at run time. The configuration bundle carries the rate matrix (GST slabs, TDS section rates, TCS rates for the industry), the field mappings (bank narration formats, ERP journal patterns, gateway settlement schema), the variance taxonomy overlay (industry-specific reason codes), the reconciliation cadence, and the settlement flow. The engine reads the configuration at reconciliation start, applies the industry rules, and produces the same audit-trail record format regardless of which industry configuration was loaded. When a group consolidates for Ind AS 108 segment reporting, the reconciling items across segments share a common variance taxonomy because the engine is common.
- **Config:** Industry preset library covering the 24 industries in scope (jewellery retail, residential real estate, gold-loan NBFC, streaming and OTT, hospital and healthcare, FMCG general trade, auto components, pharmaceuticals, IT services, hospitality, quick commerce, restaurant chains, retail modern trade, D2C brands, education services, logistics 3PL, insurance intermediary, financial services broker, media agency, telecom, EPC contractors, cooperative bank, digital lending, and account aggregator). Each preset carries: rate matrix by HSN or SAC, section-code map to the Income-tax Act 2025 taxonomy, GST composite-supply rules where relevant, ERP field mappings (SAP, Oracle Fusion, Tally, Zoho, MS Dynamics), bank narration parsers by acquiring bank, variance taxonomy layered on the shared root taxonomy, reconciliation cadence, and settlement flow. Configuration is versioned and audit-traced under Rule 3(1).
- **Output:** A multi-industry group runs one deployment of the reconciliation platform, loads one industry configuration per subsidiary, closes each subsidiary's books using rules native to its industry, and consolidates the whole group under Ind AS 108 with reconciling items expressed in a common variance taxonomy. The audit trail — every match, every classification, every re-run — is captured in a single edit-log format across all industries, meeting Rule 3(1) of the Companies (Accounts) Rules 2014. The 24-industry catalogue is extended as new configuration bundles rather than new codebases, and the engine version that runs the jeweller's close is the identical engine version that runs the hospital's close.

### Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies

Source: https://www.terra-insight.com/insights/opening-balance-reconciliation-india/

- **Problem:** Opening balance mismatches across bank, TDS receivable, and GST ITC ledgers signal unresolved prior-period errors — most commonly NACH credits received on the last working day, TDS wrongly booked in the wrong quarter (Form 26AS variance), or GST credit notes booked in March but appearing in April GSTR-2B. Left unresolved, they cascade into every subsequent reconciliation.
- **Logic:** Opening balance reconciliation runs a four-ledger cut-off check on the first day of every period: bank book opening equals prior-month bank statement closing adjusted for outstanding items; TDS receivable opening equals cumulative Form 26AS balance; GST ITC opening equals prior GSTR-3B Table 6B closing; cash-on-hand opening equals prior physical count. Variances are classified (timing, quarter-mismatch, cut-off error) and routed to a prior-period adjustment journal.
- **Config:** Four-ledger cut-off check (bank, TDS, GST, cash), Schedule III materiality threshold (typically ₹5 lakh), and prior-period-adjustment GL posting rules.
- **Output:** Opening balance sign-off per ledger, prior-period adjustment journal entries per Companies Act 2013 Schedule III, variance audit trail for each cause category, and Board-report-ready materiality disclosure.

### Oracle ERP Cloud (Fusion) for Auto-Component Manufacturers: Reconciliation Gaps to Address

Source: https://www.terra-insight.com/insights/oracle-erp-cloud-auto-component-reconciliation-gaps/

- **Problem:** Indian auto-component Tier-1 manufacturers on Oracle ERP Cloud (Fusion) get strong native support for Blanket Purchase Agreement, ASN inbound, three-way match through Cost Management, and the standard India localisation surface (GST, TDS / TCS including Income Tax Act 2025 codes 1001-1092, e-invoice, e-way bill). They still face five recurring reconciliation gaps that require 4-6 weeks of custom Oracle OTBI / DFF / OIC / concurrent-program development per gap: cum-quantity drift alerting, RMPV index linkage, ITC-04 multi-hop, Maruti e-Nagare / Tata SRM portal inbound, and programme-level cumulative tracking.
- **Logic:** Map Oracle Fusion's procurement and supply-chain modules against the 10 auto-component reconciliation streams, identify the five recurring gaps that fall outside native scope, document the Oracle-specific workaround pattern per gap (custom OTBI subject-area report for cum-drift, DFF + concurrent program for RMPV, custom build on top of Subcontracting for multi-hop ITC-04, OIC integration per OEM portal, custom OTBI roll-up for programme-level cumulative), and quantify the build effort plus ongoing maintenance burden per gap.
- **Config:** Oracle ERP Cloud (Fusion) install with Procurement Cloud, Order Management, Cost Management, Receiving, India Localisation enabled, Blanket Purchase Agreement document type configured for auto-component SA-equivalent supply, ASN inbound through Receiving Module, three-way match tolerances configured per OEM, descriptive flexfields on Blanket PO line for RMPV index basis and programme code, custom OTBI subject areas for cum-drift and programme-cumulative roll-up, Oracle Integration Cloud (OIC) flows per OEM portal (e-Nagare, TML SRM), concurrent programs for RMPV computation, Subcontracting module extended for multi-hop ITC-04.
- **Output:** An Oracle-native auto-component operating model with five quantified custom-build gaps, each carrying a 4-6 week development effort, ongoing OTBI / DFF / OIC maintenance burden across Oracle's quarterly patch cycle, total custom-development run-rate at a typical four-OEM Tier-1 at roughly ₹50-70 lakh per year, and the build-vs-buy boundary that drives the companion-product evaluation at OEM customer number three.

### Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover

Source: https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india/

- **Problem:** Oracle Fusion Cloud ERP's India Localization module handles TDS withholding and GST tax determination through release 24C but does not pull GSTR-2B JSON via GSTN API, does not match Form 26AS, and does not parse payment gateway settlement files from Razorpay, PayU, or Cashfree — forcing large Indian enterprises on Oracle Fusion to reconcile statutory and gateway data outside the ERP.
- **Logic:** Bolt an external reconciliation layer on top of Oracle Fusion via REST API pulls for AP invoices, GL journals, and bank statements, BI Publisher scheduled export to SFTP/UCM for bulk data, and FBDI inbound to write cleared-status updates back to Fusion. Ingest Form 26AS, GSTR-2B JSON, gateway settlement files externally and run multi-pass matching with tolerance bands, then clear items via FBDI.
- **Config:** Oracle Fusion connector with REST endpoints for AP_INVOICE_DISTRIBUTIONS_ALL, XLA_AE_LINES, GL_JE_LINES, JG_ZZ_* India tax tables, BI Publisher report templates scheduled via Enterprise Scheduler, FBDI import zip templates for cleared-status posting, and gateway adapter library for Razorpay, PayU, Cashfree.
- **Output:** A reconciled Oracle Fusion FI ledger with statutory (26AS, GSTR-2B) and gateway (Razorpay/PayU/Cashfree) variances all matched and cleared via FBDI writeback — no manual JSON uploads, TDS and ITC positions reliable at close, and audit trail surviving Oracle and statutory review.

### OTT and SaaS MDR Reconciliation Playbook for Indian Subscription Businesses

Source: https://www.terra-insight.com/insights/ott-saas-mdr-reconciliation-playbook-india/

- **Problem:** Indian OTT and SaaS subscription businesses processing several crore of monthly GMV through one or more payment aggregators routinely accept the settlement file as final and miss 0.10 to 0.20 percentage points of effective-rate leakage every month. The leakage sits in eight distinct cells — non-zero network MDR on zero-MDR instruments, premium cards in the wrong slab, domestic BINs charged international, Amex hidden in a blended rate, flat-rate concealment, refund and chargeback MDR retention, and recurring add-on or eNACH rejection fees stacked without contract basis. The CFO sees one blended monthly number, not the eight cells where leakage compounds.
- **Logic:** Run a seven-step monthly close. Ingest the per-transaction settlement export from each gateway keyed on settlement_id and payment_id. Classify every line by instrument, network, BIN tier, scope, and product flag. Compute per-network effective rate as fees divided by network volume. Compare each per-network effective rate to the contracted slab from the live merchant-agreement schedule, not the published headline. Run the eight-pattern leakage flag set against the per-transaction file. Build a dispute and recovery pack with rupee-quantified exposure and the contract or regulatory citation for each flagged transaction. Assemble a one-page board view that totals contracted rate, actual effective rate, basis-point gap, rupee gap, ninety-day trend, and dispute pipeline.
- **Config:** Per-gateway per-transaction settlement-file ingestion keyed on settlement_id and payment_id. Contracted-rate table by instrument and network refreshed at every contract update. BIN-to-network and BIN-to-tier mapping table. Eight-pattern leakage flag rule set with per-pattern detection logic. Refund and chargeback MDR retention register. Recurring-product add-on rule set with contract-basis check. GST 18 percent overlay on fee components only. Dispute pack template carrying transaction identifiers, rupee exposure, contract or regulatory citation, and gateway dispute window. Ninety-day rolling effective-rate trend store.
- **Output:** A monthly one-page CFO and board view with contracted blended rate, actual effective rate, basis-point gap, rupee gap, dispute pipeline, and ninety-day trend. A transaction-level exception list of the eight leakage patterns with rupee exposure per flagged transaction. A dispute pack handed to each gateway account manager for the in-window recoveries. A renegotiation brief for the quarterly contract review surfacing structural variance the dispute window cannot recover. A subscription unit-economics line for the management accounts that reconciles back to the settlement file.

### Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393

Source: https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india/

- **Problem:** Outdoor catering revenue in India does not match a dine-in restaurant's POS-and-bank pattern — it is B2B with credit terms, advance receipts, milestone billing, 18%-with-ITC GST, and customer-deducted TDS under Section 393(1) Sl. 6(i) payment codes 1023/1024, which makes a standard restaurant close model inapplicable.
- **Logic:** Match purchase order against event manifest, milestone invoices, and final tax invoice; reconcile advance receipts to GSTR-1 Table 11 and adjustments via Table 11A; net bank credit against invoice value minus customer-side TDS, then verify the deducted amount appears in Form 26AS within the same quarter.
- **Config:** Per-customer rate card, head-count tolerance band, milestone schedule (booking advance percent, pre-event percent, final reconciliation window), customer GSTIN and PAN map for TDS validation, and 18%-with-ITC routing for inputs against catering revenue.
- **Output:** A daily and per-event close that ties contracted PO value to bank receipts across milestones, surfaces advance-to-invoice gaps as Section 13 exposures, and produces a quarterly 26AS reconciliation pack against TDS deducted by corporate customers.

### Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface

Source: https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india/

- **Problem:** When an enterprise outsources GST compliance to a CA firm, liability still sits with the taxpayer but execution sits with the firm — and IMS (October 2024) adds 500–5,000 accept/reject decisions per enterprise per month that cannot be triaged without a shared reconciliation surface with clear handoff markers between firm and enterprise responsibility.
- **Logic:** Run a dual-access reconciliation workspace with role segregation for enterprise finance staff and CA firm team. Firm pulls GSTR-2B, IMS status, and e-way bill data from the GST portal using enterprise credentials; enterprise supplies the purchase register from Tally, SAP, or Zoho Books. Apply an agreed IMS decision rule-set (auto-accept trusted vendors above ₹10,000 monthly, auto-reject wrong-GSTIN invoices, flag the middle band for enterprise review). Every action attributed and timestamped.
- **Config:** Shared workspace per enterprise client with dual-party access, IMS decision rule-set configurable per client, handoff marker tags on every transaction (firm-owned vs enterprise-owned), and engagement-letter terms referenced in the deliverable pack.
- **Output:** An outsourced GST compliance cycle where the enterprise retains legal liability with clear evidence of the firm's professional work, IMS is fully triaged before GSTR-3B filing, DRC-01C surprises are eliminated, and audit trail satisfies both ICAI SA 230 and CGST Section 73/74 defence.

### Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals

Source: https://www.terra-insight.com/insights/over-leverage-detection-bank-statements/

- **Problem:** Standard FOIR calculations based on bureau data understate a borrower's true obligation burden because many Indian borrowers carry BNPL obligations, predatory app debts, and informal borrowing that do not appear in bureau pulls. Bank statements reveal all visible obligations through actual debit entries.
- **Logic:** Scan all outward transactions for EMI debit patterns (recurring debits to known lender names or with EMI narration strings), BNPL repayment patterns (recurring debits to known BNPL platforms), credit card minimum payment patterns, and debt consolidation signals (large inward credit followed by multiple outward transfers to lender accounts). Aggregate all visible obligations to compute statement-derived FOIR and compare with bureau-derived FOIR.
- **Config:** Enable for all NBFC and digital lending underwriting workflows. Update BNPL platform list quarterly. Cross-reference with predatory lending app detection for complete informal obligation coverage. Flag cases where statement FOIR exceeds bureau FOIR by more than 15 percentage points.
- **Output:** Over-leverage section in the credit report listing all detected EMI obligations by lender, BNPL recurring debits by platform, credit card payment patterns, and statement-derived FOIR versus the FOIR derived from declared obligations.

### OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions

Source: https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation/

- **Problem:** OYO operates revenue-share or minimum-guarantee contracts where OYO owns the customer relationship, sets rates, and applies SLA-based deductions — making the property's settlement file structurally different from a commission-only OTA payout, with the GST liability flowing to either OYO or the property depending on the contract structure under sub-brands like Townhouse, Capital O, or OYO Wizard.
- **Logic:** Per settlement cycle, classify each booking under the property's contract type (revenue-share, minimum-guarantee, hybrid), match to PMS folio, apply the contracted revenue-share split, compute minimum-guarantee top-up if applicable, layer in SLA-based deductions with reason codes, separate operational settlement from capex-recovery deductions on Townhouse or Capital O properties, and apply the GST treatment that matches the contract's supplier identification.
- **Config:** OYO settlement file connector with sub-brand and contract identifiers; PMS folio adapter; revenue-share split rule per property; minimum-guarantee floor per month; SLA deduction reason-code master; capex recovery schedule on Townhouse or Capital O contracts; GST supplier-identification rule per contract.
- **Output:** A reconciled OYO ledger where each cycle's payout is built up from revenue share or minimum guarantee, SLA deductions are itemised with reason codes for dispute, capex recovery is segregated, and the GST treatment matches the contract — supporting accurate revenue recognition under Ind AS 115.

### Paise-Exact Decimal Half-Up Rounding — The India Reconciliation Convention

Source: https://www.terra-insight.com/insights/paise-exact-decimal-round-half-up-india-reconciliation-convention/

- **Problem:** Indian audit convention rounds a fractional half-paise up on every rupee-and-paise computation — a rule every Indian CA learned in first-year articleship and carries into every audit of tax invoice tie-outs. Engineering convention, imported into most reconciliation software from the IEEE 754 banker's-rounding default, rounds a half to even. The two disagree by one paisa on every line where the exact half falls on an odd terminating digit, which for 9-percent CGST and 9-percent SGST computations is the majority of taxable values with three-decimal paise. On a thousand invoices in a month the drift is not one paisa but many rupees; on ten thousand invoices it can be a five-figure gap between the invoice book and the GSTR-1 filing. Add dual-Act TDS — where FY 2024-25 deductions still cite Income-tax Act 1961 sections and FY 2025-26 deductions cite Income-tax Act 2025 Section 393 payment codes — and reconciliation software that paraphrases either the rounding or the statute puts the year-end close at audit risk.
- **Logic:** Enforce Decimal arithmetic with half-up rounding as the single rounding policy end-to-end. Every rate application on a taxable value produces a Decimal with three or more paise decimals; the rounding step brings it to two decimals under the half-up convention; the CGST leg and the SGST leg on an intra-state supply are computed separately at the half-rate, each rounded up on the sub-paise half, so the invoice split is visibly symmetric per the CA convention. For TDS, resolve every deduction to the correct-period statute — an invoice dated within FY 2024-25 pins to the 1961 Act section number; an invoice dated within FY 2025-26 pins to the Income-tax Act 2025 Section 393(1) schedule entry with its payment code 1001 through 1092. The payment code, not just the rate, must appear in the TDS reconciliation output because Form 26AS and the challan tie-out require the code exactly.
- **Config:** Rounding policy is half-up rounding on all monetary computations at two-decimal paise precision. Money type is fixed-point Decimal; floating-point money is refused at the input boundary. Tax-computation ordering is (taxable value × rate) → round to paise, applied per leg (CGST and SGST separately for intra-state; IGST as a single leg for inter-state). Dual-Act TDS resolution keys on invoice date: on or after 1 April 2025 resolves to Income-tax Act 2025 Section 393(1) with the applicable Sl. number and payment code (1001 through 1092); before 1 April 2025 resolves to Income-tax Act 1961 with the legacy section number. Section 170 rupee rounding at the return-aggregate level is a separate step applied only at the GSTR-3B summarisation, never at the invoice line.
- **Output:** The reconciliation output states every rupee to the paise, every paise resolved under half-up rounding, every CGST/SGST leg equal on the split as the CA convention requires, every TDS entry pinned to its correct-period statute with its correct payment code. Auditors ticking the invoice book against the GSTR-1 filing find no per-line paise drift; auditors ticking Form 26AS against the TDS reconciliation find every deduction citing its statute and payment code with no paraphrase. The rupee-and-paise expression is reproducible byte-for-byte on a re-run of the same period — the audit trail required by Rule 3(1) proviso is preserved without commentary.

### Panipat Home Textile and Recycled Yarn Reconciliation

Source: https://www.terra-insight.com/insights/panipat-home-textile-recycled-yarn-reconciliation/

- **Problem:** A Panipat recycled-yarn mill supplying Welspun's US-export blanket and rug programs must reconcile CMLTA auction procurement of textile waste against a recycled-yarn output register, a 62 to 68 percent recovery ratio target, OEKO-TEX Standard 100 Class II certification validity for every dispatch, Section 43B(h) MSME 45-day payment discipline on the converter side, Section 194Q code 1031 TDS on the Welspun-buyer side, and e-invoicing IRN generation for every B2B invoice above the ₹5 crore aggregate-turnover threshold. Manual tracking loses the batch-level recovery ratio (letting bad waste lots eat margin invisibly), fails to catch expired OEKO-TEX certifications before dispatch (exposing the buyer to compliance disputes), and misses the 45-day MSME cascade for converter payments (disallowing the purchase cost as a deduction under the Income-tax Act until the year of actual payment).
- **Logic:** Build a waste procurement register keyed by CMLTA lot reference with weighbridge-slip weight, waste grade, bid price, and seller GSTIN and PAN with MSME registration flag. Ingest daily production register with input waste weight, output yarn weight, batch reference, blend composition, and yarn count. Compute batch-level recovery ratio and flag any batch below the 60 percent floor or above the 70 percent ceiling for physical inspection. Maintain OEKO-TEX Class II certification master with production site, product batch coverage, certification number, valid-from date, and valid-to date; block dispatch invoice generation for any batch outside the valid certification window. Ingest customer purchase orders with PO reference, yarn count, quantity, OEKO-TEX class requirement, and delivery schedule. Reconcile dispatch register against PO, invoice register against dispatch, and IRN register against invoice. Track converter-side payment ageing against Section 43B(h) 45-day cascade and Welspun-buyer-side TDS under Section 8 Sl. 8 code 1031 at 0.1 percent.
- **Config:** CMLTA and direct converter seller master with GSTIN, PAN, MSME registration flag (Udyam number), and default TDS payment code (1002 other resident or 1001 Individual/HUF for waste procurement service charges where applicable). Waste-grade master defining light cotton knits, heavy cotton wovens, mixed synthetics, hosiery clippings, and mill waste with expected recovery-ratio bands per grade. OEKO-TEX Class II certification master with production site, certification number, valid-from date, valid-to date, and covered product batches. Downstream buyer master (Welspun Anjar plant, Welspun Vapi plant, Trident Barnala, Himatsingka Hassan, plus regional Panipat blanket buyers) with GSTIN, PO template, payment terms, and Section 194Q code 1031 applicability. Yarn-count master defining count number, target blend composition, and default customer segments. Section 43B(h) alert thresholds at 30 and 40 days from goods acceptance to trigger payment escalation before the 45-day disallowance window.
- **Output:** A month-end recycled-yarn reconciliation pack: waste procurement register with lot-level weighbridge cross-check, recycled-yarn output register with batch-level recovery ratio and variance versus grade baseline, OEKO-TEX Class II certification validity register with expiry alerts, PO-to-dispatch-to-invoice-to-IRN-to-GSTR-2B reconciliation per Welspun and other buyer lot, Section 43B(h) ageing bucket for converter-side MSME payables at 30, 40, and 45-plus days, Section 194Q code 1031 TDS credit at the Panipat mill's PAN on Form 26AS cross-check against buyer-side deductions, and a certification-cost amortisation line item mapped to the yarn output volume for the certification period. The pack closes to the plant's cost accounting record and satisfies the Section 148 Companies Act cost audit for units above the ₹35 crore turnover threshold.

### Parag Milk Foods Mozzarella PLISFPI Claim Reconciliation

Source: https://www.terra-insight.com/insights/parag-milk-foods-mozzarella-plisfpi-claim-reconciliation/

- **Problem:** A Pune-headquartered dairy processor approved as a PLISFPI Segment 4 mozzarella beneficiary under the July 2024 DPIIT order must reconcile a mozzarella-only claim base for FY 2026-27 against an FY 2019-20 baseline, isolate the mozzarella SKU universe from the wider dairy portfolio, prove the 10:1 milk-to-cheese conversion yield through the vat sheet and dispatch register, and file the claim within seven months of FY-end on the Project Management Agency portal. The consolidated GSTR-1 HSN 0406 disclosure aggregates block cheese and processed cheese with mozzarella; the milk procurement pool feeds every cheese line and every liquid milk brand from the same pooling centres; and the B2B pizza-chain quick-service restaurant channel introduces Section 194Q TDS credit reconciliation on the receivable side. Missing the seven-month deadline forfeits the year's incentive; understating incremental sales leaves incentive on the table; over-stating incremental sales invites Project Management Agency audit and clawback.
- **Logic:** Isolate the mozzarella-only SKU universe using the SKU master with an FSSAI Regulation 2.1.3 mozzarella-compliance flag. Build a milk procurement register keyed by pooling centre with fat and SNF grade capture, and allocate the daily milk pool between mozzarella and non-mozzarella cheese lines by batch vat charge. Reconcile the finished-cheese dispatch register against the vat sheet at batch level, benchmarking the conversion ratio against the 10:1 mozzarella yield reference. Bridge the aggregate GSTR-1 HSN 0406 disclosure to mozzarella-only revenue by subtracting non-mozzarella cheese SKUs at line-item level. Reconcile B2B QSR receivable three ways — supplier GSTR-1, buyer 2B, Form 26AS TDS credit under Section 8 Sl. 8 code 1031. Reconstruct the FY 2019-20 base year from the audited annual report segment disclosure or the mozzarella sub-ledger where the base year predates a capacity ramp. Derive incremental sales, apply the branch-specific incentive rate, and lock the claim base for auditor sign-off before the seven-month filing deadline.
- **Config:** SKU master with FSSAI mozzarella-compliance flag, format (block / grated / cubed / shredded / IQF), pack size, HSN 0406 sub-classification; milk procurement register with pooling centre, quantity, fat and SNF grade, procurement price; vat sheet with batch ID, milk charged, rennet and culture, finished cheese weight, brine loss; finished-goods dispatch register with SKU, channel (pizza-chain QSR / HORECA / MT / GT), cold-chain temperature log reference; B2B receivable register with customer PAN, invoice value, Section 194Q TDS deducted (code 1031 at 0.1 percent), Form 26AS reconciliation status; FY 2019-20 mozzarella baseline reconstruction workpaper; branch-specific incentive rate table by scheme year; Project Management Agency audit evidence pack template with seven-month filing checklist.
- **Output:** A year-end PLISFPI Segment 4 mozzarella claim reconciliation pack: mozzarella-only revenue for the operational year (own-plant, FSSAI-compliant, cold-chain-verified); milk-to-cheese conversion yield against the 10:1 benchmark with batch-level variance flags; GSTR-1 HSN 0406 to mozzarella-only bridge; B2B QSR three-way receivable reconciliation with Form 26AS 194Q credit; FY 2019-20 base year workpaper; incremental sales calculation and applied incentive rate for the branch; the Project Management Agency audit evidence pack ready for portal submission within seven months of the eligible financial year-end.

### Partial Payment Reconciliation: How to Allocate and Match in Indian Finance

Source: https://www.terra-insight.com/insights/partial-payment-reconciliation-india/

- **Problem:** 35% or more of AR payments in Indian services businesses are partial: instalments, milestone withholds, retention amounts, or TDS-net payments mistaken for partials. Incorrect allocation across invoices leaves phantom open balances, stale ageing, and wrong bad-debt provisions.
- **Logic:** Apply remittance advice first, apply credit notes to invoice balance before any cash, then allocate the cash to specific invoices, posting TDS on the paid portion at the correct section rate. Maintain a running open balance per invoice and use FIFO or oldest-invoice rules when remittance detail is absent.
- **Config:** Remittance-advice ingestion, credit-note sequencing rule, FIFO allocation default, and per-invoice TDS posting linked to Form 26AS match.
- **Output:** Accurate invoice-level open balances, correct AR ageing, TDS receivable tied to each paid portion, and clean bad-debt provisioning based on genuine overdue balances.

### Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them

Source: https://www.terra-insight.com/insights/password-protected-bank-statement-india/

- **Problem:** Password-protected bank statement PDFs from Indian private sector banks cannot be parsed until the correct password is resolved, creating workflow failures when applicants cannot recall their password.
- **Logic:** A consent-based collection workflow captures the password from the applicant at submission; when that fails, a derived-candidate approach attempts publicly documented bank-specific password formats before returning a clean failure status.
- **Config:** The lender's application form must include a password field and a clear consent disclosure covering the underwriting purpose, with derived-candidate logic configured per bank in the parser.
- **Output:** Either a fully unlocked and parsed transaction table ready for analysis, or a documented failure status with guidance for the credit team to request a fresh statement from the applicant.

### Paytm Payment Gateway MDR Reconciliation for Indian Merchants

Source: https://www.terra-insight.com/insights/paytm-payment-gateway-mdr-reconciliation-india/

- **Problem:** Paytm Payment Gateway settles in a ~1.99–2% standard slab and a 3% premium slab and presents a single 'UPI' line in the settlement file that in practice mixes bank-account UPI (zero network MDR) with wallet-on-UPI (1.1% interchange above ₹2,000) and where applicable RuPay credit-on-UPI (~2% above ₹2,000). The wallet-on-UPI slice, the chargeback dispute fee, and the non-reversed MDR on refunds compound silently because per-instrument reconciliation is not in place.
- **Logic:** Reconciliation parses the Paytm PG settlement file by transaction identifier, joins to the order reference on the ERP/OMS side and to the NEFT credit narration and UTR on the bank side, and subdivides the 'UPI' rail line into bank-account UPI, wallet-on-UPI and credit-on-UPI sub-instruments using the rail attributes available in the row. Each sub-instrument is tested against its expected NPCI/RBI interchange band — zero for bank-account UPI, 1.1% above ₹2,000 for wallet-on-UPI, ~2% above ₹2,000 for RuPay credit-on-UPI — and any divergence is flagged. The premium 3% slab is reconciled per network so that Amex and Diners volume can be lifted out of the blended view. Chargeback dispute-fee adjustments and MDR retained on refunded transactions are tracked separately so they no longer hide inside the blended fee bucket.
- **Config:** Paytm PG settlement-file ingestion, per-instrument tagging rule that subdivides the 'UPI' line into bank-account UPI / wallet-on-UPI / RuPay credit-on-UPI, NPCI 1.1%-above-₹2,000 wallet-on-UPI verification rule, per-network effective-rate report (Amex, Diners, Visa, Mastercard, RuPay, UPI sub-instruments), chargeback dispute-fee tracker, MDR-on-refund non-reversal tracker, and GST-on-fee separate-line tracker.
- **Output:** Per-row MDR variance trail, a per-network effective-rate report that isolates wallet-on-UPI from bank-account UPI and Amex from the blended slab, a chargeback dispute-fee ledger reconciled against bank adjustments, a refund-MDR compounded-cost report, an audit-ready monthly MDR-versus-budget waterfall, and a clean separation of standard-slab and premium-slab volume that supports renegotiation conversations with Paytm.

### PayU MDR Reconciliation: Standard 2% + Premium Slab Handling for Indian Merchants

Source: https://www.terra-insight.com/insights/payu-mdr-reconciliation-india/

- **Problem:** PayU's settlement file shows a single 2% domestic line and a 3% premium line, but the premium line silently blends Amex, Diners, commercial cards, international cards and EMI, and the international volume sometimes lacks a separate forex line. A D2C or subscription merchant transitioning from sub-Rs 10 lakh published pricing to a negotiated custom rate above the threshold has no automatic way to know whether the post-negotiation effective rate reflects the contract, or whether residual premium-cell volume is being charged at pre-negotiation slabs.
- **Logic:** Reconciliation joins each PayU settlement_id to the bank nodal credit by UTR plus date plus net amount, then resolves every transaction to its instrument and issuer attributes from the card BIN. A per-network expected-rate model — 2% domestic on Cards, NetBanking, UPI and Wallet; 3% on Amex, Diners, international and EMI; the contracted custom rate for merchants above Rs 10 lakh per month — is compared against the actual fee in the settlement file. Variance above 0.15 percentage points on the effective blended rate triggers a per-network audit. Commercial-card BINs are isolated and confirmed against the merchant contract; international BINs are isolated and confirmed against the issuer-country attribute to flag any domestic-issuing BIN charged at the cross-border rate.
- **Config:** PayU settlement-file ingestion with the published column structure (Transaction ID, Merchant Reference, Payment Mode, Card Type, Card BIN, Issuer Country, Gross Amount, MDR Amount, GST on MDR, Net Settlement, Settlement UTR, Settlement Date), per-instrument expected-rate table loaded from the signed Merchant Service Agreement, commercial-card BIN whitelist, international-acceptance forex-line tracker, Section 393(1) Sl. 8(v) payment-code 1035 TDS column reconciling to Form 26AS, and GST on MDR reconciliation to GSTR-2B.
- **Output:** A monthly effective-rate report that separates each network's true cost from the blended quote, a commercial-card and international-card variance ledger flagging any transaction billed at a slab that does not match the contracted rate, a TDS reconciliation against Form 26AS for the operator deduction, an input-tax-credit claim file for the GST on MDR aligned to GSTR-2B, and a renegotiation pack for the next contract cycle when effective rate drifts above the contracted custom rate.

### PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts

Source: https://www.terra-insight.com/insights/payu-settlement-reconciliation/

- **Problem:** PayU nodal T+2 credits arrive as batched NEFT deposits blending card, UPI, debit, credit, and LazyPay BNPL transactions, each at different MDR rates (0% UPI, 0.4-0.9% debit, 1.5-2.5% credit, up to 3.5% international) plus 18% GST on MDR. Without instrument-wise unpacking, fee variances and ITC on MDR GST remain invisible.
- **Logic:** Matching joins the PayU settlement_id against the bank UTR plus date plus net amount, then resolves each transaction by Payment ID and Order ID to its instrument type, expected MDR, and GST on MDR. Rate-card comparison flags instrument-level over-deductions; LazyPay transactions are segregated for distinct accounting treatment.
- **Config:** Instrument-specific MDR rate table, LazyPay transaction classifier, PayU tax invoice matcher to GSTR-2B for ITC, and date-boundary alignment between Dashboard export and bank cycle.
- **Output:** Instrument-wise revenue and MDR schedule, MDR over-deduction recovery list, GSTR-2B-aligned ITC claim for MDR GST, and BNPL-isolated settlement ledger for LazyPay.

### PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity

Source: https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india/

- **Problem:** Lenders cannot detect altered bank statement PDFs through manual review at origination volumes — font differences of 0.5pt, invisible metadata layers, and row-level balance manipulations pass visual inspection every time
- **Logic:** Multi-layer forensic inspection during document ingestion: PDF metadata validation against banking-software signatures, font inventory consistency check, transaction-level balance chain recomputation, impossible-date flagging against 150+ RBI bank holidays 2019–2026
- **Config:** Runs on every submitted PDF automatically; known banking-software signature library (Finacle, T24, iText, Crystal Reports, BI Publisher); ATM-withdrawal threshold auto-adjusted for round-number clustering; produces per-document authenticity verdict with audit trail
- **Output:** Document-level authenticity verdict (clean / flagged / unknown) with specific findings listed, plus transaction-level flags for balance breaks and date anomalies — all with audit trail for each processed statement

### Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards

Source: https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india/

- **Problem:** PE investors demand month-close by day 5, board pack by day 10, monthly GSTR-2B match, quarterly Form 26AS reconciliation, and weekly cash reporting. Founder-led companies built for annual statutory audit cannot meet this cadence without restructuring the reconciliation process.
- **Logic:** Shift from monthly batch to continuous reconciliation: bank recon by day 2, platform settlements by day 3, AR and AP by day 4, GSTR-2B and TDS receivable by day 5. Produce a standing reconciliation pack (bank, AR, AP, TDS, ITC, settlement) that supports the board pack and the next-round due diligence file.
- **Config:** Continuous data ingestion, role-based SLAs tied to board calendar, and a pre-built reconciliation pack template that doubles as year-end audit evidence and next-round due diligence.
- **Output:** A 5-day close, board pack backed by signed reconciliation schedules, and a due diligence pack ready for the next funding round or secondary transaction without the usual 6-month cleanup.

### Peer Review Mandate by ICAI: Scope, Process, Reviewer Selection for CA Firms

Source: https://www.terra-insight.com/insights/peer-review-mandate-icai-india/

- **Problem:** ICAI's Peer Review Mandate determines which CA firms can sign listed-entity statutory audit reports — SEBI now requires a valid Peer Review Certificate as a precondition. Mid-tier firms moving from Phase I to Phase II coverage must operationalise the review for the first time: select files, host the reviewer, respond to observations, remediate within the response window, and renew every five years.
- **Logic:** The peer review evaluates two layers: the practice unit's overall quality control system under SQC 1 and the application of Standards on Auditing on a sample of completed engagement files. Reviewers are empanelled CAs assigned by the Board with independence safeguards. Findings are logged with materiality grading; the practice unit responds during the response window; the Board issues, refuses, or revokes the Peer Review Certificate based on the reviewer's final report.
- **Config:** Quality control manual aligned to SQC 1, engagement file template with mandatory SA documentation checklist, partner-and-staff rotation policy, file-selection memo identifying engagements likely to be reviewer-selected, response-window project plan for observation remediation, certificate renewal calendar five years out.
- **Output:** Peer Review Certificate enabling acceptance of listed and specified-entity statutory audit appointments, reviewer's observation log with closure status, remediated quality control system, and audit-trail evidence supporting Standards on Auditing compliance across the sample.

### Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering

Source: https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india/

- **Problem:** Indian EPC and engineering contractors typically run a portfolio of 15-40 active Performance Bank Guarantees (PBGs) across 10-30 customer contracts, totalling 5-10% of cumulative contract value, with each PBG valid through execution plus warranty (12-24 months from commissioning) and incurring 0.5-1% per annum bank commission billed quarterly with 18% GST; the PBG ledger must distinguish from retention (cash withheld by customer), track release triggers (commissioning, warranty expiry, no-claim certificate), handle extensions on programme delays with the extension cost mapped as pass-through or contractor absorbed, and reconcile monthly to the issuing-bank statement.
- **Logic:** Build a per-PBG register keyed on the contractor's internal PBG number with linked issuing-bank instrument number, beneficiary, contract reference, PBG value, validity start and end, release trigger and quarterly commission accrual; tie each PBG to the contract milestone tracker (order acceptance trigger for issuance, commissioning certificate or warranty expiry for release); maintain an expiry calendar with 60 / 30 / 7-day renewal alerts; for every BG commission debit on the bank statement, post the cost to finance expense and claim ITC under Section 16 of the CGST Act against the bank's tax invoice; on programme delay, raise an extension request 60 days before expiry and classify the extension cost as pass-through or contractor-borne; reconcile monthly against the issuing-bank statement for new issuances, releases and live PBGs.
- **Config:** PBG register with internal PBG number, bank instrument number, issuing bank, beneficiary, contract reference, PBG value, validity start / end, release trigger (commissioning / warranty / no-claim), quarterly commission rate; expiry calendar with renewal alert thresholds; bank statement BG commission ledger with GSTR-2B match for ITC; programme variance tracker driving extension requests; contract clause mapping classifying extension cost as pass-through or contractor cost; monthly two-way reconciliation against issuing-bank statement.
- **Output:** A monthly PBG close where the contractor's PBG register reconciles to the issuing-bank statement with new issuances, releases and live PBGs all matched; BG commission entries on bank statements tie to GSTR-2B and the ITC claim under Section 16; expiry calendar drives 60 / 30 / 7-day renewal alerts; release triggers on completed projects are actioned with the customer; extension costs are accrued as pass-through or contractor cost per contract clause; contingent liability disclosure ties to the PBG portfolio outstanding.

### Personal Care FMCG GST 2.0 Reconciliation (Soaps, Shampoos, Toothpaste)

Source: https://www.terra-insight.com/insights/personal-care-fmcg-gst-2-0-reconciliation/

- **Problem:** Indian personal care FMCG brands faced an overnight rate reset on 22 September 2025 when CBIC Notifications 09 to 16/2025-CTR moved soaps (HSN 3401), shampoos (HSN 3305), and toothpaste (HSN 3306) from 18 percent to 5 percent GST. The reconciliation pain sits in the straddle — pre-22-September dispatches already in distributor and retailer hands sold after the transition at the old MRP, in-stock MRP overprint requirements under Legal Metrology Rule 33, scheme reimbursements accrued at the old rate paid out at the new rate, and per-channel-tier credit-note treatment under Section 15(2) and Section 34. Without a transition-date discipline, the trade-spend GL is over- or under-stated, MRP-overprint compliance fails the consumer affairs audit, and the GSTR-1 amendment cycle mis-rates credit notes.
- **Logic:** Maintain three registers from end of business 21 September 2025 onward. The dispatch register stamps every outward supply with a transition-date flag (pre-22-September at 18 percent, post-22-September at 5 percent). The in-stock declaration register captures distributor and retailer opening inventory per SKU at the cut-over so downstream MRP-overprint compliance and channel-margin compression are quantifiable. The scheme matrix flags every active scheme for cross-over treatment so the accrual engine books at the underlying dispatch rate, not the rate at scheme issue. Section 15(2) per-scheme determination governs whether retro credit notes reduce taxable value; Section 34 governs the credit-note issue window. Cross-foot the trade-spend liability monthly and split the rate-segregated balances on every month-end close through 31 March 2026.
- **Config:** Scheme master with effective date range, percentage, Section 15(2) treatment flag (invoice-recorded, post-supply qualifying, non-qualifying), and cross-over flag where the scheme period spans 22 September 2025; dispatch register with invoice number, dispatch date, distributor GSTIN, SKU, HSN, MRP, dispatch rate (18 or 5); in-stock declaration by distributor by SKU at end of business 21 September; consumer scheme true-up matrix by SKU by distributor; Legal Metrology Rule 33 compliance record per SKU per overprint method; pre-22-September and post-22-September segregated accrual registers maintained in parallel through 31 March 2026; Section 393(1) Sl. 18 (legacy 194H) TDS rate at 5 percent for distributor commission flowing in cash.
- **Output:** A transition reconciliation pack split by pre-22-September and post-22-September flows: dispatch volumes by rate, in-stock decline against the channel-side baseline, scheme accrual and payout split by underlying-supply rate, credit-note register with effective rate per invoice, Legal Metrology overprint status by SKU, and a rate-segregated trade-spend liability cross-footed to the GL. Per-distributor MRP-overprint variance surfaces the in-stock recovery exposure; the cross-over scheme register feeds the GSTR-1 amendment cycle at the right rate; the eight-step transition checklist feeds the statutory audit pack with documentary evidence at 31 March 2026.

### Personal vs Business Transaction Separation in MSME Bank Statements

Source: https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme/

- **Problem:** MSME borrowers typically run personal and business transactions through one current account, making raw inflow totals an unreliable revenue indicator for credit underwriting.
- **Logic:** Transaction-level signals — UPI VPA structure, NACH mandate purpose codes, merchant category inference from narration patterns, recurring outbound payment counterparties — are used to classify each entry as personal or business before income analysis begins.
- **Config:** Classification rules are calibrated per account type (current vs savings), per business segment (trading, services, manufacturing), and per transaction channel (UPI, NEFT, IMPS, NACH, RTGS). Lenders can define additional exclusion rules for known personal transfer counterparties.
- **Output:** Separate personal and business transaction ledgers for the analysis period. Business inflow total and monthly trend used for synthetic P&L. Personal transaction log retained for affordability and obligation assessment.

### PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank

Source: https://www.terra-insight.com/insights/pf-ecr-reconciliation-india/

- **Problem:** PF ECR reconciliation spans three sources: ECR filing on the EPFO portal, the corresponding bank debit, and the PF expense ledger entry. Misapplied EPS ₹15,000 cap, multiple establishment codes, and look-alike challan amounts in the same period cause systematic mismatches and Section 7Q 12%-per-annum interest on late payment.
- **Logic:** Use the TRRN as the primary match key across EPFO portal, bank statement, and PF ledger. Validate the 8.33% EPS cap at ₹1,250 per employee above ₹15,000 basic and the 12% EPF employer share on the balance. Reconcile monthly before the 15th of the following month to avoid interest under Section 7Q.
- **Config:** TRRN-keyed matching across all three sources, establishment-code-level sub-ledger, EPS cap validation rule, and 15th-of-month deadline trigger.
- **Output:** A reconciled PF ledger tied to EPFO filings and bank debits, zero late-payment interest, clean employee-level contribution audit trail, and a documented sign-off pack for statutory and EPFO inspection.

### PF and ESI Statutory Payment Reconciliation: ECR Filing and Compliance for Indian Employers

Source: https://www.terra-insight.com/insights/pf-esi-statutory-payment-reconciliation-india/

- **Problem:** A 1,400-employee manufacturer files the ECR on time but discovers two business days later that the bank challan deposit failed, putting the contribution in default. Section 7Q interest at 12 percent per annum starts running, and inspection exposure under Section 14B widens with each day of delay.
- **Logic:** Reconcile three artefacts the same business day — payroll register, ECR file, and bank challan deposit confirmation — keyed on employee identifier for the per-row match and on month-total for the aggregate match. Any unmatched challan deposit triggers same-day re-initiation. Successful deposits close the cycle and update the statutory liability ledger.
- **Config:** Per-employee payroll register, ECR file in the EPFO and ESIC prescribed formats, bank challan reference master, contribution-share computation rules per current law, monthly cut-off enforcement (15th of following month), and a Section 7Q interest meter for any deposit that lands after cut-off.
- **Output:** Clean ECR-to-challan reconciliation closed before the cut-off, late-fee interest avoided, Section 14B damages exposure minimised, and a defensible statutory audit trail showing every employee's contribution from payroll register to EPFO and ESIC challan.

### Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing

Source: https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india/

- **Problem:** Pharma manufacturers must reconcile every batch against Schedule M (revised 2023) Good Manufacturing Practice batch-record requirements, finished-goods register, finished-goods packed register, dispatch register, distributor recall list, QR-code track-and-trace data for top 300 brands since 2023, CDSCO PvPI pharmacovigilance signals, batch recall recovery with bank receipt reversal, and Section 17(5)(h) ITC reversal on destroyed batches — all under phased Schedule M compliance running through December 2026.
- **Logic:** Maintain a batch master keyed by manufacturing licence and Schedule M batch record; tie every batch through BOM consumption to API and excipient lots; reconcile finished-goods register against packed register against dispatch register at batch level; integrate QR-code data feed where applicable for top 300 brands; cross-reference CDSCO PvPI signals at batch level; on recall, reconcile dispatch quantity against return-received quantity per distributor and per batch; reverse Section 17(5)(h) ITC on destroyed batch inputs.
- **Config:** Pharma batch configuration with manufacturing licence master, Schedule M revised-2023 compliance phase tag per site, batch record register with API lot and excipient lot traceability, finished-goods packed register, dispatch register per distributor, QR-code feed integration for top 300 brands, CDSCO PvPI signal capture per batch, recall workflow with bank receipt reversal, Section 17(5)(h) ITC reversal builder.
- **Output:** A monthly batch close where every Schedule M batch record reconciles to BOM-to-API trail, finished-goods register ties to packed register and dispatch register, QR-code data confirms top 300 brand dispatch quantities to retail, CDSCO PvPI signals cross-reference correctly to manufacturing batches, recall recovery is tracked per distributor with bank receipt reversal, and Section 17(5)(h) ITC reversal flows through GSTR-3B for destroyed batches without double-counting against returns reconciliation.

### Pharma Distributor and Stockist Reconciliation for Indian Pharmaceutical Manufacturers

Source: https://www.terra-insight.com/insights/pharma-distributor-stockist-reconciliation-india/

- **Problem:** Indian pharma manufacturers route 80-90% of sales through a CFA → super-stockist → retail chemist chain on consignment, with primary-vs-secondary sales gaps of 5-25% sitting as channel inventory, expiry returns split into saleable and non-saleable buckets, CFA service charges at 1.5-3.5% of dispatched value, Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) on CFA charges, and Section 34 GST credit notes on returns — five overlapping reconciliation rails that no generic ERP module handles together.
- **Logic:** Reconcile CFA stock-in (manufacturer dispatch) to stock-out (invoices to stockists) to closing stock (CFA monthly statement); match primary sales to secondary sales data from stockist uploads to surface channel inventory and parallel-trade leaks; split expiry returns into saleable (relabel and reissue) and non-saleable (destruction certificate filed) with both credit-noted under Section 34 inside the cut-off window; deduct Section 393(1) Sl. 6(i) contractor TDS on CFA service-charge invoices at 1% (code 1023) / 2% (code 1024) with thresholds; tie GST output reversal on returns to the stockist's GSTR-2B.
- **Config:** CFA master keyed by state, CDSCO licence number and GSTIN; stockist master with secondary-sales feed source (C&S, AIOCD AWACS, or distributor portal); product master with batch number, manufacturing date, expiry date and shelf-life policy; expiry-return taxonomy with saleable/non-saleable flag and destruction-certificate reference; CFA service-charge contract per state with percentage band and per-box handling; Section 393(1) Sl. 6(i) vendor rate matrix (code 1023 Ind/HUF, code 1024 other); Section 34 credit-note ageing ledger per dispatch lot.
- **Output:** A daily reconciled view per CFA showing dispatched value to invoiced value to closing stock with variance coded by reason; primary-vs-secondary gap per stockist aged month-over-month with channel-inventory days-on-hand; expiry-return register split saleable vs non-saleable with destruction-certificate status; CFA service-charge invoice approval gate validating base value and Section 393(1) Sl. 6(i) TDS deduction at code 1023/1024; Section 34 credit-note ageing per dispatch lot with cut-off countdown to the 30 November window.

### Pharma Expiry Returns Reconciliation: Saleable vs Non-Saleable Accounting

Source: https://www.terra-insight.com/insights/pharma-expiry-returns-saleable-non-saleable-india/

- **Problem:** Indian pharma manufacturers absorb 4-6% of secondary sales as expiry returns split between saleable (near-expiry repricing) and non-saleable (CDSCO-witnessed destruction under Schedule M GMP), each driving a different Section 34 CGST credit note timing, a different Rule 42 ITC reversal calculation, and a different Ind AS 36 impairment provision — with the Section 393 TDS overlay on every destruction-service invoice — across thousands of batches and dozens of stockists per month.
- **Logic:** Reconcile every return goods receipt at batch level against the original sales invoice, classify into saleable or non-saleable based on residual shelf life and CDSCO destruction trigger, issue the Section 34 credit note inside the 30-November-of-following-FY window for saleable returns reducing output GST, compute Rule 42 proportionate ITC reversal on consumed BoM inputs for destroyed batches reported in GSTR-3B Table 4(B)(2) in the destruction month, layer Ind AS 36 impairment progressively at 12/6/3 months from expiry against carrying inventory value, and deduct Section 393(1) Sl. 6(i) contractor TDS (code 1023 at 1% Ind/HUF, code 1024 at 2% other) on destruction-service vendor payments.
- **Config:** Batch master with manufacturing date, stamped expiry, original invoice reference and stockist code; return-goods-receipt taxonomy splitting saleable vs non-saleable with residual-shelf-life threshold; Section 34 credit note tracker with original-FY-plus-November-30 deadline alarm; Rule 42 reversal calculator using standard BoM cost × destroyed pack count × weighted input tax rate; Ind AS 36 provision matrix at 12/6/3 month bands; CDSCO destruction certificate register keyed by batch number; Section 393(1) Sl. 6(i) vendor rate matrix (code 1023 Ind/HUF, code 1024 other) for destruction agencies.
- **Output:** A monthly closed view per batch showing return quantity received, saleable-versus-non-saleable split, Section 34 credit note status (issued, reported in GSTR-1, deadline-clock), Rule 42 ITC reversal amount and GSTR-3B reporting line, Ind AS 36 provision booked by ageing band, CDSCO destruction certificate captured, and the Section 393(1) Sl. 6(i) contractor TDS challan tied to the destruction-vendor invoice by code 1023 or 1024.

### Pharmaceutical Distributor and Expired Stock Return Reconciliation

Source: https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india/

- **Problem:** Pharma manufacturers face distributor and expired-stock returns running 3-5% of annual sales, requiring reconciliation against the GST credit note mechanism under Section 34 of the CGST Act and Rule 53, ITC reversal under Section 17(5)(h) when stock is destroyed, insurance claim handling on damaged stock, CSR-donation tax treatment under Section 135 of the Companies Act, Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) TDS on distributor service fees, and the post-April-2024 GST amendment that caps credit note issuance at 30 November of the following FY.
- **Logic:** Hold a distributor-and-batch-level return register linked to the original sale invoice; classify each return as near-expiry / full-expiry / damaged / regulatory-recall / replacement; issue a Section 34 credit note within the post-April-2024 time-limit window; reverse ITC under Section 17(5)(h) on destroyed-stock inputs; reconcile insurance claim against the destruction event; tag CSR-donation stock with recipient 80G certification; deduct Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) on distributor service fees.
- **Config:** Returns configuration with distributor master tagged for return policy, SKU + batch traceability to original sale invoice, return reason codes (near-expiry, full-expiry, damaged, regulatory-recall, replacement), Section 34 credit note workflow with Rule 53 particulars, Section 17(5)(h) ITC reversal builder, insurance claim register, CSR donation tagger with 80G recipient master, Section 393(1) Sl. 6(i) flag on distributor service fees.
- **Output:** A monthly returns close where every return ties to its original sale invoice, credit notes issued within the Section 34 + post-April-2024 amendment window, ITC reversal under Section 17(5)(h) flows through GSTR-3B for destroyed-stock inputs, insurance claims reconcile to inventory destruction events without double-counting, CSR-donated stock is tagged for Section 80G compliance, and distributor service fees roll up under Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) challan.

### Pharma Export: Drawback + RoDTEP + Advance Authorisation Stacking

Source: https://www.terra-insight.com/insights/pharma-export-drawback-rodtep-reconciliation-formulations/

- **Problem:** A Tier-1 integrated pharma formulation exporter running the Ahmedabad plant network with a Q2 FY 2026-27 export book of an illustrative 3,200 shipments across 45 destination markets at approximately Rs 1,850 crore aggregate FOB value must reconcile three parallel DGFT export-incentive schemes at shipping-bill level — Duty Drawback under the AIR schedule (Chapter 30 rate typically 1.5 to 2.5 percent of FOB), RoDTEP under Appendix 4R (Chapter 30 rate typically 1.2 to 1.8 percent of FOB) and the Advance Authorisation Scheme under Chapter 4 of the Foreign Trade Policy 2023. Drawback and RoDTEP stack on the same shipping bill; Advance Authorisation is exclusive on the same input quantum and requires a non-availment declaration in the shipping bill where the finished product is manufactured from duty-free imported inputs. At the annual authorisation-close date, an Export Obligation Discharge Certificate (EODC) filing reconciles the SION-entitled duty-free import quantum with the actual export performance; any Export Obligation Lapse triggers full customs duty recovery plus interest on the un-utilised import quantum.
- **Logic:** Build a per-shipping-bill export incentive ledger keyed to the shipping bill number and the finished product HSN. For each shipping bill, capture: FOB value in shipment currency and INR equivalent at the shipping bill date exchange rate; the AIR drawback rate applicable to the HSN on the shipping bill date and the drawback amount credited by the Customs EDI system; the Appendix 4R RoDTEP rate applicable and the RoDTEP claim amount; the Advance Authorisation number (if any) against which the finished product is manufactured and the non-availment declaration flag in the shipping bill; the e-BRC realisation status, realisation date, realisation currency and INR-equivalent value; and the RoDTEP scrip issuance date and scrip value in the ICEGATE ledger. For each Advance Authorisation, maintain a running per-authorisation ledger of SION-entitled input quantum, actual imports made, actual exports performed and residual export obligation. At the authorisation validity end, generate the EODC reconciliation report showing the SION-mapped versus actual position and any Export Obligation Lapse quantum with the recoverable duty plus interest computation.
- **Config:** Shipping bill master with shipping bill number, port of loading, shipping date, destination country, buyer identifier, INCOTERM 2020 code, invoice currency and value, FOB INR equivalent at shipping bill date and finished product HSN at 8-digit granularity; per-HSN drawback rate register refreshed against each DGFT Public Notice with the effective date; per-HSN RoDTEP rate register refreshed against each Appendix 4R revision with the effective date; Advance Authorisation master with authorisation number, issue date, validity date, input SION mapping, duty-free import entitlement quantum and export obligation quantum; per-authorisation shipping bill linkage tagging every shipping bill for finished product manufactured from a specific authorisation; drawback and RoDTEP claim register per shipping bill; non-availment declaration flag per shipping bill; e-BRC status register with realisation date, currency and INR value; RoDTEP scrip issuance and utilisation register from ICEGATE; annual EODC reconciliation report generator with EOL computation and recoverable duty plus interest calculation.
- **Output:** A monthly export incentive close pack: per-shipping-bill drawback amount claimed and credited by Customs EDI, per-shipping-bill RoDTEP scrip amount claimed and issued on ICEGATE, per-shipping-bill Advance Authorisation linkage with non-availment declaration audit, e-BRC realisation status ageing (realised within 30 days, 30 to 90 days, 90 to 180 days, over 180 days per FEMA outstanding-realisation rules), and per-authorisation SION-mapped versus actual export progress. At authorisation-close date, an annual EODC reconciliation showing SION-entitled input quantum against actual export performance with any Export Obligation Lapse quantum, computed customs duty recovery and interest at the notified authorisation rate. The pack ties the export incentive INR flows to the shipping bill FOB base and to the Ind AS 21 realisation currency translation, so the P&L export incentive income line reconciles to the underlying shipping bill and the balance sheet export receivable reconciles to the realised e-BRC value.

### The 5/12/18 Input Mix: A Worked Refund Example for Pharma Formulations

Source: https://www.terra-insight.com/insights/pharma-inverted-duty-refund-input-mix-5-12-18-worked-example/

- **Problem:** A Tier-1 pharma formulator's Baddi plant produces approximately Rs 55 crore of Chapter 30 formulation output per month at 5 percent GST post the 22 September 2025 rate reset. Its input base is structurally rate-mixed at the 5/12/18 profile — active pharmaceutical ingredients under HSN Chapter 29 heading 2941 at 5 percent, glass vials under HSN 7010 at 18 percent, printed cartons under HSN 4819 at 12 percent, excipients under mixed Chapters 12 to 35 at 5 percent, and industrial solvents under HSN Chapter 27 at 18 percent held aside for the Notification 09/2022 carve-out. The monthly Form GST RFD-01 filing must decompose the eligible Net ITC by input HSN chapter, correctly exclude the input-services and capital-goods ITC per Notification 14/2022, hold the Chapter 27 solvent ITC as a distinct disclosure line, and apply the amended Rule 89(5) formula to arrive at a defensible maximum refund quantum.
- **Logic:** Build the plant's input register keyed to invoice-level HSN classification and rate tag. Compute per-line ITC as invoice value multiplied by the input rate. Tag each line with a Notification 09/2022 carve-out flag (Chapter 27 yes/no) and a Notification 14/2022 exclusion flag (input service or capital good yes/no). Aggregate the eligible-input ITC lines into the Net ITC pool decomposed by 4-digit HSN chapter — API leg (Chapter 29 heading 2941 and Chapter 30 heading 3003), glass vial leg (Chapter 70 heading 7010), printed carton leg (Chapter 48 heading 4819), excipient leg (mixed chapters 12 to 35). Hold the Chapter 27 solvent line aside on the conservative carve-out treatment; hold the input-services and capital-goods lines aside on the Notification 14/2022 exclusion. Apply the amended Rule 89(5) formula: Maximum Refund = (Turnover of inverted-rated × Net ITC / Adjusted Total Turnover) minus (Tax payable on inverted-rated × Net ITC / ITC availed on inputs and input services). Attach the Statement 1A invoice-level annexure with the Chapter 27 solvent disclosure line. File Form GST RFD-01 electronically on the GST portal within two years from the relevant date under Section 54.
- **Config:** Plant master with GSTIN, state, HSN Chapter 30 output sub-heading assignment (3003 bulk drug mixture or 3004 finished dosage form), and expected monthly outward supply band. Input HSN register with per-vendor per-invoice HSN classification anchored to Chapter 29 (2941 antibiotics as APIs), Chapter 70 (7010 glass containers), Chapter 48 (4819 printed cartons), Chapter 27 (industrial solvents), and excipient chapters 12, 17, 25, 28, 29, 32, 33, 34, 35, 38. Rate tag per line. Notification 09/2022 carve-out flag (Chapter 27 yes/no). Notification 14/2022 exclusion flag (input service or capital good yes/no). Net ITC composition register keyed to 4-digit HSN. Rule 89(5) refund workbook per plant per tax period with the amended-formula computation. Statement 1A invoice-level annexure builder with Chapter 27 solvent disclosure line. Form GST RFD-01 electronic filing feed. Treasury projection against Form GST RFD-04 provisional receipt within seven days and Form GST RFD-06 final sanction post-scrutiny.
- **Output:** A monthly refund pack per plant per state GSTIN: aggregate outward supply value at 5 percent Chapter 30; Net ITC composition table decomposed by input HSN chapter with per-line HSN, rate, invoice value and ITC quantum; Chapter 27 solvent line disclosed as a distinct row on the conservative carve-out treatment; input-services and capital-goods ledger aggregated separately and identified as excluded from the Net ITC numerator; amended Rule 89(5) formula application with both base-case (solvent included) and defence-case (solvent excluded) maximum refund quantum; Statement 1A invoice-level annexure; and Form GST RFD-01 draft ready for portal submission. Rolling treasury projection maps each filed RFD-01 to its expected RFD-04 provisional receipt and RFD-06 final sanction timing so the finance team can size the working-capital gap between accrued refund and cash receipt.

### Pharma Inventory Rate-Switch: Reconciling 12% Stock Sold at 5%

Source: https://www.terra-insight.com/insights/pharma-inventory-gst-rate-switch-22-september-2025-reconciliation/

- **Problem:** A large formulator's central depot in Mumbai carrying pre-22-September-2025 stock at 12 percent input GST on landed cost, selling the same stock post-cutover at the new 5 percent output GST, must reconcile a depot-wise SKU-level stock-in-trade ITC ledger against a post-cutover output-invoice register at the new 5 percent rate. Section 15 valuation on ongoing bonus schemes and trade discounts must be split cleanly at the rate change date. The depot must document on the audit record that no Rule 42 or Rule 43 common-credit reversal is required because the pre-cutover ITC was validly claimed on 12 percent input at receipt and Section 16 does not reverse credit for a prospective output rate change. Manual reconciliation across a national depot network with 30-plus branches loses the batch-level ITC provenance, aggregates scheme accruals into blended credit notes at a single rate (which breaches Section 34), and mis-attributes the one-time inventory-rollover margin cushion to routine trading margin.
- **Logic:** Freeze the opening stock ledger at end-of-day 21 September 2025 at the SKU by depot by receipt-batch level, keyed on the ITC claim date, the input rate at receipt, and the landed cost per unit. Ingest every post-cutover outward invoice against that stock and compute output GST at 5 percent under Section 15. Tie the closing stock quantity to the opening stock minus outbound plus fresh receipts and reconcile the ITC ledger against GSTR-3B at the GSTIN level — no reversal accrues against pre-cutover stock because Section 16 does not disturb validly claimed credit. Split every ongoing scheme accrual and post-supply discount into two rate buckets — pre-cutover invoices attract 12 percent credit notes under Section 34, post-cutover invoices attract 5 percent credit notes. Classify each scheme against Section 15(1), Section 15(2), or Section 15(3) — pre-agreement invoice-linked schemes qualify for Section 15(3) exclusion from GST base, volume-linked incentives without pre-agreement invoice link stay outside Section 15 and are treated as financial adjustments. Compute the working-capital position from the electronic credit ledger — the 7-percentage-point differential between 12 percent input and 5 percent output on rolling pre-cutover stock accrues to the ledger for a defined transition window until pre-cutover stock is exhausted.
- **Config:** Depot master with depot code, GSTIN, address, and warehouse type (central versus branch versus consignment); SKU master with HSN (3003 for bulk drugs, 3004 for formulations, 9018 to 9022 for medical devices), pack size, unit landed cost, and rate applicable at receipt; receipt-batch master keyed on GRN date, ITC claim date, input rate (12 percent pre-22 September 2025, 5 percent post), landed cost per unit, and quantity received; outward invoice register at the invoice-line level with SKU, quantity, transaction value, output GST rate, and — for scheme-linked lines — the reference to the underlying scheme master and the pre-agreement invoice link; scheme master keyed to scheme type (bonus quantity, trade discount, volume rebate), pre-agreement date, and Section 15 classification; credit-note register keyed to the original invoice reference so the credit-note rate always ties to the invoice rate; GSTR-1 and GSTR-3B feed for reconciling output tax remittance against the invoice register and input tax credit against the receipt-batch register; Section 54(3) refund workbook feed for ongoing inverted-duty refund cycles on packaging inputs and capital goods.
- **Output:** A cutover-date reconciliation pack — opening stock as at 21 September 2025 by SKU by depot by receipt batch with associated 12 percent input ITC crystallised in the electronic credit ledger; a rolling post-cutover stock consumption schedule mapping outbound quantities to pre-cutover receipt batches on a FIFO or weighted-average basis; a monthly output-invoice register at 5 percent GST with Section 15 valuation tie-back per invoice line; a scheme-linked credit-note register split into 12 percent (pre-cutover invoice) and 5 percent (post-cutover invoice) buckets under Section 34; a Section 15 classification schedule for each active scheme; a working-capital variance line showing the 7-percentage-point rollover cushion accruing to the electronic credit ledger during the transition window; and — for the audit file — a documented position note establishing that Rule 42 and Rule 43 are not engaged because the output supply remains taxable under HSN 3004 at the reduced 5 percent rate.

### Rule 45 Material Movement: ITC-04 for Pharma Loan-Licensees

Source: https://www.terra-insight.com/insights/pharma-job-work-material-movement-rule-45-itc-04-quarterly-return/

- **Problem:** A Mumbai-registered pharma brand-owner running a Chapter 29 antibiotic loan-licensee network across Baddi in Himachal Pradesh, Silvassa in the Dadra and Nagar Haveli UT, and Sikkim must maintain a Rule 45 CGST per-challan material movement register on every API dispatch, file Form GST ITC-04 quarterly by the 25th of the month following quarter-end populating Tables 4 (dispatch to job-worker), 5A (goods received back from the same job-worker), 5B (goods received back from another job-worker), and 6 (goods deemed as supply under Rule 45(4)), and monitor the Section 143 one-year return window per input to avoid the Rule 45(4) deemed-supply plus 18 percent interest exposure. A Q1 FY 2026-27 aggregate of 148 challans covering Rs 22.4 crore of API value across the three loan-licensees, with 142 challans (Rs 21.6 crore) returned and 6 challans (Rs 0.8 crore) pending at quarter-end and approaching 9-month age, is the operating scale where the reconciliation between the challan register, the ITC-04 portal filing, the loan-licensee's HSN 9988 IGST-12-percent job-work service invoice, and the aging monitor becomes a standing quarterly control that determines whether the brand-owner enters Q2 clean or with a live deemed-supply provision on the year-end books.
- **Logic:** Build a Rule 45 challan movement register keyed on the dispatch challan number, with each row carrying the dispatch date, destination job-worker GSTIN, HSN code, quantity, taxable value, expected return date (dispatch date plus one year), actual return challan number and date, and current status (in-transit, at job-worker, returned, deemed-supply). Ingest the daily dispatch feed from the brand-owner's ERP (SAP FI material ledger, Oracle Fusion inventory issue, or equivalent). Ingest the return challans from the loan-licensee (typically shared via portal or email at the end of each processing cycle) and match to the original dispatch challan by cross-reference. Run a proactive aging monitor on the register with escalation triggers at 9-month, 10-month and 11-month ages so pending returns can be pursued (or the Rule 45(4) deemed-supply liability provisioned and paid) before the 12-month deadline. Aggregate the quarter's dispatch challans into Table 4 of Form GST ITC-04, the quarter's return challans into Table 5A (same job-worker return) or Table 5B (different job-worker return, where the inter-job-worker transfer scenario applies), and any challans that crossed the 12-month deadline during the quarter into Table 6 (deemed supply with the taxable value and GST liability computed). File Form GST ITC-04 on the GST portal by the 25th of the month following quarter-end. Reconcile the ITC-04 portal-acknowledged summary against the internal challan register aggregated for the quarter. Match the loan-licensee's HSN 9988 IGST-12-percent job-work service invoice to the brand-owner's GSTR-2B and book the ITC on the input-service leg. At year-end, the aggregate deemed-supply exposure position, the total ITC on job-work service invoices, and the standing pending-challan aging trend are reported to the Section 65 audit-readiness pack.
- **Config:** Loan-licensee master with GSTIN per third-party manufacturer premises, state code (Himachal Pradesh, Dadra and Nagar Haveli UT, Sikkim, etc.), and additional-place-of-business declaration status for any inter-job-worker transfer scenarios; HSN and material master keyed to Chapter 29 antibiotic APIs and Chapter 30 bulk drug preparations; Rule 45 challan template with all Rule 55 mandatory fields (challan number, date, consigner/consignee GSTIN, HSN, description, quantity, taxable value, tax rate, place of supply for interstate movement); dispatch feed from the brand-owner's ERP (SAP FI material issue, Oracle Fusion inventory issue, Tally material out); return-challan intake from the loan-licensee; 12-month aging monitor with configurable escalation triggers (default at 9, 10, 11 months); Form GST ITC-04 filing template with Tables 4, 5A, 5B and 6 aggregation logic; portal-vs-books tie-out step after each quarterly ITC-04 filing; loan-licensee HSN 9988 IGST-12-percent job-work service invoice match against GSTR-2B; Rule 45(4) deemed-supply computation engine with the taxable value, applicable GST rate, and Section 50 interest-at-18-percent-per-annum calculation from the original dispatch date.
- **Output:** A rolling Rule 45 material movement dashboard per loan-licensee showing: (1) the quarter's dispatch position — challan count, aggregate value, HSN breakdown; (2) the quarter's return position — return-challan count, aggregate value, matched to originating dispatch challan; (3) the pending-return aging bucket — 0-3 months, 3-6 months, 6-9 months, 9-11 months, 11-12 months, over 12 months (deemed supply); (4) the ITC-04 quarterly return draft with Tables 4, 5A, 5B and 6 populated and ready for GST portal submission by the 25th of the month following quarter-end; (5) the ITC-04 portal-vs-books tie-out log showing any variance for correction; (6) the loan-licensee job-work service invoice match log to the brand-owner's GSTR-2B with ITC posting; (7) the Rule 45(4) deemed-supply exposure report on any input that has crossed the 12-month window with the GST liability and Section 50 interest quantified; (8) at year-end, the aggregate Section 143 job-work compliance summary for the Section 65 GST audit-readiness pack.

### Pharma R&D Tax Incentive: Section 35(2AB) Weighted Deduction and DSIR Recognition

Source: https://www.terra-insight.com/insights/pharma-r-and-d-tax-incentive-section-35-2ab-india/

- **Problem:** Indian pharma companies claim Section 35(2AB) deduction on in-house R&D — historically a 150% weighted deduction, sunset to 100% from FY 2020-21 onward — and must reconcile every rupee of claimed spend against DSIR Form 3CK recognition, audited Form 3CLA filing, and Form 3CL quantification, with strict carve-outs for land, building, marketed-product clinical trials, and out-of-facility research. Variance between the company's claim and DSIR's quantification typically runs 8-15%, and the assessing officer accepts only the Form 3CL number at scrutiny.
- **Logic:** Reconcile R&D cost-centre GL lines into four buckets (eligible capex, eligible revenue, ineligible-carve-out, out-of-scope), tie every fixed-asset addition to the R&D facility registration number, match every vendor invoice to a work-completion certificate from the recognised facility head, file Form 3CLA with the statutory auditor's certificate by 31 October, and book the income-tax return claim equal to the Form 3CL quantified number — not the company's own claim. Withholding on R&D vendor payments runs in parallel under Section 393/395 payment codes, separate from the 35(2AB) computation.
- **Config:** DSIR registration number on the R&D facility master, R&D cost-centre taxonomy with eligibility flag per centre, vendor master tagged for CRO vs scientific-consultancy vs equipment-AMC with the matching TDS code, fixed-asset register filter for R&D scientific equipment with land/building exclusion, Form 3CLA worksheet template (capex schedule + revenue schedule + auditor sign-off section), Form 3CL variance log per assessment year, cross-era legacy-section cross-reference for pre-FY26 transactions, TDS code map (1002 contractor, 1003 professional, 1052 non-resident).
- **Output:** An annual Form 3CLA-ready schedule showing eligible capex by asset class with FAR linkage, eligible revenue spend by cost centre with vendor-invoice and work-completion-certificate references, ineligible spend logged for transparency, Form 3CL variance closed within the year, monthly TDS challan on R&D vendor payments under codes 1002/1003/1052 reconciled to 26AS, and a cross-era cross-reference report tying pre-FY26 legacy-section transactions to the new payment-code regime.

### Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing

Source: https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india/

- **Problem:** Pharma manufacturers in India operate under NPPA / DPCO 2013 ceiling prices for scheduled drugs, PLI Pharma incremental-sales incentives across three product categories, Schedule M GMP batch-level traceability requirements, an R&D AP stream that must be ring-fenced from production AP for Section 35(2AB), formulation vs API segment accounting, expired and near-expiry stock buyback returns, GST complexities around online pharmacy aggregators under Section 9(5), and Section 393 TDS on API procurement and technical fees — each requiring its own reconciliation rail.
- **Logic:** Tag every SKU as scheduled or non-scheduled at master setup with the active NPPA ceiling price; build a parallel PLI claim ledger keyed to eligible HSN / product code with base-year benchmark; enforce batch-level BOM-to-invoice trail at GRN under Schedule M; ring-fence R&D AP via a separate cost centre with DSIR tagging; run formulation and API as distinct segments with intercompany pricing controls; reconcile expired-stock returns to original sale invoice; treat Section 9(5) online pharmacy aggregator sales as e-commerce supplies; map Section 393(1) Sl. 6(iii) / Sl. 8(ii) / Sl. 6(i) TDS deductions to per-vendor counters with monthly challan reconciliation.
- **Config:** Pharma configuration with NPPA scheduled-drug master, PLI Pharma category tags (Cat 1/2/3), Schedule M batch-trace flag on every BOM line, R&D cost centre and DSIR approval flag, formulation vs API segment code, expired-stock return reason codes (near-expiry, full-expiry, regulatory recall), Section 9(5) e-commerce aggregator flag on customer master, Section 393 TDS code map per vendor type, distributor and stockist margin slab per scheduled SKU.
- **Output:** A monthly pharma close where scheduled SKU invoices stay within the NPPA ceiling backed by margin calculation; the PLI Pharma annual claim file ties to invoice-level eligible sales; every batch QC release ties to its BOM-to-invoice trail under Schedule M; R&D AP rolls up cleanly into the Section 35(2AB) weighted deduction claim; formulation and API segment P&Ls reconcile to a consolidated trial balance; expired-stock returns tie to original sale invoice with proportionate ITC reversal; Section 9(5) e-commerce supplies are tagged for aggregator GST treatment; Section 393 TDS deductions tie to monthly challans and quarterly returns.

### Pharmacy Stockist Reconciliation for Indian Pharma Distribution

Source: https://www.terra-insight.com/insights/pharmacy-stockist-reconciliation-india/

- **Problem:** Pharma stockist reconciliation must close batch-level expiry returns, MRP-vs-PTR margin slips from mid-quarter trade schemes, Schedule H/H1/X custody logs, and a Section 9(5) GST split between marketplace-fulfilled and stockist-fulfilled orders, while honouring Rule 86B cash floor and Section 393 commission TDS.
- **Logic:** Ingest CFA dispatch advice, secondary sales DMS feed, expiry-return register, manufacturer credit notes, and marketplace settlement MIS. Key every line to batch number and original PTS. Classify variance as scheme-adjusted credit note, breakage allowance, ITC reversal on expiry, MRP-PTR margin slip, or 9(5) supplier-of-record mismatch.
- **Config:** 3-month vs 6-month expiry windows by channel, breakage allowance 0.5-2%, Section 393 commission TDS 2% with code 1001, Rule 86B 1% cash floor at ₹50L monthly turnover, Section 9(5) ecom GST split, Schedule H/H1/X chain-of-custody.
- **Output:** Batch-level closing stock with weighted-average PTS, expiry-return claim ledger with manufacturer credit note matching, MRP-PTR margin slip register by SKU, GST 9(5) supplier-of-record reconciliation, 26AS TDS reconciliation for commission payouts.

### PhonePe Payment Gateway MDR Reconciliation: The "Free" Promo and the Standard Plan

Source: https://www.terra-insight.com/insights/phonepe-pg-mdr-reconciliation-india/

- **Problem:** PhonePe Payment Gateway publishes a single blended Standard Plan number (1.95%, currently shown as 'Free*' under a limited-time launch offer) and routes per-instrument pricing through a Business Dashboard quote rather than a public rate card. Finance teams therefore lack the slab table needed to verify each settlement line, and lack a documented revert-to-standard trigger for the day the promo ends — both gaps are silent.
- **Logic:** Reconciliation parses the PhonePe PG settlement file by transaction ID, joins to the OMS order, and tests each row against three reference rates simultaneously — the promo rate currently in effect, the Standard Plan 1.95% revert baseline, and the per-instrument slab supplied by the Business Dashboard quote — flagging any row where the deducted fee diverges from the rate band for that instrument. A parallel rule isolates direct-collect PhonePe UPI inflows (zero network MDR, no PhonePe PG settlement file) from PhonePe PG net settlements so the two rails are never co-mingled in the GL.
- **Config:** PhonePe PG settlement-file ingestion, three-rate verification model (promo rate + Standard Plan revert + per-instrument slab from Business Dashboard quote), wallet/PPI-on-UPI 1.1%-above-₹2,000 rule, dual-rail isolation rule (PhonePe PG net settlements vs direct-collect PhonePe UPI), promo-end-date alert, and GST-on-fee separate-line tracker.
- **Output:** Per-row MDR variance trail, a flagged exception list for any settlement line outside the contracted rate band, a clean monthly MDR-versus-budget waterfall, an audit-ready promo-expiry alert, and a separated PhonePe UPI direct-collect ledger that no longer corrupts gateway settlement reconciliation.

### Pine Labs POS MDR Reconciliation: Terminal-Level Settlement and Multi-Outlet Audit

Source: https://www.terra-insight.com/insights/pine-labs-pos-mdr-reconciliation-india/

- **Problem:** Pine Labs settles per terminal per day to a per-outlet nodal credit, and a multi-outlet operator sees as many settlement batches as it has outlets — every batch a separate reconciliation surface that finance teams typically aggregate before checking the per-network slab. A single terminal billing RuPay debit at 0.90 percent against a zero-MDR mandate, or a Visa debit slab pinned one basis point above the RBI 0.90 percent cap, sits invisible inside the consolidated P&L until a terminal-by-terminal audit is run.
- **Logic:** Reconciliation explodes the consolidated Pine Labs MIS into TID-level rows, joins each TID per-day batch to its outlet's nodal bank credit on settlement UTR plus date plus net amount, and resolves every transaction to its network and card-type slab from Card Network and Card BIN. A per-network expected-rate model is applied per terminal: RuPay debit at 0 percent network MDR; Visa and Mastercard debit at the RBI cap (0.40 percent small merchant with Rs 200 per-transaction cap, 0.90 percent large merchant with Rs 1,000 per-transaction cap) or the contracted rate where lower; Visa and Mastercard credit at the contracted slab in the 1.4 to 2.5 percent band; American Express and Diners at the 3 percent premium slab; commercial and corporate cards at the contracted premium slab. Variance per terminal is annualised and ranked, surfacing the mis-configured terminals first.
- **Config:** Pine Labs terminal MIS ingestion with the per-terminal column structure (Terminal ID, Transaction Date, Card Number masked, Card Type, Card Network, Card BIN, Gross Amount, MDR Amount, GST on MDR, Net Settlement), per-terminal per-network expected-rate table loaded from the Merchant Service Agreement and the RBI 2017 circular caps, RuPay debit zero-MDR guard, commercial-card BIN whitelist, terminal rental and AMC line tracked separately from the MDR line, chargeback dispute fee tracker, GST on MDR reconciliation to GSTR-2B.
- **Output:** A per-outlet and per-terminal monthly variance report ranking terminals by annualised leakage, an RBI-cap compliance check that flags any non-RuPay debit slab above 0.40 percent or 0.90 percent, a zero-MDR check that flags any non-zero network MDR on RuPay debit, a commercial-card volume tracker per outlet, an input-tax-credit claim file for the GST on MDR aligned to GSTR-2B, and a renegotiation pack for the next acquirer contract cycle when terminal-level variance crosses the contracted blended rate.

### Plastic Injection Moulding Reconciliation for Auto Components: Material, Tooling and OEM-Owned Moulds

Source: https://www.terra-insight.com/insights/plastic-injection-moulding-reconciliation-auto-india/

- **Problem:** An Indian plastic injection moulding supplier produces auto interior, bumper, under-hood and connector components from four resin families (ABS, PP/TPO, PA66+GF, PC/ABS) on a mix of OEM-owned moulds (capitalised on OEM books, held at supplier premises) and supplier-owned moulds (capitalised on supplier books under Ind AS 16). Reconciliation must close cycle-time piece-rate conversion billing against contracted machine-rate per hour and contracted cycle time per mould, run index-linked RMPV claims on virgin resin consumption with regrind blending discipline, post mould-cycle amortisation on supplier-owned moulds, raise periodic tooling-maintenance back-charges and approved refurbishment invoices on OEM-owned moulds, and apply 18 percent GST on the conversion service under HSN 9988 plus resin GST per chapter heading.
- **Logic:** Maintain per-mould master with ownership flag (OEM versus supplier), contracted cycle time, machine-rate per hour, regrind-blend percentage per part, mould-cycle counter and expected mould-cycle life. Per shift per mould, log machine cycles, dispatched piece count, resin consumed (virgin and regrind), and actual cycle-time. Close the resin-to-piece identity per shift; flag actual-versus-contracted cycle drift; run RMPV claim on virgin resin equivalent against the contracted index reference. On supplier-owned moulds, post Ind AS 16 amortisation per cycle. On OEM-owned moulds, run the tooling-maintenance back-charge cadence and surface refurbishment triggers. Bill the conversion invoice at piece-rate × dispatched piece count with 18 percent GST under HSN 9988.
- **Config:** Per-mould master with ownership flag, cycle-time spec, machine-rate, regrind-blend percentage per part, cycle-counter and life expectancy; resin-family master with index reference (crude / butadiene / styrene / caprolactam / bisphenol A) per family; per-machine master with tonnage class and machine-rate matrix; OEM-owned mould stewardship register with tooling-maintenance back-charge cadence; refurbishment-trigger master per mould-cycle threshold; RMPV index master with monthly publication dates and contractual reference.
- **Output:** A monthly moulding reconciliation statement closing resin-to-piece identity per mould per shift; cycle-time drift dashboard flagging contracted-versus-actual variance per mould; RMPV claim register per resin family with virgin-equivalent computation and regrind credit; supplier-owned mould amortisation per Ind AS 16 with cycle-counter trigger; OEM-owned mould tooling-maintenance back-charge register and refurbishment-trigger queue; conversion invoice register with HSN 9988 at 18 percent GST and dispatched-piece-count audit trail.

### Platform Fee Leakage on Razorpay, PayU, Cashfree: A D2C Audit Playbook

Source: https://www.terra-insight.com/insights/platform-fee-leakage-razorpay-payu-india/

- **Problem:** Indian D2C and B2C businesses processing thirty thousand to two lakh monthly transactions across Razorpay, PayU, Cashfree, and cross-border Stripe absorb 0.05% to 0.25% of monthly volume in fee leakage because the aggregated settlement layer hides MDR slippage, instrument-mix repricing, GST-on-MDR alignment errors, undisclosed convenience and chargeback fees, paise-truncation in the aggregator's favour, and currency-conversion margin on cross-border. Without per-transaction fee-column reconciliation against the contracted rate sheet, the variance is closed every day as 'fee adjustment' and the recovery window expires unused.
- **Logic:** Pull per-transaction settlement files daily by payment aggregator and channel. For every transaction, compute expected fee as contracted rate by instrument slab times gross. Compare to actual fee column. Surface variances by instrument, by day, by month. Aggregate month-on-month instrument-mix drift to detect repricing. Reconcile aggregator monthly tax invoice against per-transaction GST totals. For cross-border, compute expected currency conversion spread against published RBI reference rate and surface margin variance. File chargeback or rate-correction claims within platform dispute window.
- **Config:** Per-transaction settlement file pipeline by aggregator. Contracted rate-sheet table by instrument slab and payment channel. Fee-column reconciliation engine with PAN-merchant, transaction-id, instrument-slab, gross, expected-fee, actual-fee fields. Month-on-month instrument-mix drift detector with two-percentage-point threshold. GST-on-MDR ITC alignment workflow against aggregator monthly tax invoice. Cross-border FX spread calculator versus RBI reference rate. Chargeback dispute filer with 60-90 day window tracker. Recovery register feeding Discovered Money on fee-deduction class.
- **Output:** A daily fee-leakage dashboard by aggregator with rupees recoverable, dispute window, and recovery probability. A monthly instrument-mix drift report flagging repricing candidates. A monthly GST-ITC alignment report. A quarterly fee-leakage trend by aggregator for contract review preparation. A standing chargeback register tracking claims filed, claims accepted, claims rejected.

### Platform Fee Recovery Playbook for D2C: Razorpay, PayU, Marketplace Settlement Audit

Source: https://www.terra-insight.com/insights/platform-fee-recovery-d2c-india/

- **Problem:** A D2C brand routing revenue through three to five payment aggregators and one to two marketplaces accumulates platform fee leakage across MDR drift, settlement-vs-orders mismatch, refund processing, chargeback non-representment, and FX drift on international card transactions. The deductions are contractually defined and individually small, but aggregate to 0.4-0.8% of GMV — material for any brand with annualised GMV above ₹50 crore. The audit is rarely structured: finance teams treat aggregator reports as authoritative and the drift compounds quarter over quarter.
- **Logic:** Run a five-track audit. Track one — MDR per instrument: pull six months of transaction-level settlement files, compute expected fee per transaction at contracted slab by instrument and network, compare to actual deduction, aggregate drift per aggregator. Track two — settlement-vs-orders: match daily order count, gross value, and expected net credit to actual settlement batches; identify missing or delayed batches. Track three — refund leakage: per-refund register matching original transaction fee treatment, partial refund proration, and credit timing. Track four — chargeback: 24-hour intake, per-reason-code evidence library, representment-window discipline, win-rate dashboard. Track five — FX drift: international transaction recompute against published reference rate plus contracted markup. Route variance per track to a named owner with a contractual SLA per the aggregator master agreement.
- **Config:** Per-instrument MDR slab table per aggregator (credit, debit, UPI, netbanking, wallet, EMI, BNPL, international card). Daily settlement-vs-orders reconciliation with per-batch variance threshold. Per-refund register with fee-treatment field. Chargeback workflow with per-reason-code evidence template and 24-hour intake. FX reference-rate source and per-transaction recompute. PA-PG escalation matrix with aggregator-side counterparts named per agreement. Monthly aggregator scorecard covering net effective MDR, settlement reliability, refund-processing latency, chargeback win-rate, and FX drift. Quarterly contract review feeding renegotiation.
- **Output:** A monthly Discovered Money register for platform fees by aggregator by track, with rupees identified, rupees in dispute, rupees recovered, rupees structurally lost. A weekly chargeback queue with representment status. An aggregator scorecard feeding contract renegotiation at renewal. A quarterly board pack line item for platform fee recovery alongside the broader leakage program.

### PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27

Source: https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india/

- **Problem:** PLI Auto scheme operates a ₹26,058 crore outlay over FY 2023-24 to FY 2027-28 with claim disbursement requiring incremental-sales calculation over FY 2019-20 base year, DVA certification at 50%+ thresholds, eligible-product certification, committed-investment milestone tracking, PMA quarterly filing, sanction-to-bank-credit lag of 30-90 days, and post-sanction reconciliation against actual bank receipt — with GST exemption posture and Income Tax taxability creating dual accounting treatment.
- **Logic:** Reconcile claim per quarter against base-year frozen ledger (FY 2019-20 actuals by eligible product), tie eligible-sales calculation to DVA-certified production, file with PMA on quarterly cadence, age sanction letter against bank-credit arrival, queue PMA disallowance lines for appeal in next cycle, book bank credit to correct GAAP ledger with GST exempt and Income Tax taxable treatment, monitor committed-investment milestones against eligibility maintenance.
- **Config:** PLI eligible-product master with FY 2019-20 base sales frozen, DVA calculation worksheet with imported-content tracking, committed-investment milestone register, PMA filing cadence calendar, claim status workflow (drafted, filed, under-review, sanctioned, credited, appealed), bank-credit matching configuration against sanction letter reference, GAAP-treatment flag per receipt.
- **Output:** A quarterly PLI claim dashboard showing eligible incremental sales per product, DVA percentage achieved, claim band, filed claim amount, sanction letter status, bank-credit receipt date and amount, any disallowance amount queued for appeal, cumulative scheme-tenure incentive realised against ₹26,058 crore outlay share, and committed-investment milestone status.

### PLI Auto Scheme Claim Process for FY 2026-27: How Auto-Component Suppliers File and Track Claims

Source: https://www.terra-insight.com/insights/pli-auto-scheme-claim-process-fy-2026-27-india/

- **Problem:** The PLI Auto scheme operates a ₹25,938 crore outlay across a five-year tenure with quarterly claim filing on the SIAM-DHI portal, PMA review by IFCI Limited, sanction-to-bank-credit lag of 30-90 days, disallowance handling, and reconciliation across the FY 2019-20 frozen base year, DVA-certified production, committed-investment milestones and the eventual bank receipt — running across four overlapping cycles per claim period for the full scheme tenure.
- **Logic:** Maintain FY 2019-20 frozen base ledger per eligible product; compute claim-year incremental sales per quarter from audited financial books reconciled to GSTR-1; obtain DVA certificate per quarter at the SKU level; file with SIAM-DHI portal on quarterly cadence with documentation pack; track each filed claim through PMA review, clarification queue, sanction letter and bank credit; reconcile sanction amount against filed claim with disallowance reason; age sanction-to-bank-credit lag; queue disallowances for appeal in next cycle; book PLI receipt to correct GAAP ledger with appropriate GST and Income Tax treatment.
- **Config:** PLI eligible-product master with FY 2019-20 base sales frozen, DVA worksheet with imported-content tracking at the SKU level, committed-investment milestone register against scheme commitment, SIAM-DHI portal filing calendar (Q1 mid-Aug, Q2 mid-Nov, Q3 mid-Feb, Q4 mid-May), claim status workflow (drafted / filed / under-review / sanctioned / credited / appealed), bank-credit matching configuration against IFCI sanction-letter reference, disallowance register, GAAP-treatment flag per receipt.
- **Output:** A quarterly PLI claim dashboard for FY 2026-27 showing eligible incremental sales per AAT product, DVA percentage achieved versus threshold, claim band applied, filed claim amount with portal reference, IFCI sanction letter status with disbursement reference, bank-credit receipt date and amount, sanction-to-credit ageing, any disallowance amount queued for appeal, cumulative scheme-tenure incentive realised against committed envelope and committed-investment milestone status.

### PLI MMF Apparel + Fabric Claim Reconciliation

Source: https://www.terra-insight.com/insights/pli-mmf-apparel-fabric-claim-reconciliation/

- **Problem:** An MMF apparel and fabric manufacturer in Panipat, Surat, or Bhilwara approved as a PLI participant under Category A (₹100 crore plant-and-machinery investment) or Category B (₹300 crore) must file an annual claim for the incentive on incremental sales over the FY 2019-20 base year, across HS Chapters 54, 55, 61, and 62, and demonstrate that every SKU in the eligible-turnover calculation contains ≥70 percent MMF fibre content. Manual PLI claim reconciliation across the HSN-wise sales register, fibre composition test reports, GSTR-1 outward supplies, shipping bill HSN, audited financial statements, and the plant-and-machinery capitalisation schedule typically drops SKUs due to HSN mis-classification or fibre-content mis-declaration, mis-states the incremental sales calculation against the base year, and fails the DPIIT audit-firm certification the first time — costing the participant an entire claim year of incentive payout on ₹100 crore or more of incremental turnover.
- **Logic:** Build a PLI eligible-turnover register keyed by invoice line, tagged at 8-digit HSN, linked to SKU-level fibre composition test reports and to the fixed-asset capitalisation schedule for the P&M investment threshold. Ingest the sales register from the ERP (SAP FI, Oracle Fusion, or Tally), the GSTR-1 HSN summary from the GST portal, the shipping bill HSN from the customs system, and the audited financials from the auditor's working file. Reconcile every invoice line to a fibre composition test report; disqualify SKUs below the 70 percent MMF threshold. Aggregate eligible turnover by claim year, subtract base-year FY 2019-20 eligible turnover, and compute incremental sales. Test the incremental against the minimum hurdle for the claim year. Apply the PLI rate (Category A or B; year 1 to year 5) to the incremental to compute the claim value. Cross-tie the P&M capitalisation to the cut-off date threshold. Produce the audit-firm certification pack in the DPIIT-mandated format.
- **Config:** PLI participant master with approval reference, category (A or B), plant-and-machinery investment commitment, cut-off date, base-year FY 2019-20 declared turnover in eligible products, claim years remaining, and rate schedule per year; HSN eligibility master covering Chapter 54 (5401-5408 synthetic filament), Chapter 55 (5501-5516 synthetic staple), Chapter 61 (6101-6117 knit apparel), and Chapter 62 (6201-6217 woven apparel); SKU-to-fibre-composition mapping with test report reference, test method (IS 667 or IS 3416), NABL lab certificate, MMF percentage by weight, and pass/fail against the 70 percent threshold; fixed-asset register feed with capitalisation date, invoice reference, GRN, commissioning certificate, and eligibility flag (P&M yes/no); minimum incremental sales hurdle per claim year; DPIIT audit-firm certifier working paper template; GSTR-1 HSN summary import for cross-verification; shipping-bill import for export line reconciliation.
- **Output:** A year-end PLI claim pack: HSN-wise eligible turnover for the claim year (Chapter 54, 55, 61, 62 with ≥70% MMF content), non-eligible turnover (cotton apparel, sub-70% blends), and total turnover reconciled to audited financials. Base-year FY 2019-20 eligible turnover recap. Incremental sales calculation showing eligible turnover minus base, tested against the minimum incremental hurdle. PLI rate applied to incremental (Category A or B, year 1 to 5) to derive the claim value. Plant-and-machinery capitalisation schedule demonstrating threshold met by cut-off. Per-SKU fibre composition test report register. Audit-firm certification working paper in DPIIT-mandated format. Disqualification log for SKUs, invoices, or lines dropped from the eligible calculation with reason (HSN mis-classification, fibre content shortfall, base-year restatement, etc.).

### PLI MMF + Technical Textile Claim Reconciliation for India

Source: https://www.terra-insight.com/insights/pli-mmf-technical-textile-claim-reconciliation-india/

- **Problem:** A Category B PLI applicant in the MMF Fabrics or Technical Textiles space carrying a ₹300 crore-plus committed plant and machinery investment must reconcile the sanctioned application against actual capex, the base-year segment turnover benchmark against every subsequent performance-year turnover, year-wise incremental sales hurdles against actual segment-wise incremental delivery, CA-certified P&M and turnover statements against fixed-asset register and audited financials, and the DPIIT annual claim window against the operational calendar. The five-year performance window compounds the reconciliation because a base-year restatement, a mis-classified segment invoice, or a Section 34 credit-note gap cascades into every future claim year, and a claim revision after disbursement typically triggers an incentive recovery notice with interest. Manual reconciliation across an accounting system, a GST filing series, a fixed-asset register, and a scheme claim workflow leaves the applicant exposed to over-claims (recovery risk) and under-claims (permanent revenue leakage on the ₹10,683 crore outlay).
- **Logic:** Anchor the reconciliation to the sanction letter — capture the sanctioned tier (Category A or B), the committed P&M investment, the base-year segment turnover benchmark, and the year-wise incremental sales hurdles and incentive rates as scheme master data. Build a running fixed-asset register tagged by scheme-eligible P&M asset with commissioning date, capitalisation date, and cumulative eligible capitalisation against the sanctioned envelope. Build a segment-classified invoice register that ties every export or domestic invoice to the applicant's committed product lines by HSN (Chapter 54, 55, 61, 62, and Technical Textile sub-segment HSNs); reconcile the segment-classified register to GSTR-1 HSN-wise every month. Run Section 34 credit-note aging every quarter to force cleanup before the 30 November window. Produce the annual CA pack — cumulative P&M investment certificate, segment-wise incremental sales certificate, base-year reconciliation, and DPIIT annexures — in a format the CA can attest to.
- **Config:** Scheme master with sanctioned tier (Category A ₹100 crore or Category B ₹300 crore), committed P&M investment amount, base-year FY, base-year segment turnover by product line, year-wise incremental sales hurdle percentages, year-wise incentive rate applicable, and DPIIT annual claim window (illustratively seven months from FY-end). Fixed-asset register with scheme-eligible P&M flag, commissioning date, capitalisation date, and cost. Product line master mapping MMF Apparel (HS 61/62), MMF Fabrics (HS 54/55), and each notified Technical Textile sub-segment to internal SKU and HSN. Segment-classified invoice register keyed to GSTR-1 HSN-wise summary and GSTR-3B outward taxable turnover. Credit-note register with Section 34 aging alerts at 300, 330, and the November 30 hard-stop days per FY. TDS masters for Section 8 Sl. 8 code 1031 (194Q on capex purchases) for reconciliation against Form 26AS at supplier PAN level.
- **Output:** A DPIIT-ready annual PLI claim pack — sanctioned tier and committed investment envelope; cumulative eligible P&M investment as of performance-year end reconciled to the fixed-asset register at cost; performance-year segment-wise turnover reconciled to GSTR-1 HSN-wise; base-year segment turnover benchmark; year-wise hurdle and incremental sales delta; illustrative incentive computation at the scheme rate for CA review; Section 34 credit-note register cleared as of the November deadline; and the tax audit reconciliation anchoring the numbers to Form 3CD Clause 44. Per-claim aging alerts and CA package handoff cut the annual DPIIT claim preparation cycle from a two-month manual pull to a two-week review, and every claim year ties back cleanly to the sanction letter.

### Domestic Value Addition: KSM Reconciliation for PLI Category 2

Source: https://www.terra-insight.com/insights/pli-pharma-domestic-value-addition-key-starting-material-reconciliation/

- **Problem:** A Category 2 Active Pharmaceutical Ingredient applicant on the PLI Pharma Rs 15,000 crore scheme must reconcile the Domestic Value Addition computation for each eligible product every quarter — ex-factory value from the ERP sales ledger against the BOM-level imported-input register from the SAP material ledger or Oracle Fusion procurement module, DVA percentage computed as (ex-factory minus imported inputs) divided by ex-factory, tested against the 50 percent minimum Category 2 KSM threshold, and disclosed on the DoP PLI portal quarterly claim workbook with a statutory auditor certificate. A Chapter 29 API illustrative persona with ex-factory FY 2026-27 of Rs 82 crore against imported inputs of Rs 26 crore (Chinese Diethyl malonate KSM Rs 12 crore, Chinese 2-Chloropyridine intermediate Rs 8 crore, imported solvents Rs 6 crore) lands at 68.3 percent DVA — safely above threshold. A China-supply-crunch scenario that raises Chinese KSM landed cost by 40 percent to Rs 17 crore pushes aggregate imported inputs to Rs 31 crore and DVA drops to 62 percent — still safe. A more severe shock (Chinese KSM to Rs 25 crore and a currency-driven inflation on other imports) can inch DVA down toward the 50 percent floor, and a KSM-in-KSM double-integration story is the strategic hedge. Missing any hop — BOM-level country-of-origin flag, intra-group KSM transfer price under Section 92BA, monthly DVA trend monitor — breaks the quarterly claim and pushes the applicant into a failed-quarter incentive forfeiture with a Section 92BA transfer-pricing exposure on the intra-group KSM leg.
- **Logic:** Build a BOM master per eligible product with each input line tagged by country of origin (domestic / imported), the HSN chapter, the vendor master reference, and the invoice-level unit rate. Ingest the ERP sales ledger monthly (SAP FI material ledger, Oracle Fusion sales invoicing, or Tally sales register) and extract the ex-factory value for each eligible product. Ingest the ERP procurement ledger monthly and extract the imported-input value for each BOM line of each eligible product, aggregated to the month's production output. Compute the monthly DVA per eligible product as (ex-factory minus imported inputs) divided by ex-factory. Aggregate the monthly DVA into the quarter's DVA for the quarterly claim workbook. Trend the DVA at monthly cadence against the 50 percent Category 2 KSM threshold with an amber-zone alert at 55 percent and a red-zone alert at 52 percent. Separately hold the intra-group KSM transfer register with Section 92BA Rule 10D transfer-pricing documentation reference — the transfer price feeds the DVA composition as domestic-input value. Generate the DoP portal quarterly claim workbook per eligible product with the DVA disclosure line, the imported-input country-of-origin breakdown, and the intra-group KSM transfer disclosure. Attach the statutory auditor certificate schedule and the exception log for any product that failed the DVA test in the quarter.
- **Config:** BOM master per eligible product with country-of-origin flag and HSN chapter per input line; vendor master with country-of-origin master and DGFT importer-exporter-code cross-reference for imported vendors; ERP sales ledger extract by material code for ex-factory value; ERP procurement ledger extract by material code for imported-input value; monthly DVA computation per eligible product with the 50 percent threshold and amber/red alert bands; intra-group KSM transfer register with Section 92BA specified-domestic-transaction flag and Rule 10D transfer-pricing documentation reference; DoP PLI portal filing calendar (quarterly cycle) with the applicable claim window; statutory auditor certificate template with the DVA disclosure schedule; exception log for failed-quarter DVA products with the imported-input driver and the mitigation action (domestic-supplier substitution, backward-integration acceleration, product mix adjustment); Ind AS 20 grant recognition schedule with the reasonable-assurance trigger tied to the DoP portal approval and the DVA-passed status per quarter.
- **Output:** A quarterly Category 2 DVA claim pack per eligible product: the BOM-level composition register with country-of-origin classification, the ex-factory value from the ERP sales ledger, the imported-input value from the ERP procurement ledger decomposed by BOM line, the monthly DVA trend for the quarter with the 50 percent threshold overlay, the quarterly DVA percentage, the intra-group KSM transfer disclosure with the Rule 10D reference, the DoP PLI portal quarterly claim workbook filing template, the statutory auditor certificate schedule, and the exception log for any failed-quarter product with mitigation-action tracking. The monthly DVA trend feeds the applicant's forward outlook: a red-zone alert (DVA between 50 and 52 percent) triggers a procurement-substitution review and a KSM-in-KSM backward-integration commissioning check; an amber-zone alert (between 52 and 55 percent) triggers the finance-team-and-plant-leadership monthly review; above 55 percent is the safe zone. Ind AS 20 grant recognition entries are triggered per quarter per eligible product tied to the DoP portal approval and the DVA-passed status.

### PLI Pharma Rs 15,000 Crore: Eligibility, Incremental Sales, Disbursement

Source: https://www.terra-insight.com/insights/pli-pharma-15000-crore-eligibility-incremental-sales-reconciliation/

- **Problem:** A Category 1 PLI Pharma applicant on the Department of Pharmaceuticals Rs 15,000 crore scheme must reconcile an FY 2019-20 DoP-approved base sales register (illustratively Rs 350 crore across three identified biosimilar products), the Year N incremental sales computation against the DoP-set year threshold, the quarterly claim workbook filed on the DoP PLI portal against the applicant's monthly invoice-level sales ledger, PLI grant income recognition under Ind AS 20 (grants related to income) with the presentation choice of other income or net against expense, and the Section 115JB MAT book-profit adjustment on the grant leg. A cumulative Year 4 incremental sales of Rs 1,600 crore against a Year-4 threshold of Rs 800 crore delivers a 200 percent-of-threshold performance, but the annual incentive at 10 percent is capped at Rs 100 crore per applicant per year for Category 1; the reconciliation must expose the cap binding, the excess incentive foregone, and the impact on the six-year claim trajectory and treasury forecast. Missing any hop — product-code mapping, export-sales exclusion, sample-goods documentation, Section 92BA intra-group transfer treatment — breaks the quarterly claim, delays disbursement, and opens a Section 74 GST or Section 271 income-tax exposure at the year-end statutory audit.
- **Logic:** Build a product master keyed to the DoP-approved identified-product list, with each product tagged with the FY 2019-20 base sales value that was submitted and approved by the Project Management Agency. Ingest the applicant's monthly invoice-level sales ledger from the ERP (SAP FI material ledger, Oracle Fusion sales invoicing, or Tally sales register) and filter to identified products by product-code mapping. Compute the quarter's incremental sales as (identified-product sales for the quarter) minus (FY 2019-20 base allocated to the quarter, typically one-quarter of the annual base). Aggregate quarterly incremental sales into the year's total and compare against the DoP-published year threshold; if the threshold is met, the year is eligible for incentive computation. Apply the Category-appropriate incentive rate (10 percent for Category 1 in Years 1-4, 8 percent in Year 5, 6 percent in Year 6) and cap the incentive at the per-applicant per-year cap. Generate the DoP portal quarterly claim workbook, the reconciliation against the ERP sales ledger, the statutory auditor certificate template, and the exception log for export sales, sample distribution, and Section 92BA intra-group transfers. On the accounting side, book the PLI grant receivable under Ind AS 20 as it becomes reasonably assured, recognise as other income (or net against related expense per the entity's presentation choice) in profit or loss, and compute the Section 115JB MAT book-profit adjustment on the grant income for the year's tax provisioning.
- **Config:** Identified-product master keyed to DoP-approved list with FY 2019-20 base sales per product; scheme category flag (Cat 1 / Cat 2 / Cat 3); scheme year mapping (FY 2020-21 = Year 1, FY 2021-22 = Year 2, etc.); DoP-published incremental sales threshold per year; incentive rate schedule per category per year; per-applicant per-year cap (Rs 100 crore for Category 1); ERP product code to identified-product mapping (SAP material master, Oracle item master, Tally stock item master); sales register filters for export sales, sample distribution, inter-company transfer, and returns and rebates; Ind AS 20 recognition template with grants-related-to-income vs grants-related-to-assets flag and presentation choice (other income line vs net-of-expense); Section 115JB MAT book-profit computation schedule with the PLI grant adjustment line; Section 115BAA regime flag with the trade-off model against Section 35(2AB) forfeiture; Section 92BA specified-domestic-transaction register with Rule 10D transfer-pricing documentation flag for any intra-group transfer of identified products; DoP portal filing calendar (quarterly cycle with 45-day post-quarter filing window in typical scheme rules).
- **Output:** A quarterly PLI claim pack: the identified-product sales ledger for the quarter cross-referenced against the DoP-approved base, the quarter's incremental sales computation with year-to-date aggregation, the cumulative-year incremental sales against the DoP threshold, the incentive computation at the Category-appropriate rate with the applicant-year cap binding shown explicitly and the excess incentive foregone quantified, the DoP portal quarterly claim workbook filing template, the statutory auditor certificate schedule, the export-sales / sample-goods / Section 92BA exception log, and the accounting entry pack showing PLI grant receivable, other income (or net-of-expense presentation), the Section 115JB MAT book-profit adjustment, and any Section 194Q or Section 206C(1H) cross-check on high-value identified-product supplier or customer transactions. At year-end, the pack aggregates to the annual claim reconciliation, the year's incentive as approved by DoP against the applicant's own computation, and the roll-forward of the FY 2019-20 base for any DoP-notified changes to the identified-product portfolio. The six-year scheme window forecast rolls the year-by-year approved incentive into the applicant's treasury and Ind AS 20 grant recognition schedule.

### PLI Pharma Categories 1 / 2 / 3: Differential Eligibility Rules

Source: https://www.terra-insight.com/insights/pli-pharma-category-1-2-3-eligibility-differential-treatment/

- **Problem:** A Tier 2 pharma applicant of the scale of a Suven Life Sciences with a candidate product portfolio that straddles complex generics, APIs and repurposed drugs must run a category-selection decision matrix against the Department of Pharmaceuticals PLI Pharma Rs 15,000 crore scheme before scheme entry — Category 1 with a 10 percent Year 1-4 rate capped at Rs 100 crore per applicant per year but strict product-basket admission; Category 2 with a 10 percent Year 1-2 rate tapered to 6 percent Year 5-6 and a 50 percent Domestic Value Addition floor for the Key Starting Material leg; Category 3 with a flat 5 percent rate across the six-year window and the widest product-basket admission but the lowest incentive quantum. The matrix must reconcile product-basket fitment per candidate product, FY 2019-20 base-year sales reconstruction per candidate product from SAP FI material-code history, category-specific eligibility test (DVA for Cat 2 KSM, export commitment for Cat 3 medical device, complex-generics definition for Cat 1), incentive-rate arithmetic with per-applicant per-year cap binding explicitly quantified, and the Section 115BAA concessional-regime opt-in impact model against Section 35(2AB) weighted-deduction forfeiture. Missing any layer produces a category recommendation that under- or over-states the scheme-window disbursement forecast by tens of crores and, in a Category 1 R&D-heavy applicant scenario, can cost 4 to 6 percentage points of effective tax on the R&D pool by opting into Section 115BAA without modelling the trade-off first.
- **Logic:** Build a candidate-product register keyed to the DoP category definitions, with each candidate product tagged Cat 1 / Cat 2 / Cat 3 per the scheme guidelines. Reconstruct the FY 2019-20 base-year sales per candidate product from the SAP FI material ledger, Oracle Fusion sales invoicing, or Tally sales register, and validate against GSTR-1 FY 2019-20 filings and the audited financial statements. For Cat 2 KSM candidates, compute the historical DVA per product using the imported-input register cross-linked to Bill of Entry filings and project the forward DVA under the scheme-window supply-chain plan; test against the 50 percent floor. For Cat 3 medical device candidates, model the export-commitment percentage against the DGFT shipping-bill register. For Cat 1 candidates, validate against the complex-generics or patented-drug definitional test. Apply the category-specific incentive-rate schedule to a plausible six-year incremental-sales trajectory per candidate product basket, bind the per-applicant per-year cap and quantify the excess incentive foregone under each scenario. Run the Section 115BAA opt-in impact model — compute the effective tax under the normal regime with Section 35(2AB) weighted deduction preserved and Section 115JB MAT applied to the PLI grant, versus the concessional 22 percent regime with Section 35(2AB) forfeited and MAT exempt. Aggregate the five layers into a ranked category-selection recommendation per candidate product basket.
- **Config:** Candidate-product register with DoP category tagging (Cat 1 / Cat 2 / Cat 3); ERP material-code mapping to candidate products (SAP material master, Oracle item master, Tally stock item master); FY 2019-20 base-year sales reconstruction template keyed to material code with GSTR-1 cross-validation and audited-financial-statement tie-out; DVA computation template for Cat 2 KSM with Bill of Entry cross-linked imported-input register and 50 percent floor test; export-commitment computation template for Cat 3 medical device with DGFT shipping-bill cross-linked export register; category-specific incentive-rate schedule (Cat 1: 10 percent Y1-4, 8 percent Y5, 6 percent Y6; Cat 2: 10 percent Y1-2, 8 percent Y3-4, 6 percent Y5-6; Cat 3: 5 percent flat Y1-6); per-applicant per-year cap register (Rs 100 crore for Cat 1; category-specific caps for Cat 2 and Cat 3); Section 115BAA opt-in impact model with the Section 35(2AB) weighted-deduction forfeiture line, the Section 115JB MAT exemption line, and the normal-versus-concessional effective-tax comparison; Ind AS 20 grant-recognition projection per category-selection scenario; Section 92BA specified-domestic-transaction flag for any candidate product with intra-group transfer exposure; DoP portal filing cadence (quarterly) and category-wise workbook template.
- **Output:** A category-selection decision pack per Tier 2 pharma applicant: candidate-product register with per-product category recommendation and rationale; FY 2019-20 base-year sales reconstruction per candidate product with GSTR-1 and audited-financial-statement tie-outs; DVA / export-commitment / complex-generics eligibility test results per candidate product; six-year incentive-rate arithmetic per category-selection scenario with per-applicant per-year cap binding and excess incentive foregone quantified; Section 115BAA opt-in impact model output showing effective tax under normal regime versus concessional regime; ranked category-selection recommendation with total scheme-window disbursement forecast per scenario; and the parallel category-wise DoP portal quarterly claim workbook templates for the selected categories. On scheme entry the pack hands over to the operational PLI claim workflow — per-category product-master, per-category quarterly claim workbook, and per-category statutory-auditor certificate schedule — so the category-selection decisions made at entry cascade into the operating reconciliation surface without a manual re-mapping step.

### Base Year FY 2019-20: Reconciling Incremental Sales for PLI Claim

Source: https://www.terra-insight.com/insights/pli-pharma-incremental-sales-base-year-fy-2019-20-reconciliation/

- **Problem:** A Category 1 PLI Pharma applicant of the Alkem-scale complex-generics persona must reconstruct FY 2019-20 identified-product sales at SKU-and-UoM level for a 10-molecule approved product basket, convert the pre-GST-2.0 12 percent HSN 3004 output-invoice value to a net-of-tax equivalent (the actual revenue realised under Ind AS 115), standardise the tablet-capsule-vial dose form across the workbook, adjust for DPCO 2013 ceiling-price movement on NLEM-scheduled molecules, submit the base-sales register with the audited financial statements and the GSTR-1 and GSTR-3B FY 2019-20 returns to the Department of Pharmaceuticals Project Management Agency, and secure the DoP-approved base-year certificate that anchors every subsequent Year 1 through Year 6 incremental sales bridge on the quarterly claim workbook. Base-year sales illustratively at Rs 285 crore across the 10-molecule basket; Year 1 minimum incremental threshold of 10 percent = Rs 314 crore; Year 4 cumulative incremental sales approaching Rs 1,650 crore against a DoP-set Year 4 threshold of Rs 780 crore = 212 percent-of-threshold performance = raw incentive of Rs 165 crore capped at the Rs 100 crore Category 1 applicant-year cap. The base-year reconstruction is a five-to-six-year-old data-engineering exercise; SKU-level historical data recovery from the SAP or Oracle archive, UoM standardisation across dose forms, and volume-vs-value adjustment for MRP-controlled molecules under DPCO 2013 are the three surfaces where an untidy reconstruction breaks the DoP certification cycle.
- **Logic:** Extract FY 2019-20 sales at invoice-line level from the SAP FI billing document archive or the Oracle Fusion sales invoicing history, filtered to identified products by ERP material-code mapping to the DoP-approved product list. For each invoice line, compute the net-of-tax revenue as gross invoice value divided by (1 + applicable output-tax rate) — 12 percent for most HSN 3004 formulation SKUs in FY 2019-20, 5 percent for the small subset. Sum invoice-line net revenue per SKU per state GSTIN per month across FY 2019-20 to produce the per-SKU monthly sales register. Apply the UoM standardisation table to convert primary pack UoM (10-tablet strip, 30-capsule bottle, 5-vial pack) to per-dose-form quantity so the workbook carries both value and standardised physical volume. Cross-check the aggregated FY 2019-20 sales value against the audited revenue line for identified products under Ind AS 115 and against the GSTR-1 outward supplies filed for FY 2019-20 across every state GSTIN. Net off Section 34 credit-note adjustments recorded post-year-end against FY 2019-20 invoices (returns, trade discount reconciliation, price protection). For NLEM-scheduled SKUs, tag each SKU with the FY 2019-20 NPPA ceiling price and set up the DPCO 2013 price-control adjustment register that will track ceiling-price movement across the six-year scheme window. Submit the reconciled base-sales register with the audited financial statements, the FY 2019-20 GSTR-1 and GSTR-3B returns, the ERP-to-DoP mapping table, the UoM standardisation table, the DPCO 2013 flag and ceiling-price snapshot, and the statutory auditor certificate to the DoP Project Management Agency for base-year certification. On issue of the DoP base-year certificate, freeze the base-sales register as the immutable reference for the Year 1 through Year 6 incremental sales bridge on the quarterly claim workbook.
- **Config:** SAP FI billing document extract (or Oracle Fusion sales invoicing history) for FY 2019-20 at invoice-line detail; ERP material master with DoP-approved identified-product flag and product-code mapping; UoM standardisation table with dose-form and per-unit conversion factors; HSN and tax-code map (HSN 3004 at 12 percent for most FY 2019-20 formulations, 5 percent for the small subset); NLEM-scheduled-formulation flag and NPPA ceiling-price snapshot for scheduled SKUs; Section 34 CGST credit-note register keyed to original FY 2019-20 invoices; state GSTIN roster for the applicant's multi-state manufacturing and invoicing footprint; audited financial statements FY 2019-20 (standalone entity); GSTR-1 and GSTR-3B FY 2019-20 filings; Ind AS 115 revenue recognition policy note; statutory auditor certificate template for base-year sales certification; DoP base-year certificate template and Project Management Agency submission pack format; DPCO 2013 price-control adjustment register with per-SKU ceiling-price movement tracker across the six-year scheme window; Year N incremental sales bridge template with volume-growth leg and price-realisation leg decomposition for scheduled formulations.
- **Output:** A DoP-submission-ready FY 2019-20 base-sales pack: the per-SKU per-molecule sales register at both value (net-of-tax revenue in rupees) and standardised physical volume, aggregated to the identified-product-basket total; the ERP-to-DoP product code mapping table with every SKU accounted for; the UoM standardisation table for cross-SKU comparability; the NLEM DPCO 2013 flag and FY 2019-20 NPPA ceiling-price snapshot for scheduled SKUs; the Section 34 credit-note net-off register; the state-GSTIN-level GSTR-1 and GSTR-3B FY 2019-20 tie-out; the Ind AS 115 revenue reconciliation to the audited standalone financial statements; and the statutory auditor certificate confirming the base-year sales value. On issue of the DoP base-year certificate, the frozen base-sales register anchors every Year 1 through Year 6 quarterly claim workbook — the Year N per-quarter identified-product sales extraction, the incremental sales bridge against the DoP-set year threshold, the Category 1 incentive at 10 percent (Years 1-4) / 8 percent (Year 5) / 6 percent (Year 6) with the Rs 100 crore applicant-year cap binding, and the DPCO 2013 volume-vs-value decomposition on scheduled formulations.

### PLI Technical Textile (Medical, Agro, Packaging) Claim Reconciliation

Source: https://www.terra-insight.com/insights/pli-technical-textile-medical-agro-claim/

- **Problem:** A specialist technical-textile principal running four PLI-eligible product lines — sportech (sports nets), geotech (geogrid, geobag), agrotextile (crop protection nets, mulch mats), and packtech (FIBC, woven sacks) — must reconcile a PLI Textiles claim against DPIIT operational guidelines: segment-wise incremental sales certification against a base-year turnover, plant-and-machinery investment year-wise against commissioning date, and compliance with the tier-linked minimum incremental sales hurdle. The scheme's 8-digit HS code eligibility list means that even minor product variants (a non-notified variant on the same production line) are excluded from the incremental tally, and shared P&M between eligible and non-eligible production requires an engineering allocation. Missing this reconciliation leads to Chartered Accountant certificate rejection, Independent Engineer verification gaps, and PLI incentive claw-back during the DPIIT Project Management Agency scrutiny cycle.
- **Logic:** Build a segment-wise turnover register keyed to notified 8-digit HS codes; separate base-year FY 2019-20 turnover by segment from each performance-year turnover by segment; compute segment-wise incremental sales and cross-verify against audited financials, GSTR-9 annual return, and shipping bills. Maintain a plant-and-machinery asset register with per-asset invoice reference, date of commissioning, eligible-P&M classification, and segment attribution; run the cumulative P&M investment tally against the declared tier (₹100 crore Category A or ₹300 crore Category B). Cross-map every SKU to its 8-digit HS code and flag non-notified variants excluded from the PLI-eligible tally. Reconcile job-work movement (Rule 55, ITC-04, Section 143 CGST) so that intermediate technical-textile conversion stages do not fall foul of the deemed-supply clock. Produce the annual DPIIT claim pack — Chartered Accountant certificate, Independent Engineer certificate, statutory auditor's compliance affidavit, product-wise sales detail at 8-digit HS code — with source-document traceability at every line item.
- **Config:** PLI registration master with declared tier (A or B), scheme year, base year (FY 2019-20), base-year segment-wise turnover baseline, and applicable minimum incremental sales percentage; notified 8-digit HS code list per the DPIIT operational guidelines, tagged by technical textile sub-segment (medical, agro, packaging, mobiletech, geotech, sportech, buildtech, protech, oekotech, indutech, hometech, clothtech); SKU-to-HS-code mapping table for every product line with the eligible/non-eligible flag; plant-and-machinery asset register with per-asset invoice reference, date of commissioning, cost, eligible classification, and segment attribution; job-work-chain configuration (Section 143 CGST 1-year clock, Rule 55 challan register, ITC-04 filing frequency); segment-wise turnover feed from the sales system, cross-referenced to GSTR-1 line items, e-invoice IRN, and export shipping bills; audit-trail retention for the seven-year DPIIT claim-scrutiny window.
- **Output:** An annual PLI Textiles claim pack: segment-wise incremental sales table (base-year FY 2019-20 versus performance year), Chartered Accountant certificate of incremental sales cross-verified to audited financials and GSTR-9, Independent Engineer certificate of cumulative P&M investment against commissioning date, statutory auditor's compliance affidavit confirming the minimum incremental sales hurdle at the declared tier, product-wise sales detail at 8-digit HS code, and job-work reconciliation confirming Section 143 CGST closure for every intermediate conversion chain. Non-eligible variant sales are separately reported and excluded from the incremental tally with an explicit reconciliation footnote. Site-visit-ready asset register with invoice copies, commissioning certificates, and photographs supports DPIIT verification. Year-wise P&M investment tally against the declared tier surfaces any tier under-achievement early enough to remedy before the scheme timeline closes.

### PLI Pharma Quarterly Disbursement: DoP Portal Reconciliation

Source: https://www.terra-insight.com/insights/pli-pharma-quarterly-disbursement-dop-portal-reconciliation/

- **Problem:** A Category 1 PLI Pharma applicant on the DoP Rs 15,000 crore scheme running its Year 6 quarterly claim cycle must reconcile the DoP PLI portal submission log (Q1 filed by 15-Jul, Q2 by 15-Oct, Q3 by 15-Jan, Q4 by 15-Apr), the 30 to 60 day document verification tracker maintained by the DoP scheme secretariat, the sanction order and disbursement received 30 to 45 days after verification, the Ind AS 20 accrual policy (systematic over eligibility period Q1 through Q4 or point-in-time at sanction, per the entity's stated accounting policy), and the Section 115JB MAT book-profit adjustment on the grant income leg per quarter. An illustrative Year 6 cumulative sanction of Rs 92 crore against the Cat 1 Year 6 cap of Rs 100 crore per applicant per year leaves Rs 8 crore of cap headroom that the applicant must track quarter by quarter; a missed straddle between an Ind AS 20 accrual booked in the eligibility quarter and a DoP sanction issued in a later quarter opens a Section 115JB MAT under-provisioning exposure or a book-tax timing gap at the year-end statutory audit.
- **Logic:** Build a quarterly disbursement tracker keyed to the DoP portal claim reference number. Log the Q1 through Q4 filing dates against the scheme SOP deadlines (15-Jul, 15-Oct, 15-Jan, 15-Apr) and monitor the 30 to 60 day verification window per quarter. On DoP query issuance, route the query to the specific reconciling item (ERP mapping, export exclusion, sample carve-out, Section 92BA intra-group treatment) and reset the verification clock for the sub-item. On sanction order receipt, reconcile the DoP-sanctioned amount to the applicant's book-side claim and record the reconciling items — SKU disallowance, intra-group treatment difference, cap binding — in the tracker with owner and closure target. Drive the Ind AS 20 recognition entry per the entity's accounting policy (systematic accrual over the eligibility period or point-in-time at sanction). Feed the quarterly PLI grant income leg to the Section 115JB MAT provisioning workflow. At year-end, reconcile the aggregate DoP-sanctioned amount to the aggregate Ind AS 20 grant income to the aggregate Section 115JB MAT provisioned for the year — each dimension must reconcile to a single audit-defensible number.
- **Config:** DoP portal claim reference master with quarter tag (Q1 through Q4), scheme year (Year 1 through Year 6), filing date, verification start date, verification end date, sanction date, disbursement date, and cash-receipt date; identified-product master keyed to DoP-approved list with FY 2019-20 base sales per product and ERP material code mapping; incremental sales computation per quarter with YTD aggregation and comparison to DoP-set year threshold; applicant-year cap binding tracker (Rs 100 crore for Category 1) with YTD claimed, headroom remaining, and excess incentive foregone; DoP query letter register keyed to reconciling item and response cycle; sanction-versus-books reconciling item register with owner, target closure date, and closure status; Ind AS 20 accounting policy flag (systematic accrual over eligibility period OR point-in-time at sanction) with disclosed policy note reference; Section 115JB MAT book-profit adjustment schedule per quarter with grant-income leg reconciled to Ind AS 20 recognition; Section 115BAA regime flag; Section 92BA specified-domestic-transaction register with Rule 10D transfer-pricing documentation reference for intra-group transfers.
- **Output:** A quarterly PLI disbursement reconciliation pack per quarter per scheme year: DoP portal filing calendar with per-quarter filing date, verification start and end dates, sanction date, and cash-receipt date; sanction-versus-books reconciling items list with SKU disallowance, intra-group treatment difference, cap binding, and each item's owner and target closure; Ind AS 20 grant recognition entry pack with policy-choice flag (systematic or point-in-time), grant receivable balance, and profit and loss recognition leg per quarter; Section 115JB MAT book-profit adjustment schedule with grant-income line per quarter and year-to-date aggregation; treasury projection mapping expected sanction and cash-receipt dates against the applicant's working-capital forecast. At year-end the pack aggregates to the annual PLI disbursement reconciliation, the year's Ind AS 20 grant income against DoP-sanctioned aggregate, and the year's Section 115JB MAT provision against normal-regime tax liability.

### PLI Textile Machinery Capitalisation and Investment Tracking

Source: https://www.terra-insight.com/insights/pli-textile-machinery-capitalisation-reconciliation/

- **Problem:** A textile PLI applicant running a greenfield or brownfield expansion under the MMF Apparel, MMF Fabrics, or Technical Textiles vertical must demonstrate cumulative eligible Plant & Machinery investment of ₹100 crore (Category A) or ₹300 crore (Category B) by the tier-measurement date, evidenced by a fixed-asset register that correctly splits P&M from civil works, land, and administrative buildings — none of which count. Commissioning date rather than order date or payment date governs when capex joins the eligible base. Applicants that mix P&M with civil construction in a single capex pool, or that count CWIP as commissioned P&M, over-state the eligible investment on the DPIIT annual declaration and expose the disbursement to defer or partial recovery.
- **Logic:** Structure the fixed-asset register with distinct asset classes from day one — Plant & Machinery (sub-classed by spinning, weaving, dyeing, utilities), Building — Factory Shop Floor, Building — Administrative and Ancillary, and Land. Tag each row with a PLI-eligibility flag. Track capex through CWIP with vendor PO, invoice, freight and erection billing, and commissioning certificate; transfer to Fixed Asset only on commissioning date (Ind AS 16 capable-of-operating criterion). Report gross capitalised cost — not WDV — as the PLI eligible investment. Reconcile the annual DPIIT declaration against three anchors: the CWIP-to-Fixed-Asset transfer log, the audited financial statement P&M gross block movement, and the vendor payment trail from the banker's statement.
- **Config:** Fixed-asset register with four asset classes (P&M, Building-Factory, Building-Admin, Land), P&M sub-classed by process line (spinning, weaving, dyeing, utilities); PLI-eligibility flag per row (Eligible / Not Eligible / Under Review); commissioning-date field with installation certificate reference and trial-production report reference; capitalisation-date field aligned to Ind AS 16 capable-of-operating criterion; CWIP tracking ledger with vendor PO, invoice, freight, and erection billing threads keyed to the eventual P&M asset row; depreciation block for both Ind AS 16 book (WDV or SLM at entity option) and income-tax Section 43 (WDV at prescribed rates); DPIIT declaration draft template with cumulative eligible investment by FY, product-line linkage (MMF Apparel / MMF Fabrics / Technical Textiles), and auditor-certification annexure; PLI tier threshold (₹100 crore Category A or ₹300 crore Category B) and gestation-period end-date configuration.
- **Output:** A DPIIT-audit-ready pack for the annual PLI declaration: cumulative gross eligible Plant & Machinery investment by financial year and by sub-class, cross-reconciled to the CWIP-to-Fixed-Asset transfer log, the audited financial statement P&M gross block movement, and the vendor payment trail. Commissioning-date evidence bundled per machinery phase-batch — installation certificates, trial-production reports, capitalisation-date entries. Non-eligible capex (civil works, land, administrative buildings, pre-operative expenditure) reported separately and reconciled to the balance-sheet total capex, with the eligible-versus-total ratio shown. Tier-threshold monitor tracks cumulative eligible investment against the ₹100 crore or ₹300 crore ceiling with alerts at 75 percent, 90 percent, and 100 percent of target.

### PLI Textile Minimum Investment Tiers (₹100 cr vs ₹300 cr) Reconciliation

Source: https://www.terra-insight.com/insights/pli-textile-minimum-investment-100-cr-300-cr-tier/

- **Problem:** A new-entrant textile mill applying for the PLI scheme for MMF Apparel, MMF Fabrics, or Technical Textiles must choose between Category A (₹100 crore minimum P&M investment, lower incentive multiples) and Category B (₹300 crore minimum P&M investment, higher incentive multiples) at registration, and then reconcile the year-wise capitalisation of plant and machinery against the chosen tier threshold at every DPIIT annual review through the incentive window. A mismatch between the internal P&M register and the DPIIT-declared figure — driven by mis-dated commissioning certificates, capital work-in-progress carried into the wrong performance year, or machinery that does not qualify for the applied sub-scheme — suspends that year's incentive disbursement pending reconciliation. If the mill's capex plan later shifts upward past the Category B threshold, an upgrade is possible but requires re-registration under the DPIIT operating guidelines, and only future performance years take the higher multiples; historical years already claimed at Category A rates do not retro-flip.
- **Logic:** Build a machinery master tagged by sub-scheme (MMF Apparel per HS Chapters 61 and 62; MMF Fabrics per HS Chapters 54 and 55; Technical Textiles by product line). Ingest the year-wise P&M capitalisation register from the general ledger, joined to a commissioning certificate register keyed by asset ID. Apply the Ind AS 16 'available for use' test to place each asset into the correct performance year. Aggregate year-wise cumulative P&M investment and compare against the tier commitment (₹100 crore for A, ₹300 crore for B). Version the tier commitment on any board-approved capex revision that crosses the ₹300 crore mark, and re-run the future-year comparison at the upgraded threshold. Feed the DPIIT annual return draft from the same register so the internal ledger and the DPIIT-declared figure remain in lock-step.
- **Config:** Registration master with sub-scheme (MMF Apparel / MMF Fabrics / Technical Textiles), tier choice (A or B), registration date, and eligible investment window; machinery master with asset ID, machinery description, sub-scheme tag, HS chapter alignment, and supplier PAN and GSTIN; capitalisation register with asset ID, purchase order date, invoice date, capitalisation date (Ind AS 16 available for use), commissioning date, gross block value, and CWIP flag; commissioning certificate register with chartered engineer certificate reference; tier commitment version log with board resolution reference and revised bank guarantee reference; sub-scheme product line master for MMF Apparel (HS 61 / 62 line items), MMF Fabrics (HS 54 / 55 line items), and Technical Textiles (medical, agro, packaging, mobiletech, geotech, sportech, buildtech, protech, oekotech, indutech, hometech, clothtech).
- **Output:** A performance-year PLI tier compliance pack: year-wise cumulative P&M investment against the tier threshold (₹100 crore for A, ₹300 crore for B); sub-scheme-wise breakdown of qualifying machinery; commissioning-date-wise placement of assets into performance years per Ind AS 16; CWIP carry-forward flags for assets not yet available for use at FY close; tier-upgrade version log with board resolution and re-registration references; DPIIT annual return draft reconciled to the P&M register; and an incremental-sales computation against the base year at the tier multiple applicable to that performance year. The pack satisfies the DPIIT annual verification, the statutory audit, and the internal capex-governance committee in one closing view.

### PLI Grants vs MAT: How Section 115JB Interacts with PLI Income

Source: https://www.terra-insight.com/insights/pli-vs-mat-minimum-alternate-tax-pharma-interaction/

- **Problem:** A Tier-2 biosimilars formulator receives a PLI Category 1 quarterly disbursement of the order of Rs 62 crore for the fourth eligible year against incremental sales computed at the 10 percent Year 4 formula. The grant is recognised as book income in the statement of profit and loss under Ind AS 20 (grant related to income). The company's Ind AS book profit for FY 2026-27 sits of the order of Rs 1,240 crore; the Section 115JB adjusted book profit after Explanation 1 add-backs sits of the order of Rs 1,285 crore illustratively; the MAT at 15 percent plus applicable surcharge and health-and-education cess sits at the order of Rs 193 crore. The normal-regime tax at 30 percent on total income (after Section 35(2AB) in-house R&D weighted deduction, other Chapter VI-A deductions, and Section 32 unabsorbed depreciation set-off) sits at the order of Rs 155 crore. MAT is binding by Rs 38 crore. The Rs 38 crore excess is a Section 115JAA MAT credit carried forward for 15 assessment years, recognised as an Ind AS 12 deferred tax asset subject to the recoverability assessment. Separately the finance team must model the Section 115BAA 22 percent concessional-rate election, which would surrender Section 35(2AB), the balance of Chapter VI-A other than Section 80JJAA, and any unutilised MAT credit — an irrevocable decision that must be evaluated year on year.
- **Logic:** Build a three-register tax-provisioning workbook. Register one is the PLI grant register, keyed to the DoP quarterly disbursement approval and the Ind AS 20 recognition entry (grant related to income; profit-and-loss recognition matched to the incremental sales that trigger entitlement). Register two is the Section 115JB book-profit workbook — starting from the audited Ind AS profit for the year, applying Explanation 1 clause (a) to (k) add-backs (income tax paid, transfer to reserves, provisions for unascertained liabilities, depreciation, deferred tax and others) and clause (i) to (viii) reductions (amount withdrawn from reserves, brought-forward loss or unabsorbed depreciation whichever is less, and others), deriving adjusted book profit, and computing MAT at 15 percent plus applicable surcharge and cess. Register three is the Section 115JAA MAT credit register — tracking the credit generated each year, the 15-year carry-forward clock per assessment year, the year-by-year utilisation, and the Ind AS 12 deferred tax asset movement. Overlay a Section 115BAA scenario model — total income without Section 35(2AB), 35AD, Chapter VI-A other than 80JJAA and 80M; 22 percent plus 10 percent surcharge and 4 percent cess; no MAT; lapse of accumulated MAT credit. The base-case normal-regime provision and the parallel Section 115BAA scenario are compared and the tax decision documented in the year-end tax memo.
- **Config:** PLI grant register with quarter, Category (1/2/3), incremental-sales base, computed grant at the applicable Category rate, DoP disbursement date, Ind AS 20 recognition entry (P&L line and account); Section 115JB book-profit workbook with Ind AS profit-for-the-year opening balance, Explanation 1 clause (a) to (k) add-back line items, clause (i) to (viii) reduction line items, adjusted book profit, MAT rate 15 percent, surcharge 7 or 12 percent by total income slab, cess 4 percent, computed MAT; Section 115JAA MAT credit register with credit-generation year, credit amount, 15-year carry-forward end year, year-by-year utilisation ledger, Ind AS 12 DTA carrying value, DTA movement in the year; Section 115BAA scenario model with taxable income restated without surrendered deductions, tax rate 22 percent plus 10 percent surcharge plus 4 percent cess, MAT not applicable, MAT credit lapse if elected; Form 29B MAT report data feed; Form 3CB-3CD tax audit report data feed; audit-trail hyperlink from the tax provision in the financial statements back to the underlying registers.
- **Output:** A year-end tax-provisioning pack per assessment year: PLI grant recognised in P&L, Section 115JB adjusted book profit workbook with the Explanation 1 add-backs and reductions line-by-line, computed MAT and the normal-regime tax computation side by side, the binding-regime determination (MAT or normal), Section 115JAA MAT credit generated or utilised in the year, Ind AS 12 deferred tax asset roll-forward, and the Section 115BAA scenario evaluation memo. The pack ties to the Form 29B MAT report, the Form 3CB-3CD tax audit report, the audited financial statement tax provision, and the deferred tax note. Multi-year modelling supports the recoverability assessment for the Section 115JAA MAT credit deferred tax asset and the tax-strategy decision on whether and when to elect Section 115BAA.

### PLISFPI Claim Mechanics and Reconciliation for Indian Food Processing

Source: https://www.terra-insight.com/insights/plisfpi-claim-mechanics-reconciliation-india-fmcg/

- **Problem:** PLISFPI beneficiaries — the 53 entities in the MoFPI July 2024 DPIIT order including HUL, ITC, Britannia, Dabur, Nestle India, Tata Consumer, Varun Beverages, GCMMF, Bikaji and Haldiram — must compute and file an incremental-sales claim within seven months of each financial year-end of the ₹10,900 crore six-year scheme (FY 2021-22 to FY 2026-27). The claim base is incremental sales over a frozen FY 2019-20 base year of eligible products only, gated by minimum-sales and minimum plant-and-machinery investment thresholds, and the audit pack must reconcile to GST sales, the fixed-asset register, the contract-manufacturing TDS register under Section 393(1) Sl. 4, and the ICAI-certified statutory financials. Ind AS 20 governs the books accrual and Section 145B of the Income-tax Act 2025 governs the year-of-receipt income-tax recognition, creating a structural book-tax timing gap that the reconciliation pack has to evidence.
- **Logic:** Build a PLISFPI claim register keyed by claim year, product segment, eligible-product HSN, and beneficiary entity. Tie the FY 2019-20 base sales declared in the original application to the audited financials filed with MCA at the eligible-product level, freezing the base as the canonical reference. Reconcile claim-year incremental sales to GSTR-1 and GSTR-9 net sales by adjusting for branch transfers, returns and the segment-eligible-product carve-out. Cross-foot plant-and-machinery investment certification to the fixed-asset register from FY 2020-21 onwards. Build the contract-manufacturer output adjustment with the TDS register under Section 393(1) Sl. 4 payment codes 1001 and 1023 as the supporting evidence. Track MoFPI disbursement against filed claim line by line, classify variances by rejection reason, and feed the next-year amendment with a re-stated claim ledger.
- **Config:** Beneficiary master keyed by DPIIT order entity name, applicant category (I or II), product segment, and approved investment plan; eligible-product master with HSN-2 / HSN-4 carve-out flags per segment; FY 2019-20 base sales register frozen at original-application sign-off; annual claim-sales feed from the company DMS by product by region by period; GSTR-1 sales tie-out feed; fixed-asset register feed for plant-and-machinery investment with effective-from-FY-2020-21 flag; contract-manufacturer TDS feed under Section 393(1) Sl. 4 payment codes 1001 / 1023; MoFPI disbursement register with claim-line reference; Ind AS 20 grant accrual policy versus Section 145B income-tax timing rule for deferred-tax computation.
- **Output:** An annual PLISFPI claim pack filed within seven months of FY-end: (a) the incremental-sales reconciliation from base year to claim year by segment-eligible products, (b) the GST sales tie-out with documented adjustments, (c) the plant-and-machinery investment certification reconciled to the fixed-asset register, (d) the contract-manufacturer output inclusion with TDS-register evidence, and (e) the ICAI-member auditor's certificate. The same data feeds the Ind AS 20 grant accrual journal in the books, the Section 145B disclosure on receipt, the deferred-tax timing-difference schedule, and the post-disbursement variance ledger that feeds the next-year amendment.

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

Source: https://www.terra-insight.com/insights/plisfpi-incremental-sales-base-year-fy2019-20/

- **Problem:** PLISFPI pays incentive on the difference between an eligible year's sales of in-scope manufactured food products and the same beneficiary's FY 2019-20 base-year sales of those products — but the claim has to tie out to GSTR-3B aggregate turnover, MCA XBRL-filed audited financials, and an internal SKU-level eligible-segment sales ledger that most beneficiaries cannot reproduce without rebuild. Each eligible year is independently tested against a category-wise minimum sales threshold, and the FY 2019-20 base is fixed for the full scheme tenure FY 2021-22 to FY 2026-27. The PMA verification gate holds disbursement on every gap that cannot be explained line by line.
- **Logic:** Build a base-year register for FY 2019-20 keyed by SKU, HSN, distributor GSTIN, and PLISFPI category-eligibility flag; lock the total and the per-category cuts before the first claim is filed. For each eligible year FY 2021-22 onward, rebuild the eligible-segment sales register from the distributor management system or SAP CO-PA, applying the same SKU-eligibility master. Tie the eligible-segment total to GSTR-3B aggregate turnover via a documented walk (eligible plus ineligible product mix, plus inter-state branch transfers, plus non-GST revenue, equals GSTR-3B turnover). Tie the same eligible-segment total to MCA XBRL audited revenue via a second walk. Test the eligible-year figure against the category minimum sales threshold; if below threshold, mark year non-eligible and continue the scheme on subsequent years. Compute incremental over FY 2019-20 base, apply the scheme incentive percentage up to the cap, and produce the claim pack.
- **Config:** PLISFPI category-eligibility master mapping each SKU and HSN to the notified category list; FY 2019-20 base-year register (locked); annual eligible-segment sales register sourced from DMS or SAP CO-PA, by SKU, by month, by distributor GSTIN; GSTR-3B monthly aggregate turnover register; MCA XBRL revenue tag for each financial year; category minimum sales threshold table per scheme guidelines; reconciliation walk template (eligible-segment to GSTR-3B; eligible-segment to MCA XBRL); pre-22-September 2025 vs post-22-September 2025 rate flag per HSN for the GST 2.0 transition.
- **Output:** An annual PLISFPI claim pack with the eligible-segment sales for the claim year, the FY 2019-20 base-year sales, the incremental, the category-threshold test result, the incentive computation up to the cap, and three reconciliation walks (eligible-segment to GSTR-3B; eligible-segment to MCA XBRL audited revenue; eligible-segment to GL sales ledger). The pack is signed off by the company secretary and statutory auditor and submitted to the Project Management Agency. Internally, the same pack feeds the year-end audit committee briefing on PLISFPI incentive accrued, received, and outstanding.

### PLISFPI Mozzarella Cheese Segment Claim Reconciliation

Source: https://www.terra-insight.com/insights/plisfpi-mozzarella-cheese-segment-claim-reconciliation/

- **Problem:** Indian dairy processors approved under PLISFPI Segment 4 (Mozzarella Cheese) must reconcile a mozzarella-only claim base against a much broader dairy portfolio that includes ghee, curd, paneer, block cheese, processed cheese, and cheese analogues — all of which move through the same milk procurement pool, the same plant infrastructure, and often the same GSTR-1 HSN 0406 line-item disclosure. Without a segment-level accounting discipline, the mozzarella claim base gets contaminated with non-eligible cheese revenue, the milk-to-cheese conversion yield is impossible to substantiate against the 10:1 benchmark, and the cold-chain integrity for pizza-chain B2B versus retail cannot be demonstrated during the PMA audit — putting the Segment 4 claim at risk of partial rejection or full disqualification for the year.
- **Logic:** Isolate the mozzarella-only SKU universe using the SKU master with an FSSAI Regulation 2.1.3 mozzarella-compliance flag; extract SKU-level dispatch and secondary-sales data from the DMS by channel (pizza-chain B2B versus modern trade versus general trade). Reconcile milk procurement to vat charge to finished-cheese weight batch-by-batch, benchmarking conversion against the 10:1 ratio and flagging batches beyond tolerance. Split own-plant volume from third-party contract-manufacturing volume (Section 393(1) Sl. 4 arrangements) and exclude the outsourced portion from the claim base. Cross-check the reconciled mozzarella revenue against the Ind AS 108 segment disclosure (if disclosed) or internal management accounts (if bundled). Run the base-year comparison against the beneficiary's FY 2019-20 mozzarella-specific revenue to derive incremental sales for the Segment 4 claim.
- **Config:** SKU master with mozzarella FSSAI compliance flag, format (block / grated / cubed / shredded), pack size, HSN 0406 sub-classification, and channel eligibility; milk procurement register with pooling centre, quantity, fat and SNF grade; vat sheet with batch ID, milk charged, rennet and culture, and finished-cheese weight; finished-goods dispatch register with SKU, channel (pizza-chain B2B / MT / GT), cold-chain temperature log reference; DMS secondary-sales feed by channel; contract-manufacturing register with third-party dairy, quantities, and Section 393(1) Sl. 4 TDS codes 1001 / 1023; Ind AS 108 segment map linking mozzarella SKUs to the disclosed operating segment; FY 2019-20 base-year mozzarella revenue baseline; PMA (Project Management Agency) audit-evidence pack template.
- **Output:** A quarter-end PLISFPI Segment 4 mozzarella claim reconciliation pack: mozzarella-only revenue (own-plant, FSSAI-compliant, cold-chain-verified) for the claim quarter; milk-to-cheese conversion yield for the quarter against the 10:1 benchmark, with batch-level variance flags; channel split between pizza-chain B2B and retail with cold-chain audit evidence; contract-manufacturing exclusion register; incremental sales over FY 2019-20 base year; the Ind AS 108 segment reconciliation bridge; and the PMA audit-evidence pack ready for submission to the Ministry of Food Processing Industries.

### PLISFPI Marine Products Claim Reconciliation

Source: https://www.terra-insight.com/insights/plisfpi-marine-products-claim-reconciliation/

- **Problem:** Segment-3 PLISFPI marine-products beneficiaries — Keventer Agro and similar coastal seafood processors among the 53 named entities under the ₹10,900 crore scheme — file annual incremental-sales claims that pivot on three different evidence streams: APEDA RCMC validity per consignment, EIC pre-shipment lab-test invoices per shipping bill, and FIRC realisation against the export shipping bill via Form 15CA/CB. The three streams sit in three different systems (the APEDA portal, the EIC inspection records, the AD-Category-I bank's FIRC ledger), HSN classification across 0303/0304/1604/1605 governs both the eligible base and the GST treatment under Section 16 IGST Act, and the FY 2026-27 close is the last eligible operational year — meaning the FY 2025-26 and FY 2026-27 claims represent the final tranche of incentive in the scheme tenure.
- **Logic:** Build a PLISFPI Segment-3 ledger keyed by shipping-bill number, RCMC reference, EIC certificate number, FIRC reference, HSN code, and notified plant. Walk every shipping bill through a four-leg validation: RCMC validity on shipping-bill date, EIC pre-shipment certification on consignment, IGST treatment confirmation (LUT bond or paid-and-refund) per Section 16 IGST Act, and FIRC realisation per Form 15CA/CB. Compute the incremental-sales delta against the base-year baseline at HSN level. Cross-foot the eligible-export ledger to the books of account and to the APEDA-administered export realisation register. Surface every shipping bill that fails any leg with the reason code so finance can chase the evidence before the MoFPI claim window closes.
- **Config:** Beneficiary master with MoFPI entity number, segment (Segment-3 marine products), notified-plant list, base-year baseline, and per-HSN incentive percentage; RCMC master with APEDA registration number, validity dates, and product-line scope; shipping-bill feed from ICEGATE with HSN, FOB value, and consignee; EIC certificate feed with inspection number, lab-test invoice reference, and consignment lot; FIRC feed from the AD-Category-I bank with shipping-bill linkage and Form 15CA/CB reference; HSN to GST-treatment mapping (0303/0304/1604/1605); LUT bond status per FY; CA assurance pack template per MoFPI claim instructions.
- **Output:** An annual PLISFPI Segment-3 claim pack: opening eligible-export base (FY 2025-26), incremental eligible exports versus baseline split by HSN, RCMC-validated shipping bills with EIC trail, FIRC realisation status per shipping bill, IGST treatment confirmation per Section 16 IGST Act, and the reconciled per-segment incentive computation. A reconciliation report ties the eligible-export base to the books of account and to the APEDA export realisation register. A stale-evidence register flags shipping bills missing RCMC linkage, EIC certificate, or FIRC. The pack feeds the MoFPI claim filing, the CA assurance certificate, and the year-end Ind AS audit on government-grant accruals under Ind AS 20.

### PLISFPI Processed Fruits & Vegetables Claim Reconciliation

Source: https://www.terra-insight.com/insights/plisfpi-processed-fruits-vegetables-claim-reconciliation/

- **Problem:** PLISFPI Segment-2 beneficiaries — 14 of the 53 named entities including Dabur, Varun Beverages, Tata Consumer Soulful, and three Andhra Pradesh fruit-processing players — must compute an annual incentive claim on incremental sales of eligible processed-fruits-and-vegetables SKUs over the FY 2019-20 base, while the brand-wide turnover sweeps across non-Segment-2 categories (toothpaste, hair oil, honey, snacks). The eligible-sales numerator must be cut at the SKU level, the FY 2019-20 base re-baselined for any structural change, Rule 42 ITC must be reversed on common input services, Section 145B governs the year of incentive recognition, and APMC-mandi and contract-farming procurement must be substantiated in the evidence pack — with the Ministry of Food Processing Industries auditing every claim before disbursement and FY 2026-27 being the final operational year of the six-year scheme.
- **Logic:** Build an eligible-SKU master from the approved PLISFPI scheme application with HSN code, brand SKU code, and eligibility-effective-date; tag every dispatch invoice line in the brand's ERP with the eligible-flag at the SKU level. In parallel, cut the FY 2019-20 base sales for the same eligible-SKU set from the audited annual return and lock it as a fixed-base register. Each operational year, sum SKU-eligible dispatch value net of returns and Section 15(2) qualifying discounts, subtract the locked FY 2019-20 base, and apply the scheme rate for the year to compute the claim. In parallel, run Rule 42 ITC apportionment monthly on common input services and reverse the non-eligible portion; tag PLISFPI receivable separately in the GL for Section 145B year-of-receipt recognition; archive APMC weighbridge slips, mandi-fee receipts, farmer-cum-receipts and contract-farming agreements against the finished-goods batches in the eligible-sales register.
- **Config:** Eligible-SKU master (HSN code, brand code, eligibility effective date, MoFPI amendment reference); FY 2019-20 base register (locked, by SKU and HSN); operational-year dispatch feed from ERP with eligible-flag and Section 15(2) treatment per scheme; brand-wide turnover feed for the Rule 42 apportionment denominator; common input services GL for Rule 42 numerator (advertising, cloud hosting, audit fees, corporate rent, management consultancy); APMC mandi procurement register (weighbridge slip, mandi fee, rural development cess, lot number, farmer-cum-receipt); contract-farming procurement register (farmer agreement, quality certificate, invoice-cum-payment voucher); Section 145B receipt-tracker for year-of-receipt income recognition; deferred-tax tracker for Ind AS 20 vs Section 145B timing differences.
- **Output:** An annual PLISFPI claim pack: operational-year eligible sales by SKU, FY 2019-20 base by SKU, incremental sales, scheme-rate application, claim amount, GST treatment (non-supply receipt), Rule 42 ITC reversal computation with monthly apportionment and annual Rule 42(2) true-up, Section 145B recognition year tagged, and an evidence pack of APMC mandi and contract-farming procurement substantiation by finished-goods batch. The pack feeds the MoFPI claim filing, the GSTR-9 reconciliation, the income-tax return Section 145B disclosure, and the year-end Ind AS 20 deferred-grant note in the audited financial statements.

### PLISFPI RTC/RTE and Millet Segment Claim Reconciliation

Source: https://www.terra-insight.com/insights/plisfpi-rtc-rte-millet-segment-claim-reconciliation/

- **Problem:** PLISFPI Segment-1 reimburses incremental sales of eligible RTC/RTE SKUs over the FY 2019-20 base year, with an additional millet sub-segment for SKUs where millets constitute 15 percent or more of the bill of materials. The 53 named beneficiaries — ITC at slot 29, Britannia, Nestle India, Bikaji, and the other branded food processors — must segregate eligible-SKU sales from non-eligible SKUs in the GL, tie the eligible-SKU revenue to GSTR-1 HSN-level reporting for the claim period, evidence the millet ratio against ingredient bill of materials and batch production records, and audit-confirm it through Ind AS 108 segment disclosures, all by the claim filing window for each operational year through FY 2026-27. A mismatch between the claim's eligible-sales line and the segment-revenue line in the audited financials invites rejection or clawback at MoFPI certification.
- **Logic:** Build an eligible-SKU master keyed by article number, HSN code, BOM hash, and segment (RTC/RTE base versus millet sub-segment). For every SKU, parse the bill of materials from the manufacturing execution or SAP PP feed and compute the millet ratio at input-weight level; classify into millet-eligible (ratio at or above scheme guideline) or RTC/RTE-eligible (below the millet threshold). Match each invoice line from secondary sales and direct dispatch to the eligible-SKU master by article number, accumulate eligible-segment revenue by quarter, and cross-foot to the GSTR-1 HSN summary for the same period and HSN code. Compute incremental sales as the difference between the operational year and the FY 2019-20 base year for the same eligible-SKU set; apply the scheme percentage in force for the operational year; and reconcile the eligible-segment revenue back to the Ind AS 108 audited segment disclosure for the same period.
- **Config:** Eligible-SKU master with article number, finished HSN, scheme segment flag (RTC/RTE base / millet sub-segment / non-eligible), millet ratio, BOM reference, batch production record reference; ingredient master with HSN, millet classification, supplier, and procurement-ledger linkage; FY 2019-20 base-year sales register frozen at scheme inception (with adjustments for portfolio rationalisation per scheme guideline); period sales feed by article by quarter; GSTR-1 HSN summary feed by quarter; manufacturing batch production record by SKU by batch; Ind AS 108 segment disclosure mapping per article into reportable segments; scheme percentage matrix by operational year FY 2021-22 through FY 2026-27.
- **Output:** A claim-filing pack per operational year: eligible-segment revenue by quarter reconciled to GSTR-1 HSN summary and to the Ind AS 108 audited segment line; millet sub-segment revenue with per-SKU BOM and batch-record evidence; incremental-sales calculation against the FY 2019-20 base; incentive computation at the scheme percentage matrix; and an audit pack supporting MoFPI certification. The pack also feeds the brand's CARO 2020 disclosure on government grants and the Ind AS 20 accounting treatment for the incentive receipt — recognised on the basis of reasonable assurance that the entity will comply with the conditions attaching to the grant and that the grant will be received.

### PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem

Source: https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india/

- **Problem:** An Indian manufacturer's three-way match between PO, GRN and vendor invoice fails on 60-75% of incoming invoices because of price tolerance breaches, partial GRN drift, GST inclusive/exclusive confusion, and vendor-master errors — pushing the AP team into a perpetual exception backlog and delaying MSME payments past the Section 43B(h) 45-day window.
- **Logic:** Apply per-item-category tolerance bands (price 0-5%, quantity 0-3%, GST 0%) at PO-GRN-invoice junction; classify failures into six variance codes (UNDER_INVOICED, OVER_INVOICED, PARTIAL_QTY, GST_MISMATCH, VENDOR_PAN_MISMATCH, RATE_VARIANCE) with routing rules per code; layer Section 393(1) Sl. 8(ii) year-to-date threshold tracking per vendor PAN; flag MSME vendors for 45-day clock from GRN date.
- **Config:** Item-category-wise tolerance band table, vendor master with PAN/GSTIN/MSME flag, Section 393 code mapping (1002 contractor, 1012 purchase above ₹50L), GST-inclusion default per PO type, GRN-to-invoice matching window in days, and exception ageing buckets (0-30, 31-60, 60-90, 90+ days).
- **Output:** A daily AP close where matched invoices route to payment, exceptions route to the queue by variance code, MSME 43B(h) deadlines surface before they breach, Section 393(1) Sl. 8(ii) threshold crossings trigger TDS deduction on the next invoice automatically, and the monthly exception rate trends toward sub-15%.

### Poultry Contract Farming Reconciliation — Broiler India Cornerstone

Source: https://www.terra-insight.com/insights/poultry-contract-farming-reconciliation-broiler-india/

- **Problem:** A broiler integrator running 30,000 contract farmers at 5,000-bird shed capacity, six 45-day cycles per year, and 900 million birds of annual placement must reconcile the DOC issue register (5,000 chicks per shed at Rs 30 per DOC illustrative), the feed issue register (approximately 4 metric tons of pre-mix per shed per cycle at illustrative Rs 32,000 per MT), the medicine and vet supply register, the bird-lift log against a target 4,500 birds per shed lifted (10 percent mortality allowance), the FCR-linked grower payment (illustrative Rs 8 to 10 per bird lifted, or Rs 36,000 to Rs 45,000 per shed per cycle), the Section 194C code 1023 or 1001 TDS remitted on the service consideration (illustrative Rs 720 to Rs 900 per shed per cycle), and the Section 143 CGST return-of-inputs closure via quarterly Form GST ITC-04 for the DOC, feed, medicine, and returned-broiler challan streams. Manual reconciliation across 180,000 shed-cycles per year loses per-cycle FCR variance, misses grower entity classification for TDS coding, and leaves Section 143 challans unclosed beyond the quarter — exposing the integrator to Section 201 short-deduction TDS demands, Section 74 GST retroactive liability on deemed supplies, and Section 43B(h) MSME payables disallowance on the upstream maize and soya meal feed input chain.
- **Logic:** Build a grower master keyed on grower ID, shed ID (a single grower may run multiple sheds), PAN, entity type (Individual/HUF versus other resident), bank account, and TDS code (1001 versus 1023). Build a cycle master with cycle number, placement date, target lift date, DOC lot, feed formulation, and FCR benchmark band by strain and season. Ingest the DOC dispatch challan (Rule 55 format), the feed dispatch challan, the medicine dispatch challan, and the bird-lift return challan into a cycle-shed key. Compute derived FCR per shed per cycle as (feed dispatched in kg minus feed returned or wasted) divided by (birds lifted x average lift weight in kg). Apply the FCR-linked performance schedule to the base per-bird rate and derive the grower's service consideration for the cycle. Apply the code 1001 or 1023 TDS at 1 or 2 percent on the service consideration keyed to grower entity type, remit against the grower's PAN to TRACES, and net-settle to the grower's bank. Aggregate Section 143 challan tally by grower for each reporting period and file Form GST ITC-04 on the notified schedule (half-yearly for principals Above Rs 5 crore turnover). Flag any Section 143 challan more than 270 days old as a proactive alert well before the 1-year deemed-supply trigger.
- **Config:** Grower master with grower ID, shed ID, GPS location, PAN, entity type, bank account, TDS code (1001 or 1023 or the material-not-supplied variants where relevant), and previous-cycle FCR history; shed master with shed capacity in bird count, floor area, and equipment tier (open-sided versus environmentally controlled); DOC batch master with hatchery source, strain (Ross 308 versus Cobb 500), batch date, and reference FCR benchmark; feed formulation master with starter, grower, and finisher composition and lot pricing; per-cycle placement schedule tied to processing plant slaughter capacity; FCR benchmark band by strain and season (typical band 1.6 to 1.9 with a 5 percent tolerance either side); mortality allowance band (typically 8 to 10 percent); base per-bird payment schedule and FCR-linked performance adjustment matrix; Form GST ITC-04 filing calendar (half-yearly at scale, per Notification 35/2021); Section 143 challan aging tracker with a 270-day proactive alert; upstream feed supplier master with Section 43B(h) MSME flag on maize, soya meal, DORB, and vitamin premix vendors.
- **Output:** A per-cycle contract farming reconciliation pack for the integrator's finance and operations chair: DOC and feed issue tally by shed, medicine and vet supply tally by shed, bird-lift return tally by shed with average live weight and FCR derivation, grower payment schedule with base plus FCR performance adjustment and mortality reconciliation, TDS deduction ledger keyed to code 1001 or 1023 with Form 26Q or 26AS reconciliation, and a Section 143 challan aging register showing every outbound challan matched to an inbound closure. Quarterly output: Form GST ITC-04 filing base with the full challan set, unclosed-challan aging report, and an FCR performance dashboard by shed and region. Year-end output: the integrator's grower P&L aggregated by shed, the Section 43B(h) MSME payables aging on upstream feed vendors, and the GSTR-9 reconciliation of the Section 143 free-issue cycle against the GST audit's expected trail.

### IEX and PXIL Power Exchange Reconciliation for Indian Open-Access Buyers

Source: https://www.terra-insight.com/insights/power-exchange-iex-pxil-reconciliation-india/

- **Problem:** An Indian open-access buyer trading on IEX and PXIL across DAM, TAM, GTAM and RTM segments faces a four-rail reconciliation: trade confirmations arrive per exchange per segment per day in 96 fifteen-minute blocks (or 48 half-hour blocks for RTM), clearing-bank pay-in or pay-out lands on T+1 as a single net figure that aggregates many trades, exchange margin block-and-release moves daily independent of trade settlement, and DSM deviation charges from the regional pool account land on a separate monthly cycle linked to the SLDC interface meter.
- **Logic:** Reconcile each trade confirmation against the clearing-bank pay-in or pay-out by trade ID and value date, decompose the daily net into per-block components, tie each block to the physical schedule submitted to the SLDC and to the metered drawal or injection, surface DSM deviation as the gap between scheduled and metered quantum priced at the frequency-band rate, and split the exchange fee invoice into GST-bearing fee plus GST-exempt transmission line for ITC routing.
- **Config:** Trading-member account master per exchange with clearing-corporation reference, segment configuration (DAM 96 blocks, RTM 48 blocks, TAM contract windows, GTAM RPO eligibility flag), price-band table from CERC market-coupling rules, exchange-fee schedule per segment, margin ledger configuration with block-on-bid and release-on-clearing rules, SLDC scheduled-quantum file ingest, interface meter file ingest, DSM rate table by frequency band, GST treatment table (exchange fee taxable SAC 997159 at 18%, transmission exempt per electricity notification), and bank pay-in or pay-out narration patterns for each clearing corporation.
- **Output:** A daily reconciled view per exchange per segment showing trade-confirmed quantum, scheduled quantum, metered quantum and DSM deviation per fifteen-minute block, monthly exchange-fee invoice reconciled to cleared volume with GST and ITC routing, a margin ledger showing block, release and net held by clearing corporation, transmission and SLDC charges tied to the relevant transmission-utility bill, and a per-drawee landed-cost-per-unit number that ties exchange-cleared price plus transmission plus SLDC plus DSM.

### PPI / Wallet-on-UPI Interchange: 1.1% Above ₹2,000 for Indian Merchants

Source: https://www.terra-insight.com/insights/ppi-wallet-on-upi-interchange-1-1-percent-india/

- **Problem:** Indian merchants treat UPI as a single zero-MDR rail and so do not reconcile interchange on its sub-rails. PPI/wallet-on-UPI carries 0.5%-1.1% interchange on tickets above ₹2,000 (NPCI circular 24 March 2023, effective 1 April 2023) yet the deduction lands under the generic UPI parent in the settlement file, hiding the cost. As wallet-on-UPI mix grows in D2C, food delivery, and OTT cohorts the unbilled-looking deduction accumulates materially.
- **Logic:** Reconciliation splits the UPI parent bucket into three children — bank-account UPI (zero interchange), RuPay-credit-on-UPI (~2% above ₹2,000), and PPI/wallet-on-UPI (0.5%-1.1% above ₹2,000) — using the payment-instrument sub-type field exposed in the gateway settlement payload. Each child has its own expected interchange schedule keyed on ticket size and merchant category code; the engine recomputes the expected deduction per transaction and raises a variance when actual deviates from expected.
- **Config:** Rail-split rule on the UPI parent method using the instrument sub-type field; interchange-schedule table keyed on rail + merchant category code + ticket band (NIL ≤ ₹2,000, 0.5%-1.1% above ₹2,000); UPI_INTERCHANGE variance class with tolerance threshold; refund-interchange-retention flag to detect cases where wallet interchange was not reversed on a refunded transaction; monthly GST-invoice matcher to GSTR-2B for the 18% ITC line.
- **Output:** A per-transaction wallet-on-UPI interchange variance report with recoverable over-charges, a rail-mix dashboard tracking bank-account vs RuPay-credit vs PPI share month-on-month for CFO visibility, refund-interchange retention exceptions for gateway support tickets, and an ITC-claim schedule for the 18% GST on interchange.

### PPM Quality Metric for Auto-Component Suppliers: What Finance Teams Need to Know

Source: https://www.terra-insight.com/insights/ppm-quality-metric-auto-component-finance-india/

- **Problem:** PPM (parts-per-million) is the contractually anchored quality metric in OEM-Tier 1 supply, but its financial consequences are run by finance — graduated penalty bands deducted from running settlement, sorting/rework back-charges from resident-engineer or third-party agency containment, 8D-linked debit holds, Section 34 GST credit notes on returned goods within the 30-November window, and supplier-rating downgrades that affect future allocation.
- **Logic:** Compute the supplier's own rolling-12-month PPM from internal rejection records per OEM and per part-programme; compare to OEM-asserted PPM and contractual threshold; validate the asserted penalty band against the contractual schedule; tie sorting back-charges to the sorting authorisation, agency timesheet and quantity sorted; reconcile returned goods to a Section 34 credit note within the 30-November cutoff; keep penalty, sorting and goods-return charges in separate buckets so they are not double-netted; cross-reference each debit to its 8D closure status to age the dispute window.
- **Config:** Part-programme master with contractual PPM threshold and penalty band schedule, OEM-specific rolling-window rule, quality-notification taxonomy keyed by rejection slip and 8D ID, internal rejection register, sorting-authorisation register, GST routing splitting goods credit notes (Section 34, 30-November cutoff) from penalty and sorting recoveries, debit-dispute calendar.
- **Output:** A per-OEM PPM finance dashboard showing supplier-computed PPM versus OEM-asserted PPM by part-programme, applicable penalty band with rupee impact validated against the contractual schedule, sorting back-charges matched to authorisations, Section 34 credit-note queue with cutoff watch, debit-dispute queue with 8D status overlay, and a running supplier-rating exposure flag.

### Predatory Lending App Detection in Bank Statements: What Indian Lenders Check

Source: https://www.terra-insight.com/insights/predatory-lending-app-detection-india/

- **Problem:** A borrower's true debt burden may be significantly understated in formal credit bureau reports if active loan obligations are with unregistered or informal digital lending apps. Bank statements reveal these obligations through disbursal credits and repayment debits that do not appear in CIBIL or CRIF bureau pulls.
- **Logic:** Match transaction descriptions against a list of 90+ predatory and high-cost loan app names, including entities that have been banned or flagged by RBI and those that have re-launched under alternate names. Record each matched transaction with count, total debit, total credit, and top five matched app names. Correlate inward credits (loan disbursals) with outward debits (repayments) to estimate hidden obligation levels.
- **Config:** Enable for NBFC and digital lending underwriting workflows. Update the app list quarterly to capture new entity names following re-launches post-ban. Cross-reference with over-leverage detection to surface total visible obligation burden.
- **Output:** Predatory lending risk section in the credit report with transaction count, total inward (disbursals), total outward (repayments), top five matched app names, and a combined obligation estimate for credit officer review.

### PLC (Preferential Location Charges) GST Treatment for Real Estate

Source: https://www.terra-insight.com/insights/preferential-location-charges-plc-real-estate-gst-india/

- **Problem:** An Indian real estate developer selling under-construction non-affordable apartments collects PLC (preferential location charges — higher floor, corner unit, park-facing, pool-view) as a distinct line on the buyer's demand-letter schedule, but the GST treatment on PLC is often mis-recorded — either as a separate 18% service supply, or as an out-of-GST premium, or bundled at the wrong composite rate — creating a triangular reconciliation exposure across the sale deed, the composite GST invoice and the RERA Form 4 progress report.
- **Logic:** Apply CBIC Circular 197/09/2023-GST composite-supply rule — bundle PLC, floor-rise, car parking and common-area charges with the principal apartment sale under Section 8 CGST + Schedule II Entry 5(b), tax at the same effective rate as the principal (5% CGST for under-construction non-affordable, 1% for affordable, NIL for post-CC), embed the 1/3rd deemed land deduction in the effective rate, tie every PLC rupee across sale-deed line-item, composite GST invoice line and the developer's PLC revenue sub-ledger.
- **Config:** Project master keyed by RERA registration with construction status flag (under-construction vs post-CC); price sheet per unit with base consideration + PLC schedule by floor / view / orientation + car parking + floor-rise; composite invoice template with HSN 9954, effective rate (5% / 1% / NIL) per project status; composite-supply register aggregating all bundled line-items per invoice; RERA Form 4 progress report ingestion tied to customer collection register; buyer-side TDS 26QB reconciliation tied to the composite consideration.
- **Output:** A per-unit reconciliation view showing the base consideration, the PLC line-item, the aggregate composite consideration and the applicable GST rate with clear under-construction vs post-CC flag; a monthly composite-supply register tie-out to Form GSTR-1 outward supply table; a quarterly RERA Form 4 progress report tie-out showing PLC-inclusive collections in escrow; an audit-ready evidence pack per unit linking the sale deed PLC line, the composite GST invoice line and the developer's revenue-recognition entry.

### Premium Card Fee Hidden in UPI Appearance: Fee-Schedule Extraction

Source: https://www.terra-insight.com/insights/premium-card-fee-embedded-in-upi-lookalike-streaming-payment-gateway-india/

- **Problem:** Streaming subscription checkouts frequently display a 'Pay via UPI' tile that in practice routes premium credit cards through UPI-on-cards rails at 1.5% to 2.4% MDR plus 18% GST. Finance teams that reconcile MDR by tile label — assuming 'UPI = zero' — under-book gateway cost, under-recover input tax credit, and produce fee schedule mismatches that auditors flag against the 30/12/2019 Zero MDR notification.
- **Logic:** Fee extraction reads the network field, card type field, and BIN prefix from every settlement line, not the checkout tile label. A rules table maps each combination — UPI plus VPA is zero MDR; RuPay Debit is zero MDR; RuPay Credit routed through UPI is 1.5% to 2.4%; American Express, Visa premium, or Mastercard premium is the corresponding published card schedule — to the expected MDR band. Each line's computed MDR is compared to the actual fee deducted in settlement, and variances beyond a tolerance are opened as exceptions with the specific rule that failed.
- **Config:** Settlement network dictionary (UPI, RuPay Debit, RuPay Credit, Visa Debit, Visa Credit including Signature and Infinite, Mastercard Debit, Mastercard Credit including World and World Elite, American Express, Diners), UPI-on-cards routing flag, MDR schedule table per network per MCC per card tier, GST rate 18% for aggregator services, and the merchant's tax invoice from GSTR-2B matched by GSTIN and invoice number.
- **Output:** Fee reconciliation register keyed by transaction with expected MDR versus actual MDR versus GST versus ITC-claimable amount; variance report grouped by network and card tier; input tax credit schedule for GSTR-3B; and an audit-ready trail showing the Zero MDR notification is honoured on UPI and RuPay Debit rails, with the priced rails booked at their contractually agreed schedules.

### Premium Card Misrouting to the 3% Slab: A BIN-Tier Audit for Indian Merchants

Source: https://www.terra-insight.com/insights/premium-card-misrouting-3-percent-slab-bin-audit-india/

- **Problem:** Gateway settlement files apply a single deducted MDR per transaction without showing the merchant the card BIN or the product tier that justified the slab. Standard consumer-tier credit cards get auto-routed to the 3% premium slab whenever the BIN classifier flags them as signature, infinite, rewards, commercial, Amex, or Diners — and the merchant has no per-transaction visibility to challenge it. On a credit-heavy hospitality, OTA, or luxury-retail merchant, the misrouted share routinely sits at 5-20 percentage points of credit volume, accumulating silently every settlement cycle.
- **Logic:** BIN-tier reconciliation joins each settlement-file transaction to a BIN-product mapping (acquirer-provided CSV or third-party BIN database), recomputes the expected slab per transaction using the merchant's contracted rate card keyed on network plus product tier, and raises a CARD_TIER_MISMATCH variance when the actual slab deducted exceeds the expected slab. A 90-day rolling audit window matches the typical gateway retrospective-adjustment cut-off, and a per-BIN volume ranking surfaces the highest-recovery BINs first.
- **Config:** BIN-tier rule per network (Visa / Mastercard / RuPay / Amex / Diners) mapping issuer BIN to product tier (consumer / premium-signature-infinite / rewards / commercial / corporate); CARD_TIER_MISMATCH variance class with a 5-bps slab-delta tolerance to suppress rounding noise; refund-MDR retention flag and 90-day rolling recovery window for retrospective gateway disputes; GST-credit-note matcher to GSTR-2B for the 18% reversal line.
- **Output:** A per-BIN misrouting report ranking BINs by recoverable amount, a CFO-facing card-tier mix dashboard (consumer vs premium vs commercial vs Amex/Diners share month-on-month), a dispute-pack export per gateway with BIN evidence and expected-vs-actual slab calculation for retrospective adjustment requests, and a GST-credit-note reconciliation schedule against GSTR-2B.

### Premium / Signature / Infinite Credit Card MDR: Interchange Tier Risk for Indian Merchants

Source: https://www.terra-insight.com/insights/premium-signature-infinite-card-mdr-india/

- **Problem:** Luxury hotel chains, airline OTAs, jewellery retailers, and premium ecommerce merchants absorb material leakage because the issuer interchange on premium, signature, and infinite credit cards is higher than the consumer credit interchange, and Indian gateways pass the differential to the merchant by either routing the entire premium card to the published 3 percent slab or applying a non-qualified surcharge above the contracted consumer rate. The merchant sees one blended MDR column and cannot separate premium from consumer billing without a per-transaction BIN-tier join. Auto-classification errors that route consumer-tier signature cards to the premium slab compound the leakage by 0.5 to 1 percentage point per affected transaction.
- **Logic:** For every credit card transaction on the settlement file, derive the issuer product tier from the BIN against the acquirer schedule rather than from the gateway classification field alone. Compute expected fee as contracted slab for that BIN tier and network multiplied by gross. Compare to actual fee column, including any non-qualified surcharge line. Aggregate effective rate per network per card tier monthly. Flag consumer-tier transactions billed above the contracted consumer slab by more than a 5 basis point band, and flag premium-tier transactions billed at a slab the merchant agreement does not name. Cross-reference EMI-converted premium-card transactions for slab stacking.
- **Config:** Acquirer BIN-tier reference table refreshed quarterly, with first-six-digit ranges marked consumer-credit, premium-rewards (signature, infinite, world, world-elite), commercial, premium-corporate. Per-network contracted slab table for consumer, premium, commercial, EMI, international. BIN-tier rule in the MDR rule set per gateway and per network. Per-transaction expected-fee column versus actual-fee column including non-qualified surcharge. Monthly effective-rate-by-tier report by gateway. Slab-stacking detector for EMI-converted premium-card transactions. Recovery register feeding the merchant-fee leakage class for raising structured disputes against the gateway.
- **Output:** A monthly effective-rate matrix by network by card tier showing where the consumer tier is reading above contracted consumer slab and where the premium tier is reading above any contracted premium slab. A per-gateway BIN-classification variance log listing transactions where the gateway tier differs from the acquirer tier. A non-qualified surcharge audit log capturing every surcharge line above the rate column. A standing dispute register tracking BIN-tier claims filed and accepted, with recovery quantified at the monthly and annual run rate.

### Prepaid Card MDR Reconciliation for Indian Merchants

Source: https://www.terra-insight.com/insights/prepaid-card-mdr-india/

- **Problem:** Domestic prepaid cards in India ride the gateway's standard domestic card slab — Cashfree explicitly includes them in the 1.6% promo set alongside UPI, credit/debit cards, NetBanking and wallets, and Razorpay and PayU bill them at the same 2% blended domestic rate. But the gateway taxonomy and the upstream wallet/super-app flow frequently mis-classify a card-form-factor prepaid transaction as PPI/wallet, which sits on a different schedule (0.5%–1.1% interchange above ₹2,000 on UPI, or the gateway's wallet rate off UPI). The slab is not the leakage source. The classification is.
- **Logic:** Reconciliation joins the gateway settlement file against the merchant order management system and the bank statement, then runs four checks per cycle. Check one isolates every transaction the gateway has labelled prepaid card and verifies the BIN is on a Visa, Mastercard or RuPay scheme issued by an Indian bank or domestic PPI issuer. Check two flags transactions where the parent rail is wallet or PPI but the underlying instrument BIN identifies as a card — that mismatch determines whether the transaction belongs in the card slab or the PPI interchange schedule. Check three cross-references the international card BIN list against any prepaid card billed at the international slab. Check four reconciles the per-instrument effective rate (fees divided by per-instrument volume) against the contracted domestic card slab and isolates any cohort where the effective rate exceeds the contract by more than 0.15 percentage points. Every check carries GST on MDR as a separate line.
- **Config:** Gateway settlement-file ingestion with payment_id and order_id joins to the OMS; an instrument-classification rule set distinguishing domestic prepaid card from PPI/wallet using BIN, network code and instrument sub-type fields; a domestic-card slab benchmark per contracted gateway (Cashfree 1.95% standard or 1.6% promo, Razorpay/PayU 2% standard, enterprise negotiated rates carried separately); a PPI/wallet interchange schedule (0.5%–1.1% above ₹2,000 on UPI, gateway wallet rate off UPI); an international BIN list cross-reference; per-instrument effective-rate computation; refund non-reversal check; and a monthly GST invoice matcher for input tax credit.
- **Output:** A monthly prepaid card fee scorecard with per-BIN-cohort effective rate, an exception list of every transaction labelled PPI/wallet where the underlying instrument was a card (or labelled card where the underlying instrument was a non-card PPI), a domestic-versus-international classification audit, a refund-MDR drag estimate, a reconciled GST-on-MDR claim ready for GSTR-2B, and an annual exposure number the controller can take into the next quarterly gateway review.

### Prepaid and Postpaid Revenue Recognition for Indian Telecom under Ind AS 115

Source: https://www.terra-insight.com/insights/prepaid-postpaid-revenue-recognition-telecom-india/

- **Problem:** Indian telecom operators must apply Ind AS 115 across two opposite revenue shapes: prepaid recharge proceeds that must sit in unearned revenue and be recognised on consumption, and postpaid bill-cycle recognition. The reconciliation must tie cash recharge inflows to unearned-revenue movement and consumption events, present IUC pass-through gross or net based on principal-vs-agent analysis, withhold Section 393(1) Sl. 6(i) contractor code 1024 (2% for company deductees) TDS on enterprise postpaid, evaluate Section 9(5) CGST where the operator intermediates third-party services, and discharge 18 percent GST on telecom services across both streams.
- **Logic:** For prepaid: recognise the recharge inflow as a contract liability under Ind AS 115; track consumption per subscriber against the recharge balance; release the liability to revenue as minutes, data and validity are consumed; recognise the residual at validity expiry; for postpaid: bill on cycle and recognise revenue for committed services delivered; apply principal-vs-agent analysis on IUC pass-through and present revenue gross or net consistently; withhold Section 393(1) Sl. 6(i).D(b) code 1024 TDS at 2 percent on enterprise postpaid net of GST and tie to Form 26AS credit by customer PAN; evaluate Section 9(5) CGST for any third-party digital services intermediated through the operator's platform; discharge 18 percent GST on telecom services.
- **Config:** Subscriber master with prepaid vs postpaid tag and contract terms; recharge ledger with unearned-revenue posting; consumption ingestion from billing platform; postpaid bill-cycle calendar; Ind AS 115 principal-vs-agent IUC policy; Section 393(1) Sl. 6(i).D(b) code 1024 TDS rule on enterprise customers; Form 26AS reconciliation by customer PAN; Section 9(5) CGST scope assessment for intermediated services; 18 percent GST classification for telecom service.
- **Output:** A reconciled telecom revenue position showing prepaid recharge inflow tied to unearned-revenue liability movement and consumption release, postpaid bill-cycle revenue tied to receivables and collections, IUC presentation gross or net per the principal-vs-agent policy, enterprise Section 393(1) Sl. 6(i).D(b) code 1024 TDS receivable per customer tied to Form 26AS, and 18 percent GST output liability tied to GSTR-1 and GSTR-3B.

### Architect and Engineer Professional Fees TDS: Section 393(1) Sl. 15 (Legacy 194J)

Source: https://www.terra-insight.com/insights/professional-fee-architect-engineer-tds-section-194j-real-estate/

- **Problem:** An Indian real estate developer paying architects, structural engineers, MEP consultants and project management consultants for a portfolio of registered projects must deduct TDS at 10% on professional fees under Section 393(1) Sl. 15 code 1005 (legacy 194J), track ₹30,000 per FY per PAN aggregate thresholds across multiple invoices, correctly bifurcate composite contracts between 194J (design) and 194C (execution) where the same vendor performs both, and tie each consultancy payment through TDS challan, Form 26Q quarterly return and the vendor's Form 26AS credit trail — with penalties for late deduction, non-deposit and non-filing.
- **Logic:** Route every consultancy invoice through a PAN-tagged AP intake that flags Section 194J category, computes 10% TDS on gross fee (2% for pure technical services), applies threshold logic on FY-to-date aggregate per PAN, blocks payment until the correct TDS category is confirmed for composite contracts, ties challan deposit to books TDS payable, and reconciles Form 26Q filing to the AP-generated per-PAN payment schedule.
- **Config:** Vendor master with PAN and Section 194J flag; FY-to-date payment ledger per PAN per category (194J vs 194C); TDS rate table by payment code (1005 = 10%, 1005-tech = 2%, 1023 = 1%/2%); composite-contract bifurcation rule requiring separate invoice line for design vs execution; Form 26Q quarterly generator with per-PAN payment-code breakup; Form 26AS ingestion for vendor-side confirmation.
- **Output:** A per-vendor Section 194J ledger showing FY-to-date gross fee, TDS deducted, TDS challans deposited, Form 26Q reported and Form 26AS credit received per PAN; monthly exception report listing (a) vendors crossing ₹30,000 threshold requiring retroactive TDS, (b) composite invoices lacking bifurcation, (c) challan-to-books gaps, (d) 26Q-to-26AS mismatches; an audit-ready evidence trail linking every architect or engineer payment to its downstream statutory footprint.

### Professional Tax State-wise Reconciliation for Indian Employers

Source: https://www.terra-insight.com/insights/professional-tax-state-wise-reconciliation-india/

- **Problem:** A six-state employer with 920 employees runs PT cycles in parallel across Karnataka, Maharashtra, Gujarat, West Bengal, Tamil Nadu, and Telangana, each with different slabs, different cut-offs, and different portals. Without state-wise reconciliation, employees get assigned to the wrong state on transfer, the wrong slab is applied, and one state's deposit gets missed without anyone noticing until the inspection notice arrives.
- **Logic:** Carry a per-employee state-of-work field on the payroll register every month. Compute PT per employee using the slab schedule of the assigned state. Aggregate per-state totals and reconcile against the per-state deposit. Surface variances per state per month — missing state-of-work value, slab-master gap, deposit-not-made, deposit-amount-mismatch.
- **Config:** Per-employee state-of-work master, per-state slab schedule (Karnataka, Maharashtra, Gujarat, West Bengal, Tamil Nadu, Telangana, and any others where the employer is registered), per-state cut-off calendar, deposit reference master, and a per-state-per-month reconciliation MIS.
- **Output:** Clean state-wise PT filings, every employee assigned to the correct state, every slab applied correctly, every state's deposit made on time, and a defensible audit trail showing per-employee PT contribution from payroll register through state-level deposit.

### PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers

Source: https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges/

- **Problem:** PSU bank statements produce unreliable extraction results due to legacy core banking format variation, post-merger narration inconsistencies, and branch-printed PDFs that require OCR — causing payment channel misclassification and income errors.
- **Logic:** Dedicated bank-specific parsers handle each PSU bank's distinct column layout, date format, and narration prefix set, including full legacy narration mappings for accounts migrated from merged entities.
- **Config:** The parser library must include dedicated profiles for each major PSU bank and their merged predecessor entities, updated when new statement format variants are identified.
- **Output:** A transaction table with correctly classified payment channels and income categories, matching the accuracy level achieved for private bank PDFs rather than falling back to generic unclassified output.

### QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L

Source: https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation/

- **Problem:** A multi-outlet QSR chain runs across multiple states, multiple GSTINs, multiple banks, and a mix of owned and franchised outlets — with central kitchen flows, royalty and brand-fund fees, and per-outlet P&L all needing to reconcile to chain-level GSTR returns and treasury position.
- **Logic:** Reconcile at three levels: per-outlet (POS to bank to GST), per-state (aggregate by GSTIN), and chain (consolidated treasury and P&L). Match commissary issues to outlet receipts and theoretical consumption from POS recipes. Reconcile royalty and brand-fund invoices to franchisee gross sales feed. Distribute allocated costs by sales weight, then verify chain revenue ties to the sum of GSTR-1 filings across all GSTINs.
- **Config:** Per-outlet POS connectors; commissary inventory and recipe master; royalty rate card by franchisee tier; multi-GSTIN state mapping; multi-bank statement ingestion; per-outlet cost allocation engine; chain-level rollup that reconciles to consolidated GSTR returns.
- **Output:** Per-outlet P&L with cost-of-goods variance, chain-level treasury position, multi-GSTIN GSTR reconciliation, and a wastage and royalty tracking ledger that surfaces underperforming outlets and disputed franchisee invoices.

### Quality Cost Accounting for Auto-Component Manufacturers: PAF Model and Indian Tax Treatment

Source: https://www.terra-insight.com/insights/quality-cost-accounting-auto-component-manufacturing-india/

- **Problem:** Quality-related costs at an Indian auto-component Tier-1 routinely run 4-8 percent of net sales but live scattered across HR (training), plant maintenance (calibration), QA (lab consumables), sales returns (warranty), and admin (8D consultancy). Without a Prevention-Appraisal-Failure (PAF) accounting structure, finance cannot see that external-failure spend is consuming the prevention budget many times over — until OEM PPM scorecards downgrade and allocation reviews start.
- **Logic:** Map every quality-related GL line to one of four PAF buckets: prevention (training, supplier development, design FMEA, capability studies); appraisal (inspection labour, gauge calibration, lab testing); internal failure (scrap, rework, sorting on supplier-detected defects); external failure (warranty, OEM debit notes, line-stop, recall, FOMP). At month-end accrue internal-failure scrap to part-programme, external-failure warranty to a rolling 12-month provision, and OEM debit notes to the period of dispatch they relate to. Tax overlay: Section 34 GST credit notes within the 30 November cutoff for returned goods; Section 393(1) Sl. 6(i) codes 1023/1024 / Sl. 6(iii).D(b) code 1027 TDS for 8D consultancy and lab invoices; Section 393(2) Sl. 17 code 1057 for foreign labs. Report as percent of net sales monthly with rolling 12-month trend.
- **Config:** Chart of accounts segmented into four PAF GL ranges; part-programme master keyed to OEM, plant, programme and commodity; warranty provision policy with failure-rate and unit-cost-of-replacement assumptions; sorting-authorisation register tying agency invoices to quality-notification IDs; calibration master holding NABL lab schedules; supplier-development project ledger; month-end PAF accrual routine; rolling 12-month COQ trend in the management pack.
- **Output:** A monthly Cost-of-Quality dashboard showing prevention/appraisal/internal-failure/external-failure as absolute rupees and percent of sales, per programme and per OEM; tax-correct treatment of warranty replacements, sorting back-charges and lab invoices; a defensible PAF audit trail to the part-programme level; and an early-warning signal when external-failure spend rises versus prevention.

### Quick Commerce Platform Reconciliation: Blinkit, Zepto, Instamart Settlement Cycles

Source: https://www.terra-insight.com/insights/quick-commerce-blinkit-zepto-instamart-reconciliation-india/

- **Problem:** D2C brands operating across quick commerce platforms in hybrid consignment plus marketplace plus direct-buy models face a multi-cadence reconciliation problem — T+1 daily sale-through on consignment SKUs, T+15 to T+30 wholesale settlements on direct-buy, separate ad-spend invoices, FOC promotion replacement tracked outside billed inventory, and Section 9(5) versus Section 52 versus ordinary GST treatment varying by SKU category — where unstructured reconciliation absorbs 2 to 6 percent of channel spend invisibly across slotting, ad, and FOC layers.
- **Logic:** Operate three parallel reconciliation streams per quick commerce platform: daily consignment sale-through matching, fortnightly direct-buy PO-to-invoice-to-payment, and per-campaign ad-spend PO-to-invoice. Track FOC stock as a separate ledger with replacement matching. Apply Section 9(5) GST treatment only on notified categories where applicable; Section 52 TCS on marketplace categories; ordinary B2B GST on direct-buy. Match Section 393(1) Sl. 8(v) code 1035 TDS where applicable for marketplace facilitations.
- **Config:** Quick commerce platform adapters with consignment, wholesale, ad-spend, and FOC parsers per platform, SKU master tagged by commercial model (direct-buy, consignment, marketplace), dark-store stock ledger per SKU per location, campaign PO ledger with performance-report matching, FOC stock ledger, and Section 9(5) and Section 52 category mapping.
- **Output:** Reconciled receivable ledger per platform across consignment, direct-buy, and marketplace streams; ad-spend variance versus campaign PO surfaced per campaign; FOC replacement gap quantified per dark store; Section 9(5), Section 52, and Section 393(1) Sl. 8(v) code 1035 deductions cleanly mapped to the right GL; board-ready net realisation view per SKU per commercial model.

### Quick Commerce FMCG Settlement Reconciliation in India

Source: https://www.terra-insight.com/insights/quick-commerce-fmcg-settlement-reconciliation-india/

- **Problem:** An Indian FMCG brand selling ₹10 to ₹15 crore monthly across three quick commerce platforms — Blinkit, Zepto and Swiggy Instamart — receives settlement files on a T+7 to T+14 cycle with different formats per platform, seven deduction categories per file, Section 52 TCS withheld at the notified 0.5 percent rate, and a residual bank credit that has to be reconciled back to the GSTR-1 outward supply, the platform's GSTR-8 TCS line, and the brand's bank statement. Without a structured reconciliation discipline, mid-market brands routinely lose 2 to 4 percent of gross channel revenue inside mis-tagged listing fees, unclaimed BOGO replacements, mis-treated Section 9(5) versus Section 52 GST positions, and TCS credits that never land in the electronic cash ledger because the GSTR-8 reconciliation was never closed.
- **Logic:** Ingest each platform's settlement file daily with a parser per format (Blinkit, Zepto, Instamart all run different schemas); decompose the gross invoice into seven deduction buckets — item-level margin, listing fee, ad and slotting invoices (kept separate, 18 percent GST claimed as ITC), scheme reimbursement classified by Section 15(2) treatment, fill-rate and QC penalties, return-to-vendor credit notes, and Section 52 TCS at the 0.5 percent notified rate. Tag every outward supply with the TCS-collector GSTIN in GSTR-1. Tie the platform-reported TCS to the GSTR-8 GSTIN line and to the GSTR-2A TCS credit line; claim in GSTR-3B. Reconcile the net bank receipt against the platform's payment advice on the T+7 to T+14 horizon. Apply the rate-by-date table for the 22 September 2025 GST 2.0 cut-over on the affected HSN list.
- **Config:** Platform parser per ECO (Blinkit, Zepto, Instamart) with deduction-taxonomy mapping; SKU master with HSN, GST rate and 22 September 2025 cut-over flag; scheme master with Section 15(2) treatment flag per scheme; ad-invoice register routed to marketing GL with ITC claim; Section 52 TCS register at the notified 0.5 percent rate (CBIC Notification 15/2024-CT); GSTR-1 tagging rule for ECO-collected supplies (TCS-collector GSTIN); GSTR-8 ingestion per ECO per month; GSTR-2A TCS credit reconciliation rule; bank-statement matcher for net settlement receipts; clear Section 9(5) exclusion flag (FMCG goods are NOT in the deemed-supplier regime — only the four notified service categories qualify).
- **Output:** A monthly quick commerce settlement pack per platform: gross invoice raised, seven-bucket deduction decomposition with named-line breaks, net bank receipt tied to platform payment advice, Section 52 TCS three-way tie (settlement file, GSTR-8, GSTR-2A), GSTR-1 outward-supply tagging audit trail, ad-spend invoice register with ITC posture, scheme reimbursement ageing buckets (0-30 / 31-60 / 61-90 / 90+ days), GST 2.0 rate-by-date audit log, and a leakage summary surfacing un-recovered listing fees, mis-tagged ad-spend deductions, and any Section 9(5) versus Section 52 treatment error before it reaches the GSTR-3B cycle close.

### Rallis India + Sumitomo Chemical India Agrochemical Distributor Reconciliation

Source: https://www.terra-insight.com/insights/rallis-india-sumitomo-chemical-agrochemical-distributor-recon/

- **Problem:** A listed Indian agrochemical manufacturer running approximately 4,500 authorised state-level distributors and approximately 90,000 downstream retailers across a kharif (June to September) and rabi (October to March) seasonal cycle must simultaneously reconcile primary-sale invoice value with distributor GSTR-2B, Section 8 Sl. 18 code 1015 commission TDS at 5 percent on distributor incentive scheme accruals, the distributor's own Section 8 Sl. 8 code 1031 purchase-leg TDS at 0.1 percent on primary-sale value above the Rs 50 lakh single-supplier threshold, Section 15(2) CGST post-supply trade discount treatment for lifting schemes and BOGO promotions with the corresponding Section 34 credit note and distributor-side ITC reversal, the secondary-sales statement submitted by every distributor through the DMS portal (which never appears on manufacturer books but drives scheme accrual), Section 195 TDS on active-ingredient import from an overseas parent or affiliate under DTAA, and Section 43B(h) MSME 45-day aging exposure at both ends of the pyramid. Manual reconciliation across four tiers and two seasons mis-attributes scheme accrual, leaves ITC reversal exposure open on the distributor side, and creates parallel Form 26AS mismatches for both the manufacturer and the distributor at the same tax audit.
- **Logic:** Build a distributor master keyed by state, dealership-licence number, PAN, GSTIN, MSME flag, and preceding-year turnover disclosure that gates the Section 194Q code 1031 applicability check. Ingest every primary-sale invoice, extract the tax invoice under Section 31 with HSN 3808 pesticide classification at 18 percent GST, and expose the invoice-to-GSTR-1 mapping so the distributor's GSTR-2B reflects the credit within the following filing cycle. Run the secondary-sales statement ingestion from the DMS portal as a parallel ledger keyed to the same distributor code, aggregate the season-close secondary volume against the primary-sale primary volume, and produce the distributor-level lifting-scheme accrual under the scheme agreement (which by construction predates the primary supply, satisfying Section 15(2) second-limb treatment). Generate the Section 34 credit note at 18 percent GST on the scheme accrual, reduce the manufacturer's output tax liability, and post a matched ITC reversal advisory to the distributor's account through the DMS. Aggregate the primary-sale value per distributor for the year, monitor the Rs 50 lakh Section 194Q threshold, and flag the distributor's obligation to deduct 0.1 percent TDS on the manufacturer's PAN — the reciprocal Form 26AS credit is then reconciled at the manufacturer's own tax audit. Extract the Section 194H code 1015 commission accrual on any target-linked incentive scheme, deduct 5 percent, remit against the distributor PAN, and generate Form 16A to the distributor at the quarter close. For the AI import leg, ingest the shipping bill, extract the CIF value, and run the Section 195 TDS deduction under the applicable DTAA rate with the tax residency certificate on file. For the Section 43B(h) MSME aging, cross-tie every MSME-flagged supplier's payable to the 30/40/45-day aging report and expose the year-end Section 43B(h) disallowance addition before the tax audit filing.
- **Config:** Distributor master with state, dealership-licence number, PAN, GSTIN, MSME flag, preceding-year turnover, principal-product allocation, and scheme-eligibility flag; product master with HSN (3808 for pesticides, 3105/3102 for fertilizer where applicable), CIB&RC registration number, and molecule-level restrictions; scheme master with lifting-scheme volume threshold, BOGO promotion pairing, early-payment discount rate, and effective-date range that must predate the associated primary supply to qualify for Section 15(2) second-limb treatment; primary-sales ledger keyed to invoice, distributor, product, and scheme flag; secondary-sales feed from the DMS portal; TDS master with Section 194H code 1015 (5 percent commission), Section 194Q code 1031 (0.1 percent purchase-goods), Section 195 (foreign remittance under DTAA), and Section 194C codes 1023 and 1024 (contract manufacturing at MSIL formulation units); MSME payable aging bucket at 30/40/45 days; season calendar with kharif window (June to September) and rabi window (October to March) driving scheme-accrual timing.
- **Output:** A season-close multi-tier agrochemical distributor reconciliation pack: primary-sales register by distributor by product by month with HSN 3808 at 18 percent GST reconciled to GSTR-1; secondary-sales statement register by distributor with the DMS-portal cross-tally; scheme accrual register with the associated Section 34 credit note under Section 15(2) second-limb treatment and the matched distributor-side ITC reversal advisory; Section 194H code 1015 commission TDS reconciliation with Form 26AS at the distributor PAN; Section 194Q code 1031 reciprocal TDS credit reconciliation with Form 26AS at the manufacturer PAN; Section 195 foreign-remittance TDS ledger against the AI import leg with the DTAA relief workbook; Section 43B(h) MSME aging report at 30/40/45 days on both raw-material MSME suppliers (manufacturer leg) and MSME sub-distributors (distributor leg); state-level CIB&RC dealership-licence expiry alert calendar; and a season-close inventory position by distributor across kharif and rabi cycles that supports the year-end true-up and the next-season primary-sale planning cycle.

### Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart

Source: https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india/

- **Problem:** FMCG and D2C brands selling to Blinkit, Zepto, and Swiggy Instamart face a B2B wholesale-inventory reconciliation problem — 450 to 1,200 POs per month per brand at SKU-level negotiated margins (15–35% off MRP), with damage deductions at the dark-store dock, trade-promotion netting, Section 194Q TDS on purchases above ₹50 lakh, and 30–45 day payment terms — where a 1% margin drift on a top SKU compounds to lakhs of receivable variance per quarter.
- **Logic:** Match each quick-commerce payment advice to the originating PO and invoice at SKU level. Validate negotiated margin per SKU per platform against the brand's trade-scheme master. Decompose deductions into categories — trade promotion, damage, short-receipt, return, fill-rate penalty, Section 194Q TDS — and book each to its own GL. TCS Section 52 applies only for marketplace categories (rare for direct-buy FMCG); GSTR-2B captures those credits via the operator's GSTR-8.
- **Config:** Quick-commerce platform adapters (Blinkit, Zepto, Swiggy Instamart), PO and invoice mapping per dark store, SKU-level trade-scheme and margin master, damage and short-receipt classification rules, Section 194Q TDS threshold per buyer, and settlement cycle calendar (T+30 to T+45).
- **Output:** A reconciled B2B receivable ledger per platform with SKU-level margin drift isolated, damage and short-receipt variance quantified per dark store, 194Q TDS credit tracked in Form 26AS, and trade-promotion spend verified against agreed scheme rates — with a board-ready view of net realisation per SKU per platform.

### Rasi Seed Hybrid Cotton Farmer Buyback Reconciliation

Source: https://www.terra-insight.com/insights/rasi-seed-hybrid-cotton-farmer-buyback-reconciliation/

- **Problem:** A hybrid cotton seed producer running a grow-out plot programme across approximately 6,000 contract growers over 12,000 acres in Adilabad and Warangal (Telangana) and Guntur (Andhra Pradesh) must reconcile female and male parent-line issue against per-farmer buyback in quintals, State Seed Testing Laboratory (SSTL) germination and genetic purity certificates against the Seeds Act 1966 notified minima, Section 43B(h) 45-day grower payment discipline for Udyam-registered aggregators, the Seeds HSN 1209 nil-rated Section 54(3) refund cycle where 18 percent packaging and seed-treatment input GST accumulates against zero-percent output, PPV&FRA variety registration and the trait-fee ledger with the Bollgard II technology provider, and the state cotton seed MRP cap that governs the commercial packet price. Manual reconciliation across parent-line issue, supervision cycle, per-farmer buyback, SSTL certificate, and packet lot tag loses per-plot traceability, exposes the company to Seeds (Control) Order 1983 dealer-licence audit findings, and delays the Form GST RFD-01 nil-rated ITC refund by one or more quarters.
- **Logic:** Build a grow-out plot register keyed to each contract grower with plot code, village, mandal, district, acreage, and assigned female and male parent line lot. Ingest the parent-line issue transaction — kilograms of female parent seed and kilograms of male parent seed issued per plot — and expand each supervision-cycle log entry (sowing, weeding, roguing, isolation-distance check, emasculation or pollination oversight, harvest supervision) as an attribute of the plot. At harvest, capture per-plot buyback quintals against the parent-line issue and against the notified buyback rate per quintal — flag plots whose actual yield falls below the expected yield band or whose harvest quantum exceeds the parent-line multiplication factor as reconciliation exceptions. Feed the harvested seed lot to the in-house lab for germination, physical purity, and moisture testing, then dispatch to the SSTL for the notified certificate; hold the lot in bonded stock until both certificates pass the Seeds Act 1966 minima. Lots that fail are reclassified as rejected or salvage with the grower buyback settlement adjusted on the rejection rate. Extract 18 percent input GST on packaging (HSN 4811, 3923, 4819), seed-treatment chemicals (HSN 3808), and services from GSTR-3B into the nil-rated Section 54(3) refund workbook; generate the GST RFD-01 filing base against the accumulated ITC. Maintain a grower master with an MSME flag on Udyam-registered aggregators and an aging schedule against Section 43B(h) 45-day payment discipline. Maintain a variety register keyed to the PPV&FRA registration number and a separate trait-fee ledger for the MMBL Bollgard II payable, reconciled against the state-notified cotton seed MRP cap on the commercial packet.
- **Config:** Grower master with grower code, village-mandal-district address, PAN or Aadhaar-linked identifier, MSME Udyam number where the grower is a registered aggregator, and buyback bank account for direct settlement; grow-out plot register with plot code, grower code, acreage, female parent line lot, male parent line lot, and expected buyback quintal band; parent-line issue transaction table; supervision-cycle log with agronomist assignment; per-plot buyback settlement table with rate per quintal, quality-grade bracket, and rejection or salvage flag; in-house lab register with germination, physical purity, moisture, and lot number; SSTL certificate register with SSTL name, certificate number, date, and result; PPV&FRA variety register with registration number, hybrid name, protection expiry, and trait ownership; MMBL trait-fee payable ledger keyed to the Bt hybrid variety and packet quantum; state cotton seed MRP notification register keyed to state and season; Seeds (Control) Order 1983 dealer-licence register keyed to state and licence expiry; GSTR-1 and GSTR-3B feed for the nil-rated Section 54(3) refund workbook; Section 43B(h) aging schedule versus Udyam-registered grower master.
- **Output:** A per-season hybrid cotton seed production reconciliation pack: opening grow-out plot inventory by grower, parent-line issue register versus supervision-cycle log versus per-plot buyback quintals, in-house lab certificate and SSTL certificate against Seeds Act 1966 notified minima, seed-lot commercial release register with packet lot number traceable back to the grow-out plot, nil-rated Section 54(3) refund draft with 18 percent packaging and seed-treatment input GST mapped to the tax period, PPV&FRA variety register with registration number and protection expiry, MMBL trait-fee payable reconciled against state cotton seed MRP cap, Seeds (Control) Order 1983 dealer-licence audit trail across all state operating footprints, and — at year-end — a Section 43B(h) aging schedule for grower buyback payment against Udyam-registered aggregators for the Form 3CD tax audit. Per-plot buyback tally supports the next-season parent-line multiplication planning and the field agronomist performance review.

### Raw Material Price Escalation Clause Reconciliation for Indian Auto Components

Source: https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india/

- **Problem:** Auto-component prices float against raw-material indices through RMPV clauses: steel parts track HR/CR coil (JPC or named mill prices), aluminium/copper/zinc track LME (adjusted for rupee and premiums), and plastics track polymer/resin indices. Each revision cycle the supplier raises a supplementary debit invoice on a price rise or the OEM claws back via a Section 34 credit note on a fall — on goods already supplied, with a time-of-supply question, a GST credit-note window, and a lag between index publication and settlement.
- **Logic:** Recompute each RMPV claim against the contractual formula — base price plus material-weight times index movement on the named index, conversion portion held fixed — for goods supplied in the revision period; classify the result as a supplier supplementary (debit) invoice (taxable upward revision, current period) or a supplier GST credit note under Section 34 (downward revision, within the 30-November cutoff); provision the expected claim at quarter-end on observed index movement and true it up on index publication; tie each revision to the correct tax period for time-of-supply.
- **Config:** Part master carrying base price, base index level, material type and weight per part, named reference index (JPC HR/CR coil, LME with rupee/premium adjustment, polymer grade, PGM benchmark), averaging method and settlement lag; index feed by period; revision-cycle calendar (monthly/quarterly); GST mapping splitting price differential into supplementary-invoice vs Section 34 credit-note paths with the 30-November cutoff tracked; quarter-end RMPV provision ledger for true-up.
- **Output:** A per-part RMPV reconciliation showing computed price-differential per supplied quantity against the named index, the supplementary-invoice or credit-note action with GST on the differential, a quarter-end provision-vs-actual true-up, a Section 34 cutoff watch on downward revisions, and an exception queue for index-formula disputes, proxy-index mismatches, and revisions tied to the wrong tax period.

### Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders

Source: https://www.terra-insight.com/insights/razorpay-settlement-reconciliation/

- **Problem:** A Razorpay T+2 settlement lands in the merchant bank account as a single lumped NEFT credit covering hundreds of orders, net of 2% MDR, 18% GST on MDR, and refund deductions. Without order-level unpacking, the credit cannot be posted to the right revenue and expense accounts or used to claim ITC on MDR GST.
- **Logic:** Multi-pass matching joins the Razorpay settlement_id against the bank statement UTR plus date plus net amount, then explodes the batch using order_id and payment_id to map each transaction to MDR, GST on MDR, and refund adjustments. Variances are classified as FEE_DEDUCTION, TAX_DEDUCTION, ROUNDING, PARTIAL_PAYMENT, or UNEXPLAINED so each lands in the correct ledger entry.
- **Config:** Razorpay settlement-report ingestion keyed on settlement_id, bank UTR matcher with T+2 tolerance, MDR rate table per instrument, and refund-deduction tracker linking back to original order_id.
- **Output:** Order-level revenue posting, MDR expense with 18% GST on MDR eligible for ITC, matched refund entries tied to original orders, and exception ledger for unexplained settlement lines.

### Razorpay MDR Reconciliation: Published 2% vs Negotiated 1.4-1.6% for Indian Merchants

Source: https://www.terra-insight.com/insights/razorpay-mdr-reconciliation-india/

- **Problem:** Razorpay's settlement file blends seven distinct fee cells into one fee column: standard 2% domestic, 3% premium and international and EMI, 2.15% RuPay credit on UPI, 1% international bank transfer, 3.5% international wallets, 0.99% subscription add-on stacked on base, and ₹200 to ₹750 chargeback dispute fees. A subscription business reading the headline 2% loses sight of the add-on stack, the refund MDR retained on cancellations, and the Amex and corporate-card volume that has migrated into the 3% slab.
- **Logic:** Ingest the Razorpay settlement export keyed on settlement_id. Decompose every transaction into instrument, network, BIN tier, scope, and product flag (Subscriptions, Recurring, EMI, International). Recompute expected fee as the contracted slab times gross plus any add-on applicable to the product flag. Compare to actual fee column. Surface variances per cell. Track refund MDR retention and chargeback dispute fees in a standing register. Build a method-mix-weighted effective rate per month and contrast it with the contracted blended rate to expose flat-rate concealment.
- **Config:** Razorpay settlement-file ingestion keyed on settlement_id and payment_id. Per-instrument MDR rule set covering domestic standard, premium, RuPay-credit-on-UPI, international card, EMI, international bank transfer, and international wallets. Subscription add-on rule flagged on Subscriptions and Recurring product. Chargeback dispute fee tracker keyed on dispute_id with network and fee tier. Refund MDR retention register. BIN-to-tier mapping table for Amex, Diners, corporate, and signature-infinite isolation.
- **Output:** A per-instrument effective-rate dashboard contrasting actual against contracted slab. A monthly subscription add-on reconciliation showing transactions billed against contractual basis. A refund and chargeback MDR retention statement. A standing leakage register feeding the renegotiation file at quarterly review with rupees recoverable, dispute window, and recovery probability.

### RBI Debit-Card MDR Cap (RBI/2017-18/105): What It Caps and What It Doesn't

Source: https://www.terra-insight.com/insights/rbi-debit-card-mdr-cap-2017-circular-india/

- **Problem:** Debit-card MDR is regulated by RBI/2017-18/105 but the cap binds only on non-RuPay debit; RuPay debit is zero-MDR by separate mandate. Gateways frequently bill a single blended debit rate, charge MDR on RuPay debit that should be zero, or fail to apply the per-transaction ₹200 or ₹1,000 ceiling on high-ticket transactions. None of this is visible from the settlement netting line — it requires per-transaction network attribution.
- **Logic:** For every debit-card settlement row, identify the network from the BIN (RuPay vs Visa/Mastercard/others) and recompute the expected MDR. RuPay debit: expected = 0. Non-RuPay debit: expected = contracted rate (subject to RBI cap by turnover slab) on the transaction value, then clamp at the per-transaction ceiling (₹200 small / ₹1,000 large). Compare to actual MDR deducted; any positive variance on RuPay or any breach of the per-transaction cap is a recoverable over-charge. Roll up monthly to compute effective rate per network and compare to the contracted blended rate.
- **Config:** Network classifier keyed on card BIN (RuPay vs non-RuPay debit), MDR rule set with the turnover-slab cap as a hard ceiling, per-transaction cap clamp (₹200/₹1,000), RuPay-debit zero-MDR enforcement flag, and a refund-MDR retention tracker since MDR is industry-non-refundable.
- **Output:** Per-transaction debit-MDR variance report distinguishing RuPay over-billing from non-RuPay cap breaches, monthly effective rate per network with contract delta, recoverable over-charge schedule for gateway dispute, and the GST-on-fee ITC line reconciled to the gateway's tax invoice and GSTR-2B.

### Real Estate Brokerage Commission Reconciliation: TDS Section 393(1) Sl. 1(ii) Payment Code 1006

Source: https://www.terra-insight.com/insights/real-estate-brokerage-commission-reconciliation-tds-india/

- **Problem:** A real estate brokerage firm running ₹38 Cr of annual commission across 280 transactions per year — split between sale and lease, residential and commercial, with individual brokers and channel partner sub-agents — operates a four-layer reconciliation problem: Section 393(1) Sl. 1(ii) payment code 1006 TDS at 2% from developer-payers, GST at 18% on the brokerage service, RERA Section 9 broker registration per state and per transaction, and the tripartite firm-to-individual-broker disbursement with its own TDS overlay (code 1006 or code 192 depending on employment status).
- **Logic:** Reconcile every brokerage transaction at deal-closure event with the developer-payer's TDS deduction at code 1006, the GST output at 18% on the invoice, the RERA broker registration validated per state, the individual broker share computed per commercial split, and the firm-to-broker disbursement TDS at code 1006 (independent) or code 192 (employee) — with Form 168 quarterly schedules tied to the books and Form 131 certificates issued to all payees.
- **Config:** Brokerage transaction master keyed by deal ID with developer-payer, project, sale or lease, gross commission, RERA agent number used; broker master keyed by PAN with employment status (independent or employee), state RERA registration list; GST registration status and rate; TDS code 1006 applied to all commission payments and disbursements; Form 168 schedule per quarter; Form 131 certificate library per payee per quarter.
- **Output:** A per-deal close pack showing developer payment received less code 1006 TDS, GST output on the invoice, individual broker share disbursed less code 1006 or code 192 TDS, RERA agent number documentation; a monthly Form 26AS reconciliation against the developer-payer's filing; a quarterly Form 168 return with code 1006 schedule populated; a per-broker Form 131 certificate library ready for the broker's individual tax return.

### Real Estate Developer Revenue Recognition under Ind AS 115: POC, Project Cost Reconciliation

Source: https://www.terra-insight.com/insights/real-estate-developer-revenue-recognition-ind-as-115-india/

- **Problem:** An Indian real estate developer with multiple projects, hundreds of booked units per project, milestone-driven payment schedules, multi-deliverable contracts (apartment, carpark, club), and a divergence between Ind AS 115 point-in-time revenue, Section 43CB POC for tax, and milestone-driven GST output runs three parallel revenue ledgers that must reconcile at every period close — without a structured control, contract liability balances drift and deferred tax positions cannot be evidenced to auditors.
- **Logic:** Reconcile under Ind AS 115 by computing POC monthly against actual cost-to-date over total estimated cost, allocate contract price across distinct performance obligations at standalone selling prices, recognise revenue at handover for residential point-in-time obligations, maintain a parallel Section 43CB POC ledger for tax that produces deferred tax liability against book, and tie milestone GST output invoices to the contract liability rollforward per customer-unit.
- **Config:** Project master keyed by RERA registration number with total estimated cost, total saleable area, expected handover quarter; unit master with booking date, agreement value, payment milestone schedule, performance obligation split; cost ledger tagged to project for monthly POC computation; revenue policy table per project (point-in-time vs over-time per obligation); Section 43CB ledger for deferred tax; GST output register tied to milestone billing trigger.
- **Output:** A per-project quarterly close pack showing POC ratio (cost-to-date over estimated cost), contract liability roll (opening, collections, revenue recognised, closing), contract receivable position, multi-deliverable allocation reconciliation, Section 43CB taxable income vs book revenue with deferred tax liability movement, and the milestone-driven GST output reconciliation tied to GSTR-1 outward supplies for the period.

### Reconciliation Audit Trail: What Regulators Expect in India

Source: https://www.terra-insight.com/insights/reconciliation-audit-trail-india/

- **Problem:** Indian statutory framework requires an 8-year retention minimum (Income Tax Section 44AA, CGST Rule 56, Companies Act) with a queryable, time-stamped, user-attributed history of every match, exception, and override. Spreadsheet snapshots fail this bar.
- **Logic:** Generate every match, exception classification, override, and approval as an immutable, user-attributed, time-stamped event. Link each event to the source documents (invoice, Form 26AS row, GSTR-2B line, bank statement line) and preserve the full chain for scrutiny under Section 65 GST and Section 44AB tax audit.
- **Config:** Role-based access, immutable event log, per-match provenance, configurable retention (minimum 8 years), and exportable audit packs in a format the GST officer or tax auditor can consume.
- **Output:** On-demand audit trail exports that satisfy CBDT tax audit, GST Section 65 scrutiny, and Companies Act statutory audit — each keyed back to the reconciliation decision that produced the ledger entry.

### Reconciliation Automation ROI: A Framework for Indian Finance Leaders

Source: https://www.terra-insight.com/insights/reconciliation-automation-roi-india/

- **Problem:** CFOs need a defensible automation business case built on four line items: staff cost (8–12 days per month of finance effort), recovered ITC (often 0.5–2% of purchases), recovered TDS credits, and penalty avoidance on excess ITC (18% Section 50 interest plus penalties).
- **Logic:** Calculate ROI as (staff savings + ITC recovery + TDS recovery + penalty avoidance) minus (software and implementation cost) over three years. Benchmark matched rate uplift (typical 51–65% manual to 88% automated) and size the recovered ITC and TDS pool against actual prior-year variances, not vendor claims.
- **Config:** Baseline measurement against current manual match rate, transaction volume bands, and three-year model with Year 1 implementation cost and steady-state Years 2–3.
- **Output:** A board-ready ROI memo with payback period (typically 6–12 months), three-year net benefit figure, and ongoing dashboard reporting of realised savings against the original projection.

### Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like

Source: https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance/

- **Problem:** Indian finance teams rarely benchmark reconciliation externally: bank match rates below 80%, GSTR-2B below 75%, and close cycles above 10 days often pass as normal because there is no reference. Without benchmarks, under-performance is invisible until it surfaces as demand notices or audit observations.
- **Logic:** Calibrate performance against published benchmarks — bank auto-match 90%+, GSTR-2B auto-match 80–88%, close by day 3–5, exception resolution by type SLA, zero open exceptions above 30 days. Track month-over-month trend and attribute gaps to data-quality, tooling, or process root causes.
- **Config:** Benchmark targets per reconciliation type, monthly KPI dashboard with peer comparison, and quarterly calibration review with finance leadership.
- **Output:** A performance baseline showing where the team sits against Indian peers, a defensible improvement roadmap, and visible proof of progress against published standards.

### The Reconciliation Control Plan: A One-Page Template for Every Stream

Source: https://www.terra-insight.com/insights/reconciliation-control-plan-template-india/

- **Problem:** Indian finance teams document their reconciliation processes through Standard Operating Procedures and checklists that confirm the process was executed. Neither document identifies the specific ways the process can silently produce a wrong result, ranks those failures by their real Indian tax and audit consequences, or maps a named control to catch each one. When a statutory auditor asks under Section 143(3)(i) whether internal financial controls are adequately designed, or when CARO 2020 Clause 3(ii)(b) requires the quarterly bank statements filed with lenders to reconcile to the books, the SOP-plus-checklist evidence base cannot answer the design test. A single Section 16(4) missed at-risk ITC row, a single 194J-vs-194C misclassification on manpower supply, or a single DRC-01B trigger from a GSTR-1 vs 3B timing mismatch does not have a documented control lineage — and the residual risk is undefendable to the audit committee.
- **Logic:** Terra Insight's reconciliation process design method produces one artefact per stream: a one-page control plan. The template carries nine columns — function, failure mode, cause (mapped to the 6P taxonomy of People, Policy, Process, Portal, Period, Partner), Severity, Occurrence, Detection, Action Priority (High, Medium, Low), prevention control, detection control, owner, cadence, and evidence artefact. The Severity scale is anchored to Indian consequences: 10 for Section 16(4) permanent ITC loss and Section 40(a)(ia) expense disallowance; 9 for Section 200A demand with interest under Section 201(1A) and fee under Section 234E; 8 for CARO 2020 material weakness, DRC-01B or DRC-01C notice; 7 for period misstatement; 5-6 for ledger-level exceptions; 3-4 for presentation errors; 1-2 for cosmetic. The Action Priority table is Severity-first — any Severity 9 or 10 row is High regardless of Occurrence or Detection. Every High row requires two independent detection layers, at least one of which is either a system-enforced rule or an aging queue with escalation.
- **Config:** One control plan per stream: invoice-to-bank, TDS against Form 26AS or Form 168, GSTR-1 versus GSTR-3B, GSTR-2B ITC. Named owner for each row. Named prevention and detection control keyed to the row. Cadence — transactional, daily, monthly, quarterly — recorded against each detection control. Evidence artefact — the specific file, log, screenshot, or ERP report the control produces — named with a retention rule that aligns to the seven-year statutory record retention under Section 128(5) of the Companies Act. Review cadence for the control plan itself: monthly by the controller, quarterly with the audit committee, re-opened on any process change, portal change (Form 168 switchover, IMS rollout), or after every field incident that reveals a new failure mode.
- **Output:** Four one-page reconciliation control plans, one per stream, that the statutory auditor tests as the design evidence under Section 143(3)(i) and CARO 2020 Clause 3(ii)(b). Every High Action Priority row carries two independent detection layers and a named owner. Every residual risk is documented with a written acceptance rationale signed by the controller. The control plan populates the statutory audit checklist and the ICFR test plan, and both testing documents sample against it. Board and audit committee reporting: a monthly dashboard of open High Action Priority rows across the four streams, the aging of unresolved exceptions in each, and a quarterly review that re-scores Occurrence and Detection based on the previous quarter's incident data.

### The Carelessness Family: 16 Reconciliation Errors That Come From Working Late

Source: https://www.terra-insight.com/insights/reconciliation-errors-carelessness-india/

- **Problem:** The month-end scramble at Indian finance teams produces sixteen distinct careless errors — duplicated rows, transposed digits, sign flips, invisible characters, hand-mangled amounts, day/month swaps — that individually look like noise and collectively break the reconciliation working paper. A GSTR-2B match that flags a Rs 47-lakh ITC-at-risk queue often carries eight duplicates and three sign-flips inside the at-risk figure, but there is no way to separate the real leakage from the data-quality noise without walking every row. The controller signs off with a footnote; the auditor writes an observation; the CFO learns of it at year-end.
- **Logic:** Treat this family as detectable-by-construction, not detectable-by-review. Instead of asking the analyst to spot duplicates in the working paper, run a dedupe pass at file upload. Instead of asking the reviewer to notice a sign flip, run a whole-batch sign-convention validator. Instead of asking someone to catch a trailing space on a GSTIN, normalise on import. The sixteen-error catalogue tells you exactly which prevention controls to install; the sign-off gate at the end of each window becomes the residual check rather than the primary detection layer. This is the design-versus-review distinction the reconciliation process design method makes explicit.
- **Config:** A file-upload validator that checks byte-identity duplicates, near-duplicate voucher numbers on the same GSTIN and invoice number, and full-file duplicate uploads. A whole-batch sign-convention validator that flags any batch where the debit-to-credit ratio is outside a normalised band for that ledger. A master-data normalisation pass that strips whitespace and non-printing characters on GSTIN, PAN, invoice number, and voucher number. A date-parser that treats DD/MM and MM/DD ambiguously and flags any row with day less than or equal to twelve for confirmation. A manual-amount validator that rejects fields with mixed period-and-comma patterns before the row enters the ledger. A year-boundary check that flags any transaction dated more than sixty days outside the current financial year.
- **Output:** A reconciliation working paper where the carelessness class is the smallest source of unexplained variance. The controller's sign-off on Day 5 for bank, Day 10 for TDS, and Day 15 for GSTR-2B carries a residual list where the unresolved items are the ones that matter — genuine timing differences, actual missing entries, real supplier-side GSTR-1 gaps — not noise from a duplicated row or a sign flip that took an analyst three hours to trace. The Detection Envelope report tells the auditor which of the sixteen patterns the platform catches for this customer's data shape and which need a workflow-side prevention control instead.

### The Data Gaps Family: 9 Reconciliation Errors That Are Invisible Until the Arithmetic Forces Them Out

Source: https://www.terra-insight.com/insights/reconciliation-errors-data-gaps-india/

- **Problem:** Nine specific reconciliation errors are invisible on the arithmetic alone because they attack the completeness of the supplied data, not the accuracy of what was supplied. A missing fortnight leaves the bank's stated opening and closing balances intact. An entire current account absent from the upload never enters the reconciliation window. A well-formed March statement dropped into the April slot ties on its own numbers. The hardest member of the family — the window-dressed truncation, where the tail is cut and the closing balance is restated to match — produces a file that is self-consistent and cannot be caught by any reconciliation against that file alone.
- **Logic:** Treat completeness as a separate assertion from accuracy and design controls that fire outside the matching loop. A Day 0 checklist validates expected files against the account master before the sequence begins. Row-count and volume comparisons at file load flag zero-row headers and silent tail truncation against prior-period baselines. Companion sources — SA 505 bank confirmations, payment gateway settlement files, independent aggregator statements — cross-check what a single file cannot betray. Every gap that surfaces feeds back into the reconciliation process design register so the next cycle catches it earlier.
- **Config:** A monthly-close Day 0 file expectation list bound to the ERP account and vendor masters. Row-count baselines for every recurring extract, with a percentage-drop threshold that flags a missing fortnight or a truncated purchase register. A required-file completeness gate that blocks the Day 5 bank window sign-off unless every active current account statement is loaded. Vendor register linkage so the MSME 45-day check fires against a validated MSME flag rather than a null default.
- **Output:** A reconciliation cycle that refuses to certify a closing position when a required file is missing, an ITC match that reports its purchase-register row count alongside the GSTR-2B row count, a bank window sign-off that fails cleanly when the fifth current account never arrived, and an exception queue that flags a period whose transaction volume dropped without a business reason. The gap surfaces as an exception rather than as silence.

### Top 10 Reconciliation Errors That Trigger GST Notices

Source: https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india/

- **Problem:** GST demand notices most often trigger from reconciliation errors: ITC claimed without GSTR-2B support (18% interest under Section 50), duplicate invoices, GSTIN mismatches, TDS on GST-inclusive amounts, and platform settlements booked in the wrong period.
- **Logic:** Reconcile GSTR-2B against the purchase register by GSTIN, invoice number, and taxable value before filing GSTR-3B each month. Classify gaps as supplier-timing, duplicate, or genuine discrepancy, and cap the ITC claim to the matched figure only. Issue supplier correction requests for the non-timing exceptions.
- **Config:** GSTIN and invoice tolerance rules, supplier ageing buckets, TDS-on-taxable-value checks, and a pre-GSTR-3B gate that blocks claims without GSTR-2B support.
- **Output:** GSTR-3B filed with fully supported ITC, a documented reversal register, and notice-proof working papers for each filing period, reducing Section 50 interest and Section 122 penalty exposure.

### The Knowledge Gaps Family: 11 Reconciliation Errors Where a Wrong Belief Is Applied Consistently

Source: https://www.terra-insight.com/insights/reconciliation-errors-knowledge-gaps-india/

- **Problem:** Eleven reconciliation errors where a wrong belief is applied consistently — the wrong GST rate everywhere, the wrong TDS section for a whole vendor class, gross where net belongs, reverse charge missed entirely. These are internally consistent files defeating every reconciliation ever built.
- **Logic:** The mathematical truism that anchors the family's honesty is that an error consistent on both sides is invisible to any cross-check. Reconciliation catches a knowledge gap only when a companion source of truth is available — a filed GSTR-1, a TRACES Form 168, an authoritative state-of-registration reference, a Section 197 lower-deduction certificate. Without a companion source, the error remains structural-miss until an external audit surfaces it.
- **Config:** The Detection Envelope classifies each of the eleven errors as catch, catch-conditional, or structural-miss per the customer's specific data shape and the companion sources available. The classification is delivered in writing before go-live.
- **Output:** A per-customer Detection Envelope report listing each of the eleven knowledge gaps against the customer's reconciliation configuration, marking the two structural-miss patterns explicitly, and stating the specific companion sources required to move each catch-conditional to catch.

### The Misconfigured Systems Family: 11 Reconciliation Errors Where the Software Was Set Up Wrong Years Ago

Source: https://www.terra-insight.com/insights/reconciliation-errors-misconfigured-systems-india/

- **Problem:** Configuration parameters set at ERP or cloud-tenant install time — fiscal year, timezone, base currency, display unit, chart-of-accounts hierarchy, voucher sequence rule, export row cap, narration character limit — flow into every export the system produces. When any one of them is set wrong, the export file is internally consistent but carries a systematic distortion nobody notices until a reference source outside the file contradicts it. A month-end reconciliation that treats the export as the truth silently absorbs the distortion into the reconciled figure, and the distortion becomes the number that populates GSTR-3B, the TDS return, and the statutory financial statements.
- **Logic:** Eleven distinct misconfiguration patterns produce this class of failure: fiscal year set wrong, timezone date-shift, stale opening balance, voucher numbering reset mid-year, amounts exported in lakhs, foreign-currency or quantity column drift, account codes remapped mid-period, export cut at a row cap, stale saved-view header, decimal precision drift, and narrations truncated. Detection requires the reconciliation layer to compare the export against a companion reference — the previous audited period's closing balance, the counterpart file's convention, the ERP's own configuration record, or the CBDT-defined April-to-March financial year. Two of the eleven — the fiscal year misconfiguration when arithmetic is internally consistent, and the amounts-in-lakhs export when both sides share the convention — remain structurally invisible to any pairwise cross-check and require either configuration inspection or a third reference file to surface.
- **Config:** The Day 0 pre-close checklist from the 20-day monthly close playbook is the first line of defence — extract timestamps, user log entries, and the software audit trail (mandatory under the proviso to Rule 3(1) of the Companies Accounts Rules 2014 from FY 2023-24) are the raw material for detecting a configuration change since the previous cycle. The reconciliation platform loads the exports along with the configuration fingerprint — extract timestamp, currency, unit, fiscal-year label, row count, and column header signature — and compares against the previous cycle's fingerprint. A change in any parameter without a documented change-control ticket triggers a configuration exception before the reconciliation itself runs. The Detection Envelope report classifies each of the eleven patterns as catch, catch-conditional, or structural-miss for the customer's specific ERP and companion-file profile.
- **Output:** Every configuration-driven distortion is either surfaced as a labelled exception with the offending parameter identified, or documented as a structural-miss in the Detection Envelope with the compensating control required — a quarterly configuration audit, a companion reference file, or a manual sign-off gate on the extract itself. No configuration distortion silently flows into GSTR-3B, into the TDS return, or into the audited financial statements without either being caught or being explicitly acknowledged as beyond the reconciliation layer's structural reach. Auditor sampling under SA 315 finds a documented answer to every configuration risk it is required to assess.

### Reconciliation Debt: What It Costs Indian Companies Every Year

Source: https://www.terra-insight.com/insights/reconciliation-debt-india/

- **Problem:** Deferred matching compounds into reconciliation debt: unmatched TDS receivable (often 15% of entries per month), ITC claimed without GSTR-2B support, and bank suspense balances. Beyond the September GSTR-3B and ITR deadlines, large portions become unrecoverable.
- **Logic:** Age every unmatched item against three calendars — ITR assessment year, GSTR-9 ITC cut-off, and the bank suspense SLA. Segregate recoverable debt (deductor correction still viable) from write-off debt (past deadline), and clear the recoverable pool with correction return requests and GSTR-2B reversal workings before the cut-off.
- **Config:** Ageing buckets mapped to ITR AY and GSTR-9 deadlines, deductor and GSTIN-level tracking, and a suspense account clearance SLA tied to month-end close.
- **Output:** A finite, dated inventory of reconciliation debt with recoverable and irrecoverable splits, scheduled correction workflows, and a monthly debt-reduction report for the CFO and audit committee.

### The Missing and Mistimed Entries Family: 10 Reconciliation Errors That Are Why Reconciliation Exists

Source: https://www.terra-insight.com/insights/reconciliation-errors-missing-mistimed-entries-india/

- **Problem:** The fifth family of reconciliation errors is not a data-quality problem. It is the reason reconciliation exists. Ten patterns where an entry that should be present is missing, or an entry that is present is in the wrong period, or an entry that should have been reversed is still standing. The most dangerous member of this family is the bounce pair unbooked — a credit received and returned on the same wire, netted to zero in the bank, still standing as cleared in the books. When this pattern occurs, the books certify money that has bounced; the finance team believes it holds cash that is not there; the writeoff happens at year-end when the debtor's account is finally reviewed.
- **Logic:** Detection requires row-level narration inspection, not aggregate matching. Every bank row must be classified against the NACH return-code taxonomy — R01 insufficient funds, R06 account frozen, R09 account frozen due to notice, R58 account closed — and every books-side receipt must be paired against a return-file feed or a narration-inspected reversal row. Where the return file is unavailable, the detection layer must recognise the credit-and-return pattern in the bank narration itself. The cutoff straddle is caught by extending the bank match window three to five days into the next period and flagging any straddled entry. The late posting is caught by comparing the books entry date against the bank posting date and ageing the drift. The reversal-with-no-original and vendor-paid-twice cases are caught by cross-referencing bank debits against books entries by counterparty and amount within a rolling window.
- **Config:** The reconciliation platform must ingest bank statements with narration intact — not the truncated version many ERP integrations produce. The NACH return-code taxonomy must be configured against the current NPCI circular. The books side must expose the receipt or payment reference so a bank row can be paired to a specific voucher. Where a return-file feed is not available from the bank, the pattern-recognition layer must be trained on the bank's specific return-narration format — HDFC, ICICI, SBI, and PSU banks each format returns differently, and the training set must cover the customer's actual bank mix. The cutoff window must be configured — three days is standard, five days for banks with known posting delays. The cheque presentation window must be set to the RBI three-month directive.
- **Output:** Every missing entry surfaced as an exception with the counterparty, amount, and reason inferred from the bank row. Every mistimed entry surfaced as a period-drift exception with both dates and the arithmetic impact. Every bounce-pair unbooked surfaced as a top-severity exception blocking the AR sign-off until the receipt reversal is posted. Every cheque outstanding beyond its three-month validity window flagged for writeback or reissue. Every vendor debited twice flagged for recovery. The reconciliation working paper carries a class label for each exception — catch, catch-conditional, structural-miss — mapped to the Detection Envelope report the customer received before go-live.

### Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction

Source: https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software/

- **Problem:** Point-solution software (one tool for bank, another for TDS, another for GST) forces finance teams to maintain separate exception queues, audit trails, and integrations. The approach does not scale when new reconciliation types (gateways, NACH, NBFC loans) are added.
- **Logic:** Adopt a configurable platform with a shared matching engine and industry presets for healthcare, NBFC, real estate, and e-commerce. Connect data sources through APIs and connectors rather than manual file uploads, and route all reconciliation types (TDS, GST, bank, NACH, platform settlements) through one exception queue with one audit trail.
- **Config:** API-first connectors (bank, GSTN, SAP RFC, Oracle API, Tally XML), industry presets, configurable tolerance bands, and a single immutable audit log.
- **Output:** A unified reconciliation operations layer that handles existing and future matching needs without new tools, with 2–4 week deployment and single-pane-of-glass exception management.

### Reconciliation Failure Analysis: A Process Design Method for Indian Finance Teams

Source: https://www.terra-insight.com/insights/reconciliation-failure-mode-analysis-india/

- **Problem:** Reconciliation controls at Indian enterprises are designed as procedural checklists — run the report, tick the box, sign off. The controls do not identify the specific ways each function can fail, do not rank failures by severity, and cannot document why some failures were accepted while others were mitigated. Statutory auditors, ICFR reviewers, and CFOs cannot defend the process to a board or an audit committee without a documented failure analysis for every reconciliation function across every stream, including invoice-to-bank, TDS receivable versus Form 26AS transitioning to Form 168, GSTR-1 versus GSTR-3B output-side liability, and GSTR-2B input tax credit matching.
- **Logic:** Apply Terra Insight's reconciliation process design method — a seven-step discipline running across three phases. Phase one decomposes each reconciliation function into work elements, function requirements, and expected outputs. Phase two enumerates the failure modes, effects, and causes for each function, rates every mode on an anchored Severity, Occurrence, and Detection scale, and prioritises using an Action Priority table where Severity dominates over Occurrence and Detection combined. Phase three documents prevention and detection controls, owners, and cadences in a living register. The 6P cause taxonomy — People, Policy, Process, Portal, Period, Partner — walks every function through the six categories manual reconciliation failure originates in. The 12-class failure mode taxonomy applies at the function level across data extraction, classification, completeness, matching logic, timing, partner behaviour, precision, policy interpretation, aging, cutoff, evidence, and portal drift.
- **Config:** One reconciliation process design worksheet per stream, covering the four core streams (invoice-to-bank, TDS receivable versus Form 26AS or Form 168, GSTR-1 versus GSTR-3B, and GSTR-2B input tax credit). Each row lists a function, the 6P cause category, the 12-class failure mode class, the Severity anchored to Indian statutory consequences (Section 16(4), Section 200A, Section 40(a)(ia), CARO 2020, DRC-01B, DRC-01C), Occurrence based on actual incidents in the prior four quarters, Detection based on the current control layer, the Action Priority (High/Medium/Low), the prevention control, the detection control, the owner, and the review cadence. Reviewed monthly by the controller and quarterly with the audit committee, and re-opened on any material process, portal, or rule change.
- **Output:** A living register of every High-Priority failure mode across all reconciliation streams, each mapped to a specific prevention control that reduces the likelihood of the failure occurring and a specific detection control that catches the failure before it reaches the counterparty, tax authority, or auditor, with a documented risk-acceptance rationale for any residual exposure. The register becomes the design documentation ICFR testing under Section 143(3)(i) verifies, feeds the statutory audit checklist for reconciliation, and defines the point at which manual detection has topped out and reconciliation infrastructure becomes the economically viable next layer for the finance team.

### Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement

Source: https://www.terra-insight.com/insights/reconciliation-kpis-india/

- **Problem:** Without KPIs, reconciliation quality is judged retrospectively at audit. A 69% GSTR-2B match rate — 31% manual review with 3–5% error — quietly produces excess ITC claims and Section 50 interest notices that no monthly review would have caught.
- **Logic:** Track six KPIs: auto-match rate, days-to-close, exception resolution rate, exception ageing, ITC leakage, and TDS credit recovery. Review match rate and ageing weekly, close cycle monthly, ITC leakage and TDS recovery quarterly (aligned with GST and advance tax). Investigate any downward drift immediately rather than waiting for a demand.
- **Config:** Per-type KPI dashboard, target thresholds (match rate above 85%, close by day 5, ITC leakage below 2%, TDS recovery above 90%), and weekly/monthly/quarterly review cadence by role.
- **Output:** A finance controller and CFO view of reconciliation health that flags deterioration early, prevents notices, and produces a benchmarked year-end KPI scorecard.

### What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions

Source: https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india/

- **Problem:** Seven expensive CFO misconceptions — ERP solves it, monthly is enough, it is back-office work, manual is more accurate, software equals infrastructure, all variances are timing, reconciliation debt can be managed — cause structural under-investment and recurring audit findings.
- **Logic:** Reframe reconciliation as a P&L lever, not admin work. Match against external portals (Form 26AS, GSTR-2B, bank-issued MT940), run continuously (not monthly batch), automate the matching phase and keep human review for genuine exceptions, and eliminate debt rather than carry it. Benchmark metrics against industry KPIs to expose under-investment.
- **Config:** Dashboards tying reconciliation KPIs to P&L (lost TDS credits, ITC leakage, Section 50 interest), continuous-match architecture, and a zero-tolerance debt policy with defined clearance cycles.
- **Output:** A measurable shift from audit-reactive to audit-ready, with lower notice volume, faster close, and a documented benefit in lakhs or crores recovered per year.

### Reconciliation Patterns Indian CFOs Should Track

Source: https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo/

- **Problem:** CFOs who only review reconciliation on notice are responding to outcomes. Leading-indicator patterns — falling match rate, ageing 31–90 day exception bucket, growing reconciliation debt, and high-value single exceptions — predict notices 3–6 months in advance.
- **Logic:** Track five monthly patterns: overall match rate per reconciliation type (target above 85%), exception ageing buckets, reconciliation debt balance, individual exceptions above ₹5 lakh, and close cycle days. Investigate any metric drift before the next cycle rather than waiting for an audit or demand notice.
- **Config:** CFO dashboard with the five patterns, threshold-based alerts (match rate drop above 5 points, ageing bucket growth above 10%, debt growth above ₹5 lakh), and industry-specific baselines.
- **Output:** Early-warning visibility that converts reactive notice management into planned remediation, with a monthly CFO report showing pattern trend, root cause, and action plan.

### The Reconciliation Playbook: A Day-by-Day Monthly Close Guide for Indian Finance Teams

Source: https://www.terra-insight.com/insights/reconciliation-playbook-monthly-close-india/

- **Problem:** Four reconciliation streams — bank, TDS, GSTR-2B input tax credit, and GSTR-1 versus GSTR-3B — hit the same three days at month end because each is anchored to a different statutory date. The compression means one stream's exception forces another stream's compromise, the ITC figure that populates GSTR-3B Table 4 is not three-way reconciled against IMS and the purchase register, and the team files GSTR-3B at 11:47pm on the twentieth under time pressure rather than under evidence. The failure surface is not a broken finance team; it is a broken cadence.
- **Logic:** Sequence the four streams across a twenty-day operating window with a named window for each. Days 1 to 5 for bank reconciliation. Days 6 to 10 for TDS deposit and receivable reconciliation. Days 11 to 15 for GSTR-2B input tax credit matching and the at-risk queue against the Section 16(4) November 30 deadline. Days 16 to 20 for GSTR-1 versus GSTR-3B, cross-stream tolerance checks, and controller sign-off before an 11am Day 20 filing. Every stream has a preparer, an independent reviewer, and a sign-off gate that must close before the next stream begins. The escalation protocol runs on a calendar clock — Tier 1 at thirty days, Tier 2 at sixty, Tier 3 at ninety days for most items and reverse-calculated from November 30 for at-risk ITC. A Friday 4pm failure review closes the loop with the reconciliation process design register.
- **Config:** A one-page monthly close calendar published to the team on Day 0. Named roles for each stream — AR analyst, AP analyst, tax executive, tax manager, finance manager, controller. Standard extract cadence per portal — bank statements on Day 0, TDS payable ledger on Day 6, GSTR-2B pull on Day 12 for stability after the fourteenth-of-the-month generation, GSTR-1 versus GSTR-3B on Day 17. Escalation triggers documented per exception class, with the November 30 Section 16(4) deadline as the hard anchor for the ITC queue. Working papers filed in a single monthly folder, cross-referenced to the reconciliation process design register so every High-Priority failure mode has an owner and a detection control that fires inside a specific day of the cadence.
- **Output:** All four reconciliations closed by Day 20, with GSTR-3B filed on Day 20 morning rather than at 11:47pm. GSTR-3B Table 4 populated from the signed-off Day 15 GSTR-2B match; Table 6 populated from the signed-off Day 10 TDS reconciliation; Table 3.1 populated from the signed-off Day 17 GSTR-1 versus GSTR-3B check. Working papers ready for statutory audit sampling under Section 143(3)(i) and CARO 2020 Clause 3(ii)(b) evidence for the quarterly bank statement. No exception carried to next month without a written age note, an escalation owner, and an escalation-date entry on the controller's calendar. A weekly failure review that keeps the reconciliation process design register connected to the runbook exceptions.

### Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know

Source: https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india/

- **Problem:** SAP, Oracle, and Tally record accounting entries but do not natively connect to TRACES or GSTN for Form 26AS and GSTR-2B matching, do not parse NACH returns or platform settlement files, and begin to falter above roughly 1,000 transactions per month.
- **Logic:** Keep the ERP as the ledger of record and attach a dedicated reconciliation layer on top. Ingest SAP via RFC or FBL5N/FBL1N exports, Oracle via BI Publisher scheduled extracts, and Tally via XML API or CSV. Match TDS against Form 26AS by TAN and section, GSTR-2B by GSTIN and invoice, and platform settlements by UTR and settlement reference.
- **Config:** Pre-built connectors for SAP, Oracle, Tally; configurable file-based ingestion for edge cases; matching rule sets per reconciliation type; and exception routing back to the ERP exception log.
- **Output:** ERP ledger and external portal credits reconciled in one place, with variance taxonomy, auditor-ready exception logs, and close cycles compressed without replacing the ERP.

### How to Justify Reconciliation Software to Your Board: A CFO Playbook

Source: https://www.terra-insight.com/insights/reconciliation-software-board-justification-india/

- **Problem:** CFOs lose board approval for reconciliation software not because the need is disputed, but because the investment is framed as IT opex rather than a cost-recovery exercise — staff hours, TDS write-offs, ITC eligibility risk, and close-cycle working-capital friction are all invisible in the P&L until they are surfaced as rupees on a single page.
- **Logic:** Convert the four cost categories to a one-page board narrative: loaded staff hours x ₹600–₹1,200 per hour, TDS receivable write-off at 1–3% of annual TDS deducted, GST ITC ineligibility at Section 50 18% interest plus Section 74 exposure, and close-cycle delay at cost-of-capital x daily operating payments. Present a 2–4 week go-live path and a contracted 70–85% match-rate floor so the return is measurable in one quarterly close.
- **Config:** Board memo template with a four-category cost table, a 3-year payback model, a risk-weighted exposure row for audit penalty probability, and a deployment Gantt showing discovery, configuration, parallel run, and cutover milestones across the quarter.
- **Output:** Board-level approval in one cycle, with a defensible ROI case, a specific go-live milestone, and measurable cost-recovery outcomes trackable in the next quarterly close — not a best-efforts efficiency claim.

### Reconciliation Software for CA Firms in India: Beyond Audit Tools

Source: https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india/

- **Problem:** CA firms running monthly GST, TDS, and bank compliance for 30 to 500 clients hit workflow ceilings with Tally or spreadsheets — there is no multi-tenant isolation, no per-client rate cards, no batch month-end cycle across the full book, and no branded deliverable back to the client, so article clerks spend most of their time on data entry instead of review.
- **Logic:** Operate a multi-tenant reconciliation platform with one isolated workspace per client. Configure per-client masters — GSTINs, TANs, bank accounts, TDS sections, industry preset — and run monthly cycles in batch triggered by statutory calendar. Enforce role-based access so clerks see only assigned clients, partners review exceptions, and sign-off aligns with ICAI SA 230 and SA 500 documentation standards.
- **Config:** Client directory with per-client onboarding templates, rate cards, bank account register, GSTIN and TAN masters, white-label output settings, and article-clerk role assignments. Batch calendar engine keyed to statutory due dates (GSTR-3B, TDS Q-return, ITR).
- **Output:** A CA firm practice scaled from 50–150 clients to 200–400 clients per team, with audit-ready documentation per client, ICAI-compliant sign-off trails, DPDP-aligned client confidentiality, and article clerks redeployed from data entry to exception review and client advisory.

### Reconciliation Software Implementation: What to Expect in 30-60-90 Days

Source: https://www.terra-insight.com/insights/reconciliation-software-implementation-india/

- **Problem:** Indian finance teams buy reconciliation software assuming implementation is a purchase event, but non-standard ERP exports, inconsistent HDFC/ICICI/SBI narration formats, and incomplete PAN/GSTIN counterparty masters regularly derail go-live dates unless a structured 30-60-90 day plan frontloads data quality review and parallel-run validation.
- **Logic:** Run a config-only 30-60-90 day deployment: days 1–30 cover scoping, data quality review, and matching rule calibration; days 31–60 run the first full month of parallel reconciliation alongside the existing manual process; days 61–90 validate a second month, compare match rates against the contractual floor, and conduct team training before cutover. No custom code, no post-go-live development backlog.
- **Config:** Implementation runbook with discovery checklist, 3-month historical data requirement, ERP export mapping templates for SAP/Oracle/Tally/Busy, bank narration normalisation library for HDFC/ICICI/SBI/Axis/Kotak, tolerance thresholds per transaction type, and a parallel-run scorecard tied to 70–85% match rate sign-off.
- **Output:** A reconciliation platform live within 90 days across bank, TDS, and GSTR-2B streams with contracted match rates met on two consecutive monthly closes, finance team trained to self-serve the exception queue, and an audit trail operational from day one.

### Reconciliation Software ROI: How Indian Finance Teams Build the Business Case

Source: https://www.terra-insight.com/insights/reconciliation-software-roi-india/

- **Problem:** Indian finance teams asking the board to approve reconciliation software cannot point to a line item called reconciliation cost because it is scattered across staff capacity, unclaimed TDS credits, written-off ITC, audit penalty exposure under Section 201 and Section 73, and multi-day close delays — none of which appears directly in the P&L.
- **Logic:** Build the ROI model across four cost categories: fully-loaded staff cost (hours x 1.4–1.6x salary), reconciliation debt in rupees (TDS not in Form 26AS + ITC not in GSTR-2B + unresolved bank variances), audit risk exposure (18% p.a. interest + Section 271C penalty + 10% CGST penalty, probability-weighted), and close cycle delay cost. Offset against a config-only deployment investment of 2–4 weeks plus annual licence.
- **Config:** ROI worksheet with Indian regulatory defaults preloaded — Section 201 interest rates, Section 271C penalty caps, CGST Section 73 percentages, MSME 43B(h) 45-day window. Scenario toggles for 10k, 50k, and 2 lakh monthly transactions, single-entity versus multi-GSTIN, and quarterly versus monthly compliance cadence.
- **Output:** A board-ready 3-year ROI model showing payback in 6–18 months for enterprises above the 10,000-transactions-per-month threshold, with ITC and TDS debt recovery isolated as a one-time working-capital release and staff time savings as a recurring benefit.

### Reconciliation Software vs ERP: Why Indian Finance Teams Need Both

Source: https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india/

- **Problem:** SAP, Oracle, and Tally ledgers capture what the business recorded, but have no native mechanism to verify those entries against external truth — bank MT940 files, TRACES Form 26AS, GSTN GSTR-2B JSON, NPCI NACH return files, payment gateway settlement CSVs — so finance teams spend days every month reconciling manually in spreadsheets and the ERP's open-item list grows stale.
- **Logic:** Position reconciliation software as the matching layer on top of the ERP, not a replacement. Ingest external source files, normalise into a common schema, run multi-pass matching against the ERP GL export with configurable tolerance bands, classify unmatched items by variance code, and post cleared entries back via SAP BAPI, Oracle REST, or Tally import. The ERP remains the system of record for vouchers and financial statements.
- **Config:** Bi-directional ERP connectors — SAP RFC/BAPI, Oracle Fusion REST, Tally XML import, Zoho Books API — with field mappings for vendor code, invoice reference, GL code, and clearing document number. Writeback rules configurable per ERP and per transaction type so that cleared items update open-item status in the ERP without breaking audit trail.
- **Output:** A reconciled, closed ERP open-item list with external-source matching evidence against every cleared entry, variance-coded exception queue for genuine investigation, and an immutable audit trail that survives statutory audit, tax assessment, and SOX/IFC review without the ERP being replaced.

### Recurring Add-On and eNACH Mandate-Rejection Fees: Stacked Costs for Subscription Merchants

Source: https://www.terra-insight.com/insights/recurring-add-on-enach-rejection-fees-stacking-india/

- **Problem:** Indian subscription merchants — B2B SaaS, OTT, edtech, NBFC monthly EMI collectors — see effective fee burden 30 to 60 percent higher than the base MDR rate sheet suggests because the recurring add-on (around 0.99 percent per recurring transaction on Razorpay's published subscription product) and the eNACH mandate-rejection fee (around fifteen rupees plus 18 percent GST per failed debit, multiplied across retry cycles) are stacked silently on top of contracted base MDR. The fees appear in different line items, on different invoices, and across different artefacts, so the day-to-day finance team never sees the total. The annual recovery upside on a mid-sized subscription book reaches several tens of lakhs.
- **Logic:** Separate the per-transaction settlement file into recurring channel and one-time channel. For each recurring transaction, compute expected base fee at the contracted card MDR slab and expected add-on at the contracted subscription rate, then compare the sum to the actual fee column. Pull the eNACH return file separately. For each failed debit, classify the failure code against the published NPCI return reason taxonomy, attribute to mandate identifier, attempt number, and retry cycle, and total the per-debit rejection fee plus GST. Reconcile the per-transaction GST totals against the aggregator's monthly tax invoice. Surface deviations against contract clauses.
- **Config:** Per-mandate registry by aggregator with mandate creation date, status, sponsor bank, MDR contract reference. Recurring-channel settlement file pipeline. Base-MDR rule set by card slab. Recurring add-on rate by aggregator. eNACH return file pipeline with NPCI return reason code dictionary. Retry-cycle attribution by mandate identifier. Per-debit rejection fee schedule plus GST 18 percent overlay. Monthly aggregator tax invoice reconciliation engine. Variance register feeding the subscription fee dashboard.
- **Output:** A monthly subscription fee dashboard showing base MDR, recurring add-on, eNACH rejection fee with retry compounding, mandate-creation charges, and GST on each, totalled against the contract rate sheet. A failure-code distribution report classifying eNACH rejections so retry policy can be tuned per code. A monthly GST reconciliation between per-transaction totals and the aggregator tax invoice for ITC claim alignment. A quarterly contract-review brief surfacing variance against the contracted recurring rate and the published bank rejection schedule.

### Redevelopment Projects: Free Flats + Rent to Existing Tenants Under GST

Source: https://www.terra-insight.com/insights/redevelopment-project-existing-tenant-alternate-accommodation-gst-india/

- **Problem:** An Indian real estate developer running a redevelopment project on an old-society or chawl plot must simultaneously reconcile three GST-relevant streams for the existing tenants — (a) the free replacement flats owed on completion, which is a Section 7(1) supply valued under Rule 27; (b) monthly rent paid during construction, which is consideration for the surrender of tenancy rights and may attract RCM GST at 18%; (c) TDR / FSI acquired from the tenants collectively, taxable at 18% RCM per Notification 4/2019-CTR to the extent attributable to unsold-on-CC-date units. Manual spreadsheet control across these three streams routinely misses either an OMV drift on Rule 27 or an RCM under-provisioning that surfaces two years later in a Section 74 notice.
- **Logic:** Maintain a per-tenant register tying each existing tenant to their old carpet area, the replacement flat carpet area, the Rule 27 valuation basis, and the monthly rent commitment during construction. Value the free flat under Rule 27 waterfall — OMV via comparable free-sale bookings first, like-kind-and-quality next, cost-plus-10% only as last resort — and recompute quarterly as fresh free-sale bookings establish OMV. Compute TDR / FSI RCM liability at each quarter based on unsold-on-CC-date projections. Tie every rent payment in bank statement to the surrender-of-tenancy service ledger and to the RCM provisioning. Reconcile GSTR-3B output, GSTR-3B RCM inward, and GSTR-9 annual figures to the project ledger every month.
- **Config:** Project master keyed by RERA registration number with construction start date, expected CC date, and total tenant count; existing tenant register with old carpet area, replacement flat carpet area, floor, tower, agreement date, monthly rent commitment; Rule 27 valuation ledger with valuation basis (OMV / like kind / cost+10%), supporting comparable, revaluation trigger dates; monthly rent payment register tied to bank statement debits and RCM GST provision; TDR / FSI acquisition register with residential/commercial split and unsold-on-CC-date projection; GSTR-3B and GSTR-9 tie-back mapping to the project ledger.
- **Output:** A per-tenant redevelopment position showing carpet area owed, current Rule 27 valuation, GST output liability on free-flat construction service, monthly rent paid to date, RCM GST provision on surrender-of-tenancy service, and TDR / FSI RCM liability apportionment. A monthly GST filing pack per project with GSTR-3B output on construction service, GSTR-3B RCM inward on rent and TDR, and reconciliation of both to the project ledger. An audit-ready evidence trail per assessment year linking every free flat, every rent debit, and every TDR event to the source document — agreement, bank statement, and Rule 27 comparable.

### Refund Landing After PG Settlement: Negative-Net Cycle Reconciliation

Source: https://www.terra-insight.com/insights/refund-after-payment-gateway-settlement-reconciliation-streaming-india/

- **Problem:** For OTT and streaming subscription businesses in India, refunds are frequently initiated days or weeks after the original transaction has already settled. The refund cannot be clawed back from the closed settlement, so it lands as a negative adjustment in a later cycle. Finance teams that try to net the refund against the original settled amount produce a broken audit trail; teams that book it in the wrong period miss the Section 34 CGST credit note deadline and the proportional ITC reversal.
- **Logic:** The reconciliation runs across two cycles simultaneously. Cycle A holds the original gross settlement, its MDR fee, its ITC on the fee, and the recognised subscription revenue. Cycle B — the settlement cycle in which the refund is initiated — holds the negative refund line, the credit note issued under Section 34 CGST, and the proportional ITC reversal in GSTR-3B Table 4B(2). The two cycles are linked by a common transaction reference (payment_id or order_id) but are booked as independent accounting events. A refund register threads through both, closing only when settlement, credit note, and ITC reversal are all confirmed.
- **Config:** Refund-lag classifier (same-cycle vs cross-cycle), Section 34 credit-note deadline tracker (30 November of following FY), proportional ITC split engine, and negative-net-cycle detector that flags days where refund volume exceeds new settlement volume.
- **Output:** Refund register linked to original orders across cycle boundaries, credit notes issued within the Section 34 window, GSTR-3B Table 4B(2) reversal schedule matched to credit note dates, and a negative-net-cycle exception log that lets treasury anticipate bank debits for shortfall days.

### 15 Questions to Ask When Selecting a Reconciliation Vendor in India

Source: https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india/

- **Problem:** Procurement checklists for reconciliation vendors are typically adapted from generic SaaS templates that cover uptime, security, and API posture but omit the five India-specific diagnostic questions — TDS net-of-gross handling, GSTR-2B JSON ingestion, NACH return codes, data residency, and use-case scoping — that predict whether a platform will actually deliver on Indian transaction data.
- **Logic:** Use a 15-question evaluation with five India filters up front and ten universal architecture questions behind them. Require vendor responses in writing and backed by a POC on the buyer's own data. Require a contractual match-rate floor (70–85%) and ISO 27001:2022 scope documentation. Treat declines to commit on match rate or region configuration as disqualifying answers.
- **Config:** 15-question RFP template, vendor response grading rubric, POC data request pack (3 months of bank statements, ERP GL export, GSTR-2B JSON, TRACES challan CSV, NACH NPCI return file), and a contract clause library covering match rate, data residency, audit trail retention, and ISO 27001:2022 scope.
- **Output:** A documented, defensible vendor selection with written responses to each question, a match-rate floor in the MSA, ISO 27001:2022 and AWS Mumbai residency evidence, and a POC report that de-risks the first quarterly close after go-live.

### Rejection Debit After Invoice Already Paid: Section 34 Credit Note Cycle

Source: https://www.terra-insight.com/insights/rejection-debit-after-invoice-paid-auto-section-34-credit-note-india/

- **Problem:** Rejection debit notes routinely arrive from auto OEMs after the supplier has already received payment on the original invoice. The supplier owes the OEM a refund or credit for the defective quantity, must issue a Section 34 GST credit note within a statutory window, and needs to reconcile the payment received, the debit received, the credit note issued, and either a refund voucher or a next-invoice offset.
- **Logic:** Reconcile four ledger events: original invoice raised, payment received against invoice, rejection debit received from OEM, and Section 34 credit note issued. Match on OEM purchase order reference, original invoice number, and rejected quantity. Determine whether the credit is settled by refund voucher or netted against the next running invoice. Reduce output tax liability in supplier's GSTR-1 Table 9B. Confirm buyer-side ITC reversal via GSTR-2B.
- **Config:** Section 34 CGST credit note requirement, GSTR-1 Table 9B reporting, refund voucher (Rule 51) versus next-invoice offset accounting policy, statutory deadline of November 30 following financial year end, Rule 42 proportionate ITC reversal on buyer side.
- **Output:** Post-payment rejection reconciliation register showing invoice, payment date, rejection debit amount, credit note number and date, settlement method (refund/offset), GSTR-1 Table 9B period, and OEM ITC reversal confirmation.

### Refund reconciliation for payment gateways — matching deductions to credit notes

Source: https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway/

- **Problem:** Every payment gateway refund creates three simultaneous obligations: the settlement deduction, a Section 34 credit note to the customer, and a proportional ITC reversal in GSTR-3B Table 4B(2). Gateway-initiated refunds on failed captures add automatic deductions without merchant approval — each still carries the full GST reversal obligation.
- **Logic:** Three-way matching links every negative settlement line (full refund, partial refund, or gateway-initiated) to the original order_id and payment_id, the credit note issued under Section 34, and the ITC reversal posted in GSTR-3B Table 4B(2). Partial refunds split the original revenue and ITC lines proportionally so the retained portion keeps its revenue and ITC intact.
- **Config:** Refund-type classifier (full, partial, gateway-initiated), Section 34 credit-note deadline tracker (30 November or GSTR-9 filing of next FY), and proportional ITC split engine.
- **Output:** Refund register matched to source orders, credit notes issued within the Section 34 window, GSTR-3B Table 4B(2) reversal schedule, and evidence pack closing the customer-refund-to-GST loop.

### Reliance Smart / RRVL FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/reliance-smart-rsl-fmcg-settlement/

- **Problem:** Indian FMCG brands selling into Reliance Smart face a bulk-PO model with a roughly 10-day settlement cycle, settlement files that combine PO, GRN, invoice and multi-category deductions per line, and BTL marketing reimbursement claims that are netted against running payables. The PO-GRN-invoice triplet match per dispatch is broken by partial supply, QC reject lines, and stale-trade-margin pricing; BTL claims are raised without validation against the agreed scheme circular; and Section 15(2) CGST classification on trade-scheme credit notes is mis-applied — leaving brands over-paying BTL reimbursement by a meaningful share and exposing GST liability for non-qualifying credit notes.
- **Logic:** Build an RSL-specific settlement adapter that parses the bulk PO, GRN, and settlement file. Run the triplet match per dispatch line: PO quantity equals GRN-accepted quantity equals invoice quantity, PO unit price equals invoice unit price. Maintain a BTL claim register keyed by scheme circular reference, SKU, store cluster, and activation dates with evidence flag; match each RSL-raised BTL claim against the circular before approving the deduction. Classify every trade-scheme credit note under Section 15(2) Sl. (a) or (b), and only book GST liability reduction when the three-prong test is met. Cross-foot the net settlement to the brand's open receivable ledger per RSL GSTIN before payment posting.
- **Config:** RSL vendor-portal PO and settlement-file adapters; SKU master with MRP history and trade-margin schedule per RRVL category; BTL scheme master with circular reference, SKU coverage, store-cluster scope, agreed value, evidence type, and activation dates; ageing buckets on open BTL claims (0-30 / 31-60 / 61-90 / 90+ days); Section 15(2) treatment flag per scheme; Section 393(1) Sl. 8(ii) (1031) purchase-of-goods TDS threshold tracking per buyer GSTIN; pre-22-September 2025 versus post-22-September 2025 rate switch on affected HSNs.
- **Output:** A reconciled RSL settlement pack per cycle: PO-GRN-invoice triplet match exceptions surfaced per dispatch, BTL claim variance versus agreed circular surfaced per activation, Section 15(2) qualifying versus non-qualifying credit notes split, Section 393 TDS credit tracked in Form 26AS at deductee-GSTIN level, and a net realisation view per SKU per category. Aged BTL claim buckets feed the year-end audit pack under Ind AS 37 and CARO 2020.

### RERA Form 3 / Form 5 Quarterly Compliance: Escrow Drawdown vs Construction Progress

Source: https://www.terra-insight.com/insights/rera-compliance-quarterly-form-progress-report-real-estate-india/

- **Problem:** An Indian real estate developer running RERA-registered projects must file quarterly Form 3 (CA), Form 4 (Architect) and Form 5 (Engineer) certifications on the state regulator's portal within 15 days of quarter close, with escrow drawdown from the 70% pool strictly capped at the certified stage-of-completion percentage multiplied by estimated project cost — failure to file or diversion above the certified cap attracts Section 63 penalty up to 5% of estimated project cost and Section 7 deregistration risk that freezes new bookings and breaches lender covenants.
- **Logic:** Compute the certified withdrawal entitlement as (Form 5 engineer-certified POC%) × estimated project cost minus cumulative withdrawals to date; tie every escrow debit to a specific construction-cost invoice or land-cost instalment; reconcile the bank statement of the designated 70% account daily to the collection ledger and the withdrawal register; produce the Form 3 CA certification input pack quarterly from the same reconciled cost ledger that drives the books; maintain a per-state filing calendar with quarterly deadlines and per-form templates.
- **Config:** Project master keyed by RERA registration number and state with estimated total cost, total saleable area, registered completion date; designated escrow bank-account master per project; per-state certification calendar with cadence (MahaRERA monthly + quarterly, UP-RERA quarterly, K-RERA monthly cash flow + quarterly progress); certification register with Form 3 / Form 4 / Form 5 IDs, signatories, POC %, cost-to-date, entitlement computation; withdrawal register tied to construction-cost invoice ID; bank statement ingestion for daily escrow reconciliation.
- **Output:** A daily escrow position per project showing 70% pool balance, certified withdrawal entitlement to date, cumulative withdrawals, available headroom, and any over-withdrawal flag with Section 63 exposure amount; a quarterly Form 3 / Form 4 / Form 5 filing pack per project with reconciled cost-to-date, POC computation, bank-statement tie-back, and audit trail linking every escrow debit to a specific construction-cost invoice; a per-state filing calendar with quarterly deadlines and traffic-light status against each project's Form 3 upload.

### RERA Escrow Account Reconciliation for Indian Real Estate Developers

Source: https://www.terra-insight.com/insights/rera-escrow-account-reconciliation-india/

- **Problem:** An Indian real estate developer running multiple RERA-registered projects across two or three states must ring-fence 70% of customer collections per project in a designated escrow account, certify withdrawal-in-proportion via engineer + architect + CA certificates on cadences that vary by state (monthly in Maharashtra and Karnataka, quarterly under the central Act), and tie each withdrawal to specific construction-cost or land-cost invoices — with diversion attracting Section 60 penalties up to 5% of estimated project cost and project deregistration risk under Section 7.
- **Logic:** Reconcile every customer collection at deposit to the designated escrow account, route every withdrawal through a certified entitlement calculation (POC × estimated project cost − cumulative withdrawals), tie every escrow debit to a specific construction-cost invoice or land-payment instalment, maintain per-state certification calendars matched to the regulator's filing cadence, and reconcile quarterly Form 4 progress report figures to bank statements before submission.
- **Config:** Project master keyed by RERA registration number per state with estimated total cost, total area, registered handover date; escrow bank-account master per project with designated bank, IFSC, account number; per-state certification cadence calendar (MahaRERA monthly, UP-RERA quarterly, K-RERA monthly cash flow); cost ledger tagged to project for POC computation; withdrawal register with engineer-certified POC %, architect cost-to-date, CA-certified entitlement; bank statement ingestion for daily collection and withdrawal reconciliation.
- **Output:** A daily escrow position per project showing 70% pool balance, certified withdrawal entitlement to date, cumulative withdrawals, available headroom, and any over-withdrawal flag; a monthly per-state filing pack with the certified POC%, the bank-statement-reconciled cash flow, and the Form 4 progress report tied to the books; an audit-ready evidence trail per quarter linking every escrow debit to a specific construction-cost invoice with engineer, architect and CA certification IDs.

### Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework

Source: https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation/

- **Problem:** Restaurant chain finance leaders deciding how to handle aggregator reconciliation face three structurally different options — build in-house with Excel, SQL, and a data team; buy a per-aggregator reconciliation tool; or deploy reconciliation infrastructure with restaurant industry preset as one vertical — and need a TCO framing, capability checklist, and evaluation rubric that holds across multi-aggregator, multi-outlet, multi-GSTIN, multi-state, and multi-channel scope without confusing the choice with a pricing comparison.
- **Logic:** Frame TCO across six components (finance time, audit risk, dispute window losses, ITC and cash-ledger leakage, ERP integration cost, scale-out cost); apply a capability checklist covering multi-aggregator coverage, India tax framework (Section 393 TDS at 0.1% with payment code 1035, Section 52 CGST TCS, Section 9(5)), GSTR-2B and GSTR-8A integration, audit evidence, and ERP write-back; score candidates on a ten-dimension rubric; map the right option to chain scale (build below 10 outlets and single GSTIN, per-aggregator tool below 30 outlets and single aggregator, reconciliation infrastructure at multi-aggregator or 30-plus outlet scale).
- **Config:** TCO model with six components and chain-scale parameters; ten-dimension capability scorecard; Section 393 TDS calculator at 1% with payment code 1035; Section 52 CGST TCS calculator with intra-state CGST/SGST and inter-state IGST split; Section 9(5) GST classifier; GSTR-2B commission ITC matcher per GSTIN; GSTR-8A cash-ledger acceptance flow with GSTR-3B utilization; CARO 2020 audit evidence retention rule set; ERP connector inventory; pilot protocol for 30-day three-cycle two-outlet two-aggregator evaluation.
- **Output:** A vendor evaluation conclusion mapped to the chain's actual scope — aggregator count, outlet count, GSTIN spread, ERP stack, audit posture — with a TCO comparison that prices in the components a headline subscription does not, a capability gap analysis against the ten-dimension scorecard, and an implementation timeline aligned to GSTR-3B and quarterly TDS filing windows.

### Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit

Source: https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation/

- **Problem:** Restaurant cash flows through four hands between the guest and the bank — cashier drawer, shift manager, cash room, pickup agent — and each handover is an opportunity for shrinkage that aggregate end-of-day numbers hide.
- **Logic:** Run a four-point daily match: POS Z-report cash component, drawer count, cash room handover slip, bank credit narration. Classify every variance into a four-bucket taxonomy (short, over, voids, refunds), age cash-in-transit by deposit slip, and rank outlets on variance per lakh of cash sales for chain-level outlier detection.
- **Config:** POS connector pulling shift-level Z-reports per outlet; cash room handover digitisation; pickup-agent route timestamps; bank statement ingestion with deposit-slip narration parsing; chain-level rollup by region, brand, and bank.
- **Output:** A daily cash exception register at outlet level, a chain-level variance ranking, and a cash-in-transit ageing report — closing the four-point match within 24 hours and surfacing pickup-agent shrinkage by deposit-time and amount drift.

### Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393

Source: https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india/

- **Problem:** An Indian restaurant franchisee owes the franchisor four parallel monthly flows — brand royalty, national marketing fund, technology fee, and supply-chain margin on commissary purchases — each with its own GST treatment and the royalty line subject to TDS under the new Section 393(1) Sl. 6(iii).D(b) with payment code 1027, and a generic AP reconciliation does not handle this correctly.
- **Logic:** Reconcile each franchisee invoice line against its own base: royalty against franchisee POS gross sales × contracted royalty rate, NMF against gross sales × NMF rate, tech fee against transaction count or fixed monthly base, commissary supply against goods received and tax invoices. Apply 18% GST input tax credit on services (royalty, NMF, tech fee) only against 18%-with-ITC revenue lines. Deduct TDS on the royalty payment under Section 393(1) Sl. 6(iii).D(b) with payment code 1027.
- **Config:** Franchisee POS sales feed by day; royalty rate, NMF rate, tech fee schedule from the franchise agreement; commissary item master and GST rate map; 18% ITC eligibility flag by revenue line; TDS engine configured for new payment code 1027 on royalty; cross-era handling for any opening balance carried from the legacy 194J era.
- **Output:** A monthly franchisee close where each franchisor invoice ties to its own base, GST input tax credit is claimed only against eligible revenue, salary TDS challan reflects royalty TDS under code 1027, and the franchisor's GSTR-1 outward supply lines reconcile to the franchisee's GSTR-2B inward supply.

### Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs

Source: https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct/

- **Problem:** Indian restaurant GST is split across at least three regimes — 5% no-ITC for standalone restaurants, 18% with-ITC for outdoor catering, and 5% or 18% for hotel-restaurants tied to a room tariff threshold of ₹7,500 — and a single F&B operator running multiple property types must reconcile parallel ITC streams without cross-contaminating tax credits.
- **Logic:** Classify each outlet by the rate notification — standalone, outdoor catering, hotel below threshold, hotel above threshold — apply the correct rate at point of sale, segregate ITC-eligible from ITC-blocked input GST, reconcile aggregator GSTR-2B entries against Section 9(5) reverse charge rules, and produce a per-outlet GSTR-3B contribution that sums to the consolidated entity-level filing.
- **Config:** Outlet-to-rate-regime mapping table; ₹7,500 room tariff threshold flag for hotel-restaurants; Section 9(5) aggregator service recognition; ITC eligibility filter per outlet on rent, ingredients, equipment, and aggregator commission; GSTR-2B aggregator entry parser and reconciliation logic.
- **Output:** A monthly GSTR-3B that correctly applies 5% or 18% per outlet, claims ITC only on eligible streams, reconciles the aggregator GSTR-2B operator-paid GST against the restaurant's own output, and prevents the most common error: claiming ITC on a no-ITC outlet or paying GST twice on a Section 9(5) aggregator order.

### Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission

Source: https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation/

- **Problem:** An 18% with-ITC restaurant on Zomato, Swiggy, and Magicpin pays 18% GST on aggregator commission and is entitled to claim the input tax credit, but the credit is conditional on the aggregator filing GSTR-1 correctly, the invoice appearing in GSTR-2B with the right GSTIN, and credit notes for cancelled orders being tracked back to the original commission invoice — three preconditions that fail silently and leak ITC every month.
- **Logic:** Pull the aggregator settlement file commission line by order, match each commission against the aggregator's monthly tax invoice, locate that invoice in the restaurant's GSTR-2B under the aggregator's GSTIN, post the input GST to claimable ITC only if the 2B entry exists, defer the claim to the next month if the entry is missing, and reverse ITC against any credit notes that flow in for cancelled orders.
- **Config:** Aggregator settlement file connector with commission and GST line parsing; aggregator GSTIN master per state of operation; GSTR-2B fetch and inward-supply matcher keyed to aggregator GSTIN and invoice number; Rule 36(4) eligibility filter that defers ITC claim until 2B entry appears; credit-note reconciliation logic for cancelled orders.
- **Output:** A monthly GSTR-3B that claims 18% ITC on aggregator commission only when the entry is in GSTR-2B, defers any missing entries to the next cycle without breaching Rule 36(4), reverses ITC for cancelled orders via credit notes, and produces a four-way reconciled audit trail across settlement file, aggregator invoice, GSTR-2B, and purchase register.

### Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers

Source: https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india/

- **Problem:** A restaurant bar's same bill mixes GST-taxable food with state-excise-only liquor, and the legal entity must keep two parallel revenue ledgers — GST outward supply for food, excise sales register for liquor — that reconcile to the same bank credit, while complying with state-specific permit cycles, daily stock registers, and FL-licence return formats that vary across Karnataka, Maharashtra, Delhi, Tamil Nadu, and Telangana.
- **Logic:** Tag every POS line at source as food (GST 5% or 18%) or liquor (state excise or VAT); reconcile the liquor leg against permit-against-supply records, daily physical stock register, and FL-licence return; reconcile the food leg through the standard restaurant four-rail close; tie both legs to the same bank deposit by date.
- **Config:** Per-outlet FL-licence class and state, permit cycle, daily stock register format, excise duty structure, GST classification of the food line by outlet type, and till-level rail tagging that splits food and liquor at the bill-line level.
- **Output:** A daily close that produces an excise-compliant stock-and-sales register, a GST-compliant outward supply figure for food, a unified bank reconciliation that ties both legs to deposits, and a permit-utilisation report that flags FL-licence quota burn before re-order.

### Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC

Source: https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation/

- **Problem:** Restaurant POS terminals accept eight payment instruments — UPI, debit, domestic credit, international credit, wallet, BNPL, food card, prepaid — each with a different MDR, settlement cycle, and refund pattern, but the bank credit lands as a single net figure that hides the instrument mix.
- **Logic:** Reconstruct gross sales from the gateway settlement file at transaction level. Apply instrument-level MDR (UPI 0%, debit 0.4-0.9%, domestic credit 1.5-2%, international 2.5-3.5%) to derive expected MDR. Match each settlement batch to the bank credit narration. Book gross revenue with output GST, MDR as expense with 18% GST as ITC, and refunds in the cycle they reverse. T+1 to T+3 timing is reconciled via a payments-receivable ageing ledger.
- **Config:** POS-terminal connectors for Pine Labs, MSwipe, Innoviti, Razorpay POS, Paytm-for-Business; instrument-level MDR rate cards by acquirer; settlement-cycle calendars (T+1 vs T+2 vs T+3); refund-reversal mapping; bank statement ingestion with acquirer-narration parsing.
- **Output:** Per-instrument gross sales, per-acquirer MDR with ITC claim, refund reversals applied to the correct period, and a payments-receivable ageing report that shows which settlements are still in-flight versus credited.

### Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split

Source: https://www.terra-insight.com/insights/restaurant-reconciliation-india/

- **Problem:** An Indian restaurant's daily revenue lands across aggregator payouts, POS card and UPI settlements, and physical cash, each with different commissions, TDS 194O, TCS Section 52, GST splits and settlement timing — making book-to-bank match impossible without per-rail decomposition.
- **Logic:** Decompose each aggregator settlement into gross order value, commission, packaging fee, cancellation, TDS 194O and TCS Section 52 before matching the net payout to the bank credit; reconcile POS gateway settlements separately by MID and batch ID; match daily cash deposits to POS cash sales by deposit slip.
- **Config:** Per-aggregator commission rate by contract tier, packaging fee schedule, GST 5%/18% rule by outlet type and tariff threshold, multi-brand cloud-kitchen GSTIN mapping, T+N settlement cycle by gateway, and TCS Section 52 GSTR-2X claim cadence.
- **Output:** A daily close that ties POS-recorded sales to bank credits across all four rails, with classified variances (under-payout, missing TDS, GST 5% vs 18% mismatch, cash short/over) and an aged exceptions list ready for aggregator dispute and audit trail.

### Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips

Source: https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india/

- **Problem:** Restaurant service charge in India is now opt-out at customer choice (CCPA July 2022 guidelines), and the tip pool collected at the till must be distributed to staff with appropriate GST treatment of the service-charge revenue and salary TDS treatment of the tip-pool payout — none of which a generic POS-to-bank reconciliation handles cleanly.
- **Logic:** Capture customer opt-out as a discrete POS event with a reason code, not a discount; reconcile the service-charge line at the GST rate of the underlying supply (5% standalone, 18% hotel-attached or catering); route the tip pool through the payroll register so salary TDS under Section 392 with payment code 1001 applies and PF/ESI treatment is documented; tie POS service-charge revenue and tip-pool payout to bank credits and payroll register monthly.
- **Config:** POS opt-out reason codes and reporting; GST rate map by outlet type and supply line; tip-pool distribution policy with eligible employee list and weighting; payroll integration that pulls tip-pool amount into the salary line; salary TDS engine using new payment code 1001 (Section 392).
- **Output:** A monthly close where service-charge revenue ties to the GST returns at the correct rate, tip-pool payouts tie to the payroll register and salary TDS challan, customer opt-out volume is tracked as an operational metric, and the audit trail supports both consumer-protection compliance and statutory wage compliance.

### 5% Retention Debit by OEM: Not a Short Payment, Not a Rejection

Source: https://www.terra-insight.com/insights/retention-debit-5-percent-auto-oem-not-short-payment-india/

- **Problem:** Auto OEMs withhold a fixed percentage — typically 5%, sometimes up to 10% — of every supplier invoice as retention money against warranty failures. When a naive reconciliation system sees the shortfall against the invoice amount, it flags the entry as a short-payment or dispute, generating false dunning, incorrect ageing reports, and downstream errors in Section 43B(h) interest calculations.
- **Logic:** For each OEM remittance, parse the debit advice reason code. Where the reason maps to retention, security deposit, or warranty hold, classify the shortfall as a retention receivable — not a short-payment, rejection, or price adjustment. Post an entry to the retention register with the invoice reference, retention percentage, retention amount, and contractual release date derived from the master contract.
- **Config:** Retention percentage per OEM (5% default, 10% for certain safety-critical parts), warranty period in days (90/120/180 depending on part class), remittance advice reason code mapping (retention/security/warranty hold), release-date calculation rule (invoice date or delivery date plus warranty period), MSME status flag per supplier to distinguish 43B(h) clock start.
- **Output:** Retention register with open retention receivables by OEM, expected release dates, and 43B(h) status. Reconciliation report shows retention debits classified separately from short-payments, rejection debits, and rebate debits. Ageing report treats retention as a distinct bucket with its own contractual due date rather than an overdue payable.

### Retro Credit Note for FMCG Schemes Issued at Quarter End

Source: https://www.terra-insight.com/insights/retro-credit-note-fmcg-scheme-quarter-end/

- **Problem:** An FMCG brand owner runs a quarterly slab, growth-vs-base or volume-achievement scheme across the distributor pyramid; the entitlement crystallises only at quarter end when off-take figures are confirmed; the brand owner books a single retro credit note (or a small set) at quarter end against the cumulative primary-sales ledger; if the scheme circular was not in place at or before the time of the original supplies, the Section 15(3)(b) three-prong test fails and the credit note cannot reduce taxable value — but if it was, the distributor must reverse proportionate ITC and the GSTR-1 Table 9B disclosure must reconcile to the distributor's GSTR-2B and 3B; with no standing reconciliation, scheme circular vs credit-note vs GSTR-1 Table 9B vs distributor reversal drifts across three or four registers and the trade-promotion accrual ages past 90 days.
- **Logic:** Stamp every quarterly scheme with a circular reference (number, date, eligible SKUs, slab table, qualifying period); for any retro credit note booked at quarter end, verify the scheme circular date is on or before the first primary-sales invoice in the qualifying period; classify the credit note as either Section 15(3)(b) value-reducing (three-prong test met) or commercial-only (test failed); for value-reducing credit notes, compute the distributor's proportionate ITC reversal at the applicable GST rate of the original supply (with rate-by-date logic for the 22 September 2025 cut-over) and reconcile the brand owner's Table 9B disclosure against the distributor's GSTR-2B negative entry and GSTR-3B reversal; for commercial-only credit notes, route through the trade-spend GL with no GSTR-1 / GSTR-3B impact and a clean audit trail explaining why the three-prong test failed; age all quarter-end credit notes 0-30 / 31-60 / 61-90 / 90+ days against the Section 34(2) 30 November cut-off.
- **Config:** Scheme circular register per quarter (circular number, date, eligible SKUs, slab table, qualifying period, qualifying invoice flag); retro credit note register linked back to scheme circular and to original primary-sales invoice ledger; Section 15(3)(b) three-prong classifier (value-reducing vs commercial-only) per credit note; GST rate-by-date table with the 22 September 2025 cohort boundary; distributor ITC reversal calculator at applicable rate; GSTR-1 Table 9B feed reconciled to distributor GSTR-2B / GSTR-3B; trade-promotion accrual ledger feed; Section 34(2) 30 November cut-off enforcement; ageing buckets 0-30 / 31-60 / 61-90 / 90+ days.
- **Output:** A quarter-close pack per scheme code: scheme circular reference and date, retro credit note number and date, classification (value-reducing vs commercial-only) with the prior-agreement evidence on file, taxable-value adjustment, distributor's expected ITC reversal, GSTR-1 Table 9B reconciliation to distributor GSTR-2B / GSTR-3B, trade-promotion accrual reversal entry, and an ageing report against the 30 November Section 34(2) cut-off — handed to the trade-marketing controller and the GST controller before the next quarter's scheme calendar is locked.

### Retroactive Price Increase from OEM: Credit-Note Aggregation Reconciliation

Source: https://www.terra-insight.com/insights/retroactive-price-increase-auto-oem-credit-note-aggregation-india/

- **Problem:** OEM approves a retroactive price increase (say 3.5% effective three months back). The supplier has already invoiced and often been paid for hundreds of despatches in the intervening period. Section 34 CGST requires a supplementary debit note for the price differential on each despatch; GSTR-1 must reflect it; the OEM's ITC and the supplier's 194Q TDS must reconcile.
- **Logic:** Extract every original invoice raised to the OEM between the revision effective date and the approval date. Multiply the taxable value of each invoice by the differential percentage. Generate one debit note per original invoice referencing the original invoice number and date under Rule 53. Aggregate the DNs into a differential register. Match the register to the OEM's price revision letter (aggregate control), to GSTR-1 Table 9B lines filed in the DN month, and to Form 26AS 194Q entries. Reconcile the OEM's payment against the DN aggregate net of 194Q TDS.
- **Config:** Retroactive period start date (revision effective date), retroactive period end date (approval date or first invoice at new price), price differential percentage, GST rate on underlying supply (28% for most auto components), TDS 194Q rate (0.1%), aggregate purchase threshold flag (₹50 lakh crossed in FY), 180-day ITC clawback trigger for the OEM.
- **Output:** Debit note register with one row per original invoice: original invoice number, date, taxable value, differential percentage, differential taxable value, differential GST, differential total, DN number, DN date, GSTR-1 amendment period, OEM ITC eligible month, payment status, 194Q TDS deducted. Aggregated by OEM plant, HSN, and GSTR-1 return period.

### Return-to-Vendor (RTV) and Damage Credit Note Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/return-to-vendor-rtv-damage-credit-note-fmcg/

- **Problem:** Indian FMCG brands operate structured return-to-vendor programmes for near-expiry stock and a parallel damage credit-note flow for transit and godown losses, but the three registers — distributor RTV log, quality-team disposition note, and Section 34 credit note — live in different systems and rarely match line-for-line. Section 34 of the CGST Act gates GST relief on the credit note to a 30 November deadline following the financial year of original supply, ITC reversal by the distributor is required for the GST adjustment to stand, and damage liability splits between 3PL carrier, brand, and distributor depending on contract terms. The reconciliation gap leaves brand controllers exposed on 12 to 20 percent of the gross RTV value at year-end — either as unbooked credit-note liability or as time-barred Section 34 windows that have closed without issue.
- **Logic:** Build a single RTV-and-damage register keyed by dispatch invoice number, distributor GSTIN, batch code, expiry date, and return-reason code (near-expiry, transit damage, godown damage, primary-packaging failure, retailer return). Disposition each returned line through the quality flow — saleable (re-dispatchable), partially saleable (B-grade dispatch at discount), or destroy. Match each disposition to the brand's Section 34 credit note by invoice number and value; classify by liability owner (brand, 3PL, distributor, shared). Cross-foot to the original dispatch register so the returned quantity ties back to the supply; cross-foot to the GSTR-1 credit-note table to confirm the GST adjustment lands. Run ageing on open RTV lines past 30 days from receipt at the brand depot, and trigger an alert on any FY-2024-25 line still open past 31 October so the 30 November Section 34 deadline does not lapse.
- **Config:** Distributor master with GSTIN, PAN, RTV policy reference (category-specific lead times), and 3PL carrier mapping; SKU master with HSN, GST rate effective-date table (pre-22-September 2025 versus post for transition-affected lines), shelf-life days, and RTV cut-off; dispatch invoice feed with batch and expiry; RTV intake feed from the brand depot scanner; quality-team disposition feed with destroy-versus-saleable-versus-partial flag; credit-note generator keyed to dispatch invoice numbers and the original GST rate; 3PL claim ledger with consignment-note linkage; PLISFPI claim file mapping for the 16 food-processing beneficiaries; ageing buckets (0-30 / 31-60 / 61-90 / 90+) measured from depot intake date; Section 34 deadline calendar with FY 2024-25 cut-off at 30 November 2025 and FY 2025-26 cut-off at 30 November 2026.
- **Output:** A month-end RTV-and-damage reconciliation pack: opening open-RTV liability, period intake (split by return-reason code), period dispositions (saleable / partial / destroy), period credit notes issued (split by liability owner and by GST treatment), period 3PL recoveries booked, closing open-RTV liability, and per-distributor ageing register. A Section 34 deadline tracker surfaces FY-prior lines still open inside the 60-day window before 30 November and routes each to the credit-note cycle. A liability-owner split feeds the damages-and-shrinkage GL account separately from the trade-spend account, and the net-of-returns sales base feeds the PLISFPI certification calculation and the GSTR-9 turnover reconciliation.

### Returnable Packaging GST: When Does a KLT Bin Become a Taxable Supply (Auto Components)?

Source: https://www.terra-insight.com/insights/returnable-packaging-gst-klt-bin-auto-india/

- **Problem:** Returnable KLT/GLT bins and special-purpose dunnage move under a Rule 55 delivery-challan model with no GST on movement, but non-return within the agreed window converts the movement into a deemed supply triggering 18 percent GST plus Section 50 interest on the bin's current market value — complicated by security-deposit forfeit treatment, cross-plant bin movement across multiple OEM plants, and damage/loss accounting that must be evidenced before write-off.
- **Logic:** Hold a bin-pool master per OEM with serviceable inventory, security deposit per bin and contractual return window; track every outbound dispatch on Rule 55 delivery challan with expected return date; reconcile return movements against the same pool ID; for any bin past the return window without a documented loss or damage record, accrue GST at 18 percent of current bin value plus Section 50 interest from the dispatch date; on forfeit of security deposit recognise it as consideration aligned to the deemed-supply event; consolidate Plant A despatch and Plant B return into a single OEM-level pool view.
- **Config:** Bin-pool master per OEM (KLT, GLT, dunnage variants with HSN and current market value), contractual return-window calendar, Rule 55 delivery-challan register linked to e-way bills, return-receipt register, security-deposit liability ledger, deemed-supply accrual workflow with Section 50 interest computation, damage/loss evidence register, cross-plant rollup view.
- **Output:** A per-OEM returnable-packaging dashboard showing serviceable bin inventory by pool, dispatched bins past the return window flagged for deemed-supply accrual, 18 percent GST and Section 50 interest exposure, security-deposit ledger balance with forfeit queue, damage/loss write-off queue with evidence status, and a cross-plant rollup of bin location with last-known dispatch and expected return dates.

### Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers

Source: https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india/

- **Problem:** Auto components ship in returnable containers — KLT/GLT bins, trolleys, pallets, dunnage — moved under a Rule 55 delivery challan with no GST because they are not a supply, expected to cycle back empty. Across multiple OEM plants on milk-run logistics the bin-out and bin-in flows scramble, bins go missing, security deposits drift out of step with the physical float, and an unreturned bin beyond its window can become a GST deemed supply — none of which a goods-invoice reconciliation captures.
- **Logic:** Maintain a per-bin-type circulation ledger: every outward Rule 55 challan (bin-out, with declared value and e-way bill where applicable) is tied to an inward return challan/receipt (bin-in); cumulative out minus in per bin type per counterparty is the float in custody; reconcile the float against the security-deposit ledger at the agreed per-bin value; age unreturned bins against the contractual return window and quantify the GST deemed-supply exposure (tax invoice on lost/retained bins); reconcile milk-run manifests by netting flows rather than pairing dispatch-to-return.
- **Config:** Bin master keyed by bin type (KLT/GLT/trolley/pallet/dunnage/special), ownership (OEM/supplier/pooled), declared per-bin value and return window; outward and inward Rule 55 challan register with e-way bill linkage; counterparty/plant dimension for multi-plant circulation; security-deposit ledger by counterparty; milk-run manifest feed; GST mapping for the deemed-supply tax invoice on non-returned bins.
- **Output:** A per-bin-type, per-counterparty circulation reconciliation showing cumulative bin-out vs bin-in and the float in custody, a deposit-vs-float comparison at agreed per-bin value, an ageing of unreturned bins against the return window with quantified GST deemed-supply exposure, milk-run flow netting against manifests, and an exception queue for missing bins, deposit drift, mis-routed containers across plants, and bins approaching the GST trigger window.

### Returns and RTV at Branded Apparel Retail — Credit Note Section 34

Source: https://www.terra-insight.com/insights/returns-rtv-branded-apparel-credit-note-section-34/

- **Problem:** A branded apparel principal — an Aditya Birla Fashion and Retail label or a Trent Ltd Westside/Zudio label — with quarterly sales exceeding ₹80 crore and online return rates in the 25 to 40 percent industry benchmark generates thousands of Section 34 credit notes per quarter across two return legs. Marketplace customer returns arrive with a 30-day lag after the customer-purchase date; RTV flows from stores arrive with a seasonal lag at the end of Q3 winter or Q1 summer. Every credit note must reduce output GST on GSTR-3B, disclose on GSTR-1 Table 9B, and align to the ECO's returns credit ledger (with the handling-fee service invoice booked separately at 18 percent). The 30 November following-FY deadline under Section 34(2) is unforgiving — credit notes issued after that date cannot reduce output tax. Manual reconciliation loses SKU-level line items across 12,000+ return records, mis-maps ECO returns credit to the original invoice, and typically leaves output GST over-stated by 8 to 12 percent because a subset of credit notes miss the deadline or fail to file on Table 9B.
- **Logic:** Ingest the ECO returns credit ledger and the store-side RTV register into a single returns master keyed by original tax invoice reference; expand each return line item into an expected Section 34 credit note with taxable value, GST at the original rate, and issue-by date derived from the 30 November following-FY deadline plus a safety margin. Reconcile the credit-note issuance register against the returns master and flag any return line item without a matching credit note beyond 60 days. Post the ECO's returns handling fee as a separate service supply at 18 percent GST — do not net against the credit note. Cross-check the aggregate credit-note taxable value against GSTR-1 Table 9B for the return-declaration month and the output tax reduction against GSTR-3B Table 3.1(a). Reconcile the ECO's Section 52 TCS statement — the returned-supply exclusion from the net TCS base — against the credit-note register.
- **Config:** Brand GSTIN master with the state-wise registration table (multi-state warehouses generate multi-GSTIN complexity); ECO master (Myntra, Ajio, Flipkart Fashion, Nykaa Fashion) with each ECO's returns credit ledger feed format and TCS statement feed; store master with per-store GSTIN and same-legal-entity flag (distinguishes RTV credit note from stock-transfer delivery challan); SKU master with HSN, GST rate (Chapter 61 knitted apparel; Chapter 62 woven apparel; typical 5 percent below ₹1,000 per piece; 12 percent above ₹1,000 per piece), and returns policy metadata (marketplace 30-day window; store RTV seasonal cycle); the Section 34(2) 30 November following-FY deadline calendar with alert thresholds at 90, 60, and 30 days from deadline; ECO returns-handling-fee rate card per ECO (typically 2 to 5 percent of the returned value, invoiced separately at 18 percent GST).
- **Output:** A month-end returns reconciliation pack: opening balance of unclosed return line items by ECO and by store, period customer returns from ECO returns credit ledger (with SKU-level detail), period RTV from stores, credit-note issuance register with each note tied to the original tax invoice, GST reduction booked to GSTR-3B Table 3.1(a), GSTR-1 Table 9B disclosure draft, ECO Section 52 TCS statement reconciliation (returned-supply exclusion from the net TCS base), and a Section 34(2) deadline exposure list showing every open return that must be credit-noted before the 30 November following-FY cut-off. Aged returns beyond 60 days without credit-note issuance are flagged for operations follow-up. Handling-fee service invoices from each ECO are booked separately at 18 percent GST with ITC eligibility confirmed.

### Returns and RTO Accounting for D2C Brands: Reverse Logistics and GST Credit Notes

Source: https://www.terra-insight.com/insights/returns-rto-accounting-d2c-india/

- **Problem:** D2C brands with 18 to 28 percent return rates on fashion and 6 to 12 percent on personal care face a high-cardinality reverse-flow reconciliation problem — RTO, CIR, exchange, and quality return AWBs reconciled against 3PL billing, restocked-vs-refurbished-vs-written-off inventory disposition, Section 34 credit-note timing within the financial-year window, and Rule 42 ITC reversal on write-offs, where unstructured returns accounting absorbs 1 to 3 percent of GMV invisibly across reverse logistics overcharge, restocking expense in COGS, and missed credit-note windows.
- **Logic:** Build a returns ledger per AWB with original-order linkage, return category, 3PL charge, inspection outcome, and inventory disposition (restock, refurbish, write-off). Reconcile reverse-logistics charges against 3PL billing at AWB level. Track restocking expense separately from COGS. Issue Section 34 credit notes within the financial-year window for returns received outside the original tax period. Apply Rule 42 ITC reversal on write-offs in GSTR-3B.
- **Config:** OMS-to-returns linkage per AWB, 3PL rate card per return type and city tier, inspection outcome taxonomy (resaleable, refurbishable, write-off), refurbishment cost tracker, Section 34 credit-note timing calendar by financial year, Rule 42 ITC reversal calculation per write-off batch, and discarded-stock provisioning schedule.
- **Output:** A reconciled returns ledger per AWB with reverse-logistics charge variance against 3PL rate card isolated, restocking and refurbishment expense booked separately from COGS, Section 34 credit notes issued within window, Rule 42 ITC reversal correctly reported in GSTR-3B, and a board-ready return-rate and net-realisation view per SKU and per channel.

### Building the Board Case for Revenue Leakage Recovery: A CFO Guide

Source: https://www.terra-insight.com/insights/revenue-leakage-board-justification-india/

- **Problem:** Indian CFOs frequently bring revenue-leakage recovery business cases to the board that get rejected, deferred, or approved as one-shot projects rather than sustained programs. The common failure modes are asserted (rather than measured) leakage rupees, over-claimed recovery rates, missing working-capital overlay in the payback calculation, weak internal-champion structure, and no defensible audit-committee reporting cycle. A defensible board case addresses each of these with a structured three-page memo, a measured per-class rupee build-up, a 60-75% year-one recovery target, a combined inflow payback model, and a three-layer ownership structure that creates succession depth.
- **Logic:** Build the rupee number by class using the four-week baseline measurement output. Model year-one recovery at 40-55% and year-three at 65-75% with class-specific override (fee-deduction 70-85%, tax-deduction 60-80%, OEM short-pay 50-65%, ITC lagged 70-85% lagged plus 25-40% permanent). Include working-capital overlay computed per the days-recon-delay framework at the business's realistic cost-of-capital. Compute payback against combined recovered-leakage plus working-capital saving inflows against headcount-and-software-plus-setup outflows. Position three-layer ownership and audit-committee cycle. Carry sensitivity analysis on recovery rate, working-capital rate, and program cost.
- **Config:** Three-page memo template with rupee number page, operating model page, investment ask page. Appendix template with regulator-anchor table, per-class worked examples, baseline-measurement methodology. Sensitivity-analysis table with recovery rate, cost-of-capital, and program cost dimensions. Audit-committee reporting cycle template tied to the board memo. Three-layer ownership chart with named individuals and back-up. Payback calculator with year-by-year cash flow projection. Quarterly tracking dashboard for post-approval execution.
- **Output:** An approved board case for a sustained revenue-leakage recovery program with defined headcount, software-licence cost, one-time setup, expected year-one and year-three recovery rupees, and audit-committee reporting cycle. Quarterly leakage trend reporting in the standard audit-committee pack. An internal-champion three-layer structure with succession depth. A program review cycle that adjusts recovery targets and operating cadence based on observed performance.

### Revenue Leakage in Indian Finance Teams: The Seven Classes Framework

Source: https://www.terra-insight.com/insights/revenue-leakage-india-finance-teams-guide/

- **Problem:** Indian finance teams running 2–6 person reconciliation desks against tens of thousands of monthly transactions absorb structural, repeatable revenue losses across TDS credits not appearing in Form 26AS or Form 168, ITC lapsed under Rule 36(4) or reversed under Rule 37, undisclosed MDR and platform settlement fees, unreconciled NACH bounce-charge recoveries, sub-rupee rounding compounded across millions of rows, partial payments closed as full at month-end, and a residual catch-all of unexplained variance written off as a JV. Without a named class for each pattern, every month-end closes leakage by guesswork and the recovery trail is permanently broken.
- **Logic:** Apply a seven-class variance taxonomy at the point of reconciliation: FEE_DEDUCTION for platform and bank fee variance against contracted rate, TAX_DEDUCTION for TDS receivable not in Form 26AS or 168, DISCOUNT_APPLIED for discount applied without authorisation tag, ROUNDING for sub-₹10 paise variance, PARTIAL_PAYMENT for invoice short-settled against its outstanding, PENALTY_OR_INTEREST for Section 50 interest, Section 416 interest, NACH bounce charge or late-fee debit, UNEXPLAINED for residual variance with no rule match. Each class carries a regulator anchor, a detection signal, and a recovery action so the Discovered Money register can age recovery by class.
- **Config:** Variance taxonomy seven-class enum applied at reconciliation engine output, regulator-anchor table mapping each class to the operative section (Section 393/394/413/416, Rule 36(4)/37, NACH circular, contract clause), Discovered Money register keyed by class and ageing bucket, week-one detection-signal checklist for CFO baseline, recovery-action library by class with owner and standard SLA, audit-trail field on every reclassified line capturing the original class and the corrected class.
- **Output:** A monthly Discovered Money register that decomposes total reconciliation variance into the seven classes with regulator anchor and recovery owner per row, a Recovery Aged Trial Balance by class showing stuck / at-risk / recoverable rupees, a quarterly leakage-class trend report for the audit committee, and a permanent reduction in the unexplained-variance write-off line once classified variance moves to the recovery queue instead of the JV.

### Revenue Recognition for Auto-Component Manufacturers under Ind AS 115

Source: https://www.terra-insight.com/insights/revenue-recognition-auto-component-ind-as-115-india/

- **Problem:** Auto-component Tier 1 suppliers run parallel revenue streams — long-running scheduling agreements with daily kanban call-offs, discrete POs for aftermarket and spares, OEM-paid tooling bundled with part contracts, RMPV escalation claims as variable consideration, and FOMP / warranty back-charges as variable consideration reductions. Ind AS 115's five-step model has to be applied consistently across all four streams, with variable-consideration constraint at every period-end and tooling capitalisation tested against the bundled-vs-distinct criteria. A typical ₹240 crore Tier 1 booking a single quarter-end has to apply the model across 8 to 12 OEM customers, 30 to 50 active SAs, 8 to 20 tooling-amortisation lines, and a rolling FOMP provision — none of which a generic ERP revenue module handles together.
- **Logic:** Apply Ind AS 115 step-by-step. Identify each scheduling agreement plus discrete PO as a contract. Identify performance obligations — part deliveries at GRN as point-in-time, tooling as bundled-or-distinct based on programme-life commitment, engineering services where contractually separable. Determine transaction price including RMPV escalation estimate (constrained per paragraph 56) and net of FOMP back-charge provision (paragraph 51). Allocate price across performance obligations on standalone-selling-price basis where multiple POs exist. Recognise revenue at point-in-time GRN for parts, over the production schedule for bundled tooling, at ownership transfer for distinct tooling.
- **Config:** Customer master with OEM contract type flag (SA / discrete PO), performance-obligation register per contract with timing rule (point-in-time GRN / over-time / programme-end), tooling lineage table tagged bundled-or-distinct with amortisation schedule, variable-consideration estimator with method flag (expected-value or most-likely-amount), constraint rule library mapped to OEM and claim type, FOMP provision rate per OEM customer historical baseline, GRN-event capture from OEM portals and dispatch system.
- **Output:** A daily revenue recognition register per contract showing GRN-driven point-in-time bookings for parts, monthly amortisation lines for bundled tooling, period-end variable-consideration adjustment journals for RMPV (additive) and FOMP (deductive), an audit-defensible trail per contract linking the five-step application to the booked revenue, and a quarterly disclosure pack for the Ind AS 115 contract-balance reconciliation note.

### Revenue Leakage Recovery Playbook for Indian Enterprises

Source: https://www.terra-insight.com/insights/revenue-leakage-recovery-india-playbook/

- **Problem:** Indian finance teams that suspect revenue leakage rarely have a structured recovery program. Recovery happens ad-hoc — disputes filed when someone notices, escalations raised when a customer is otherwise contacted, write-offs taken at quarter-end. The result is that disputable leakage ages out, structural leakage gets accepted by default, and the audit committee cannot tell whether the leakage trend is improving. A formal recovery playbook with per-class owners, SLA library, Discovered Money register, and quarterly cycle turns recovery from project work into a standing operational capability.
- **Logic:** Map each of the seven leakage classes to a named owner, a regulator or contractual anchor, a dispute window or recovery action, a standard SLA, and an escalation route. Operate a Discovered Money register that quantifies recoverable leakage by class with stuck / at-risk / recoverable / recovered / structurally lost status. Run a four-week baseline measurement to size each class. Publish dispute-template and escalation-route libraries. Operate a monthly recovery review and a quarterly audit-committee cycle that reports rupees recovered, rupees in pipeline, rupees structurally lost. Integrate with existing reconciliation engine capability to scale residual handling.
- **Config:** Seven-class owner matrix with named individuals and back-up. Regulator-and-contractual anchor table by class with operative reference. SLA library per class with dispute window, escalation trigger, recovery action. Dispute-template library per class with regulator-aligned language. Discovered Money register with per-class rows, status field, and recovery-state machine. Monthly recovery review cycle. Quarterly audit-committee pack template. Annual playbook review covering owner rotation, SLA tightening, and template updates.
- **Output:** A monthly Discovered Money register decomposing total recoverable leakage by class with recovery probability bands. A weekly dispute-and-escalation operating queue routed to owners. A quarterly audit-committee leakage pack with rupees recovered, rupees in pipeline, rupees structurally lost, and trend. An annual playbook review report covering owner-matrix changes, SLA tightening, recovery-rate improvement, and infrastructure investment recommendations.

### GST RFD-01 Monthly Filing for Textile Inverted-Duty Refund

Source: https://www.terra-insight.com/insights/rfd-01-monthly-filing-textile-inverted-duty-refund/

- **Problem:** A textile principal running a fabric-to-garment chain claiming inverted-duty refund under Rule 89(5) must file GST RFD-01 with four statement annexures (turnover of inverted-rated supply, Net ITC, adjusted total turnover, tax payable on inverted-rated supply), track the fifteen-day RFD-03 deficiency-memo clock, monitor the sixty-day RFD-06 sanction clock under Section 54(7), and reconcile the bank credit against the sanctioned amount — every month for a monthly filing rhythm. Manual tracking loses ARNs, misses RFD-03 rectification windows, and cannot demonstrate the officer status trail at year-end audit. Missing the fifteen-day RFD-03 response window forces a fresh RFD-01 filing that shifts the claim cycle by 30 to 45 days and locks up further working capital.
- **Logic:** Build a claim register keyed by relevant period with the ARN as primary key. On RFD-01 filing, capture Statements 1 to 4 totals, supporting document checklist status, and the filing timestamp. Poll the GST portal status (or ingest the officer notification email) daily to catch the RFD-02 acknowledgement (start of the 60-day clock), the RFD-03 deficiency memo (stops the clock and requires fresh filing), the RFD-06 sanction order (issues the payment advice), and the RFD-08 payment advice (triggers bank credit). Alert the compliance team at day 12 of the RFD-03 window (three days before expiry), at day 55 of the RFD-06 window (five days before Section 54(7) statutory deadline), and on any credit-received-not-matched exception in the bank statement reconciliation.
- **Config:** GSTIN master with authorised representative details and DSC for RFD-01 filing; HSN master with inverted-duty flag per HSN (5205 yarn 5 percent, 5208 fabric 5 percent, 6006 knit fabric 5 percent, 6109 T-shirt 5 percent or 12 percent depending on retail sale price); GSTR-1 and GSTR-2B ingest feed for monthly turnover and ITC data; electronic credit ledger balance query; deficiency-memo alert threshold at 12 days from filing (three days before the fifteen-day statutory window); sanction-clock alert threshold at 55 days from RFD-02 (five days before the sixty-day Section 54(7) window); bank statement ingest for credit-match against sanctioned amount; escalation matrix to range officer and Additional Commissioner (Refunds) for 60+ day pending claims.
- **Output:** A month-end RFD-01 reconciliation pack: (1) claim register with ARN, relevant period, refund claimed, Statement 1 to 4 totals, supporting document checklist; (2) officer status trail with RFD-02, RFD-03 (if any), RFD-06, RFD-08 timestamps and day-counts against statutory windows; (3) bank credit register with sanction amount, credit received, and mismatch flags; (4) exception log for RFD-03 rectification cycles, partial rejections, and delayed sanctions with Section 54(12) statutory interest at 6 percent per annum accrued; (5) cash-flow projection showing expected credit dates for open claims. The pack satisfies the statutory audit trail, the Section 65 GST audit, and the working-capital forecasting cycle.

### RMPV Calculation Formula for Auto-Component Suppliers: Step-by-Step Worked Examples

Source: https://www.terra-insight.com/insights/rmpv-calculation-formula-auto-component-india/

- **Problem:** Auto-component finance teams must compute, document and provision RMPV claims correctly each cycle across single-material and multi-material parts, with averaging methods that change the input, settlement lags that defer the cash, and trigger bands or caps that change the formula. Errors create OEM disputes, mis-timed GST events under Section 34, and Ind AS 37 provisioning errors.
- **Logic:** Apply Claim = (Current_Index − Base_Index) × Material_Weight × Quantity_Supplied × Adjustment_Factor per material per part. Use the contractual averaging method for Current_Index. Apply trigger bands or caps via the Adjustment_Factor or as a modified differential. Provision at quarter-end on observed index movement under Ind AS 37; true up on index publication and on OEM acceptance. Route positive results to a supplementary (debit) invoice with current-period GST; route negative results to a Section 34 credit note within the 30-November cutoff. Material-portion claims do not attract Section 393(1) Sl. 6(i) contractor TDS.
- **Config:** Part master row per material carrying material weight, base index level, base price portion attributable to the material, named reference index, averaging method, settlement lag, trigger band or cap if any. Index feed by period for each named index. Quantity-supplied feed by revision period per OEM. Quarter-end provision ledger. GST routing logic splitting upward vs downward results with Section 34 cutoff watch. OEM-dispute status field per claim line.
- **Output:** A per-claim worksheet showing inputs (Current_Index, Base_Index, Material_Weight, Quantity, Adjustment_Factor), the computed differential, the rupee claim per material, the supplementary-invoice or Section 34 credit-note action with GST on the differential, the quarter-end provision-vs-actual true-up entry, and the Section 34 cutoff watch flag.

### Raw Material Price Variation (RMPV) Clauses in Auto-Component Contracts: How They Actually Work

Source: https://www.terra-insight.com/insights/rmpv-clause-auto-component-india-explained/

- **Problem:** Auto-component prices float against raw-material indices through RMPV clauses: steel parts track JPC HR/CR coil, aluminium/copper/zinc track LME (rupee and premium adjusted), plastics track polymer benchmarks, PGM-bearing parts track precious-metal benchmarks. Each revision cycle the supplier raises a supplementary invoice on a rise or the OEM claws back via a Section 34 credit note on a fall — retrospectively, against an index that publishes after the period closes, on multi-material parts where each material has its own index, with a 2-3 quarter negotiation tail.
- **Logic:** Recompute each RMPV claim against the contractual formula — base price plus material-weight times index movement on the named index per material, conversion portion held fixed — for goods supplied in the revision period; classify the result as a supplier supplementary (debit) invoice (taxable upward revision, current period under Section 12/13 time-of-supply) or a supplier GST credit note under Section 34 (downward revision, within the 30 November cutoff after the close of the relevant financial year). Apply the contractual averaging method (monthly average / three-month moving / quarter-end spot) and the settlement lag. Provision the expected claim at quarter-end on observed index movement; true it up on index publication and on OEM acceptance.
- **Config:** Part master carrying base price, base index level, material type and weight per part (one row per material for multi-material parts), named reference index per material (JPC HR/CR coil, LME with rupee and premium adjustment, polymer grade, PGM benchmark), averaging method, revision cycle (monthly/quarterly), settlement lag, and any clause-specific adjustment factor (e.g. supplier absorbs first 3% of movement). Index feed by period. GST mapping splitting price differential into supplementary-invoice (upward) vs Section 34 credit-note (downward) paths with the 30 November cutoff tracked. Quarter-end RMPV provision ledger with OEM-dispute status field.
- **Output:** A per-part RMPV reconciliation showing computed price differential per supplied quantity against the named index per material, the supplementary-invoice or credit-note action with GST on the differential, a quarter-end provision-vs-actual true-up, a Section 34 cutoff watch on downward revisions, and an exception queue for index-formula disputes, proxy-index mismatches, multi-material netting positions, and revisions tied to the wrong tax period.

### RoDTEP Appendix 4RE — AA, EOU, SEZ Textile Claim Reconciliation

Source: https://www.terra-insight.com/insights/rodtep-appendix-4re-aa-eou-sez-textile-claim/

- **Problem:** Indian textile exporters shipping from SEZ, EOU, and AA units face a distinct RoDTEP reconciliation surface separate from the Domestic Tariff Area case. Appendix 4RE — notified in DGFT Notification 10/2025-26 with effect from 1 June 2025 — carries a different tariff-line rate schedule than Appendix 4R for the same 8-digit ITC(HS) code, and applies only where the shipping bill export-type flag correctly identifies the AA / EOU / SEZ scheme. A mis-flagged shipping bill from an SEZ facility filed under the DTA route prices the claim against the wrong annexure or drops the claim entirely at ICEGATE scroll; a bill filed correctly but with an ITC(HS) code that is not on the Appendix 4RE annexure returns a zero scrip credit; and the RoDTEP claim must reconcile independently against the Advance Authorisation export obligation register, the e-BRC USD realisation, and the parallel Rule 89(5) inverted-duty refund on the yarn-to-fabric leg.
- **Logic:** Build an export register keyed by shipping bill number that captures scheme flag (FREE / ROD / SEZ / EOU / AA), source unit code (SEZ unit registration number or EOU letter of permission number), ITC(HS) 8-digit code, FOB USD, customs exchange rate at LEO date, and Appendix 4R or Appendix 4RE tariff-line rate as applicable. Match each shipping bill to its scrip credit line on the ICEGATE RoDTEP scroll — the scroll runs weekly and issues an electronic scrip against every valid claim. Match the scrip credit rupee value to the expected claim value computed from FOB × rate × customs INR/USD conversion, and route the gap to one of three states: correct scheme flag but ITC(HS) not on Appendix 4RE annexure (zero credit — commercial decision on whether to re-classify), scheme flag mismatch (route to shipping bill amendment on ICEGATE), or rate applied per annexure but scroll running late (SLA follow-up). Parallel-key each shipping bill to its e-BRC USD realisation from the authorised dealer bank feed and flag any consignment where e-BRC USD is materially short of shipping bill FOB USD. For AA-linked consignments, key each shipping bill also to the source AA licence file number and cross-post to the export obligation ledger.
- **Config:** Shipping bill master feed from ICEGATE — bill number, scheme flag, source unit code, ITC(HS) 8-digit, FOB USD, LEO date, customs exchange rate. Appendix 4R and Appendix 4RE tariff-line rate tables — separate lookup indexed by ITC(HS) code, effective from 1 May 2025 (4R) and 1 June 2025 (4RE), both valid till 31 March 2026. RoDTEP scrip scroll feed from ICEGATE — scrip number, shipping bill reference, scrip rupee value, scroll date. e-BRC feed from authorised dealer banks — bill of lading reference, USD realised, INR credited, bank rate, realisation date. AA licence master — file number, export obligation value in USD, obligation period end date. SEZ unit master — unit registration number, SEZ authority approval reference, letter of approval date. Section 89(5) inverted-duty refund register linked at shipping bill level for parallel-tracked refund flows.
- **Output:** A monthly RoDTEP reconciliation pack for the AA / EOU / SEZ book: opening pending scrip register, period shipping bills filed under scheme flags, period scrip credits received per Appendix 4R and Appendix 4RE, period claims blocked (with reason codes — scheme-flag mismatch, ITC(HS) off-annexure, e-BRC short realisation, AA licence expired), period scrips utilised or transferred, closing pending scrip register. Per-shipping-bill trace card links the ICEGATE bill, the annexure applied, the scrip issued, and the e-BRC realisation. AA-linked shipping bills also feed a per-licence export obligation ledger, and Rule 89(5) inverted-duty refunds run as a parallel column so that the yarn-to-fabric refund and the RoDTEP scrip are not double-counted or cross-netted in the export incentive receivable.

### RoDTEP Appendix 4R DTA Textile Claim Reconciliation

Source: https://www.terra-insight.com/insights/rodtep-appendix-4r-dta-textile-claim/

- **Problem:** Indian textile exporters shipping DTA consignments of cotton fabrics under HS Heading 5208 (and adjacent chapters) accrue RoDTEP claim receivables shipment-by-shipment at the Appendix 4R rate applicable to each 8-digit HS line, but the shipping-bill HS Code, the notified Appendix 4R rate, any value cap on the line, the port EDI SB-FOB, and the DGFT ICEGATE scrip credit rarely tie out on the first pass. The 24/26 May 2025 DGFT notification revised the Appendix 4R schedule with effect from 1 May 2025 and set scheme validity through 31 March 2026, so exporters carrying pre-1-May and post-1-May shipments must reconcile against two rate regimes within the same financial year.
- **Logic:** Build a shipping-bill register keyed by SB number, SB date, port code, invoice reference, HS Code (8-digit), SB-declared FOB in INR, RoDTEP scheme-code line flag, and notified Appendix 4R rate for the applicable date. Cross-reference each SB line against the Appendix 4R rate schedule effective on the SB date, applying any value cap notified for that HS line. Match the computed claim to the ICEGATE RoDTEP scroll credit posted to the exporter's ledger; classify each SB into scroll-credited, in scroll cycle, queried by Customs, or excluded. Track e-scrip generation against credited balance and utilisation against Basic Customs Duty on import consignments. Monthly reconciliation ties SB-computed claim to ICEGATE ledger credit to e-scrip inventory to BCD utilisation.
- **Config:** HS Code master with 8-digit granularity mapped to Appendix 4R rate effective from 1 May 2025 (and prior rates for pre-1-May shipments); Appendix 4R value cap register per HS line; shipping-bill feed from the exporter's freight forwarder or in-house export desk; ICEGATE RoDTEP scroll credit feed by SB number; e-scrip inventory register by scrip number, credited amount, utilised amount, and expiry; port code and Customs House filter for multi-port exporters; SB scheme-code flag validation (RoDTEP-eligible SB must carry the scheme-code line at filing time, otherwise the claim is forfeit).
- **Output:** A monthly Appendix 4R reconciliation pack: opening RoDTEP receivable, period SB-computed claim (SB-declared FOB times notified rate, capped where applicable), period ICEGATE scroll credit, period e-scrip generation, period e-scrip utilisation, period exclusions (SBs missing scheme code or falling under an excluded HS line), and closing receivable. Per-SB variance report surfaces HS-code mismatches, rate-lookup errors, value-cap truncations, and SB-FOB versus invoice-FOB gaps for the controller to resolve before the year-end audit.

### RoDTEP Claim Reconciliation for Textile Exporters in India

Source: https://www.terra-insight.com/insights/rodtep-claim-reconciliation-textile-india/

- **Problem:** Indian textile exporters run two parallel RoDTEP claim streams — Appendix 4R for Domestic Tariff Area shipments and Appendix 4RE for shipments made under Advance Authorisation, from Export Oriented Units, and from Special Economic Zones — at different tariff-line rates that DGFT Notification 10/2025-26 revised effective 1 May 2025 for DTA and 1 June 2025 for AA/EOU/SEZ. The reconciliation chain runs from shipping bill to Appendix rate lookup to e-BRC realisation to duty-scrip credit, and every hop is a leakage point. Knitwear and woven-apparel exporters that do not maintain a per-shipping-bill four-node reconciliation typically lose four to nine percent of their entitled RoDTEP value each year to wrong-appendix filings, stale HS code mappings, missing e-BRCs, exchange-rate revaluation gaps, and per-unit cap breaches at scrip credit stage.
- **Logic:** Build a shipping-bill register keyed by shipping-bill number, port code, HS code, export scheme code, FOB value in foreign currency, and RoDTEP claim flag. Enrich each row with the correct appendix — 4R when the scheme code is DTA, 4RE when the scheme code is AA, EOU, or SEZ — and lookup the current rate and per-unit cap from the DGFT master effective on the let-export-order date. Compute the RoDTEP entitlement at rate × FOB or per-unit cap × quantity, whichever is lower. Feed the authorised-dealer bank's e-BRC register in parallel and match each e-BRC to its shipping bill by shipping-bill number and port. On e-BRC match, revalue the entitlement at the realised INR value. Reconcile the DGFT scrip credit statement back to the entitlement register and flag any per-shipping-bill gap for investigation.
- **Config:** Shipping-bill master feed from ICEGATE with HS code, export scheme code, FOB, and let-export-order date; Appendix 4R and Appendix 4RE rate masters from DGFT with effective date ranges and per-unit caps; e-BRC feed from the authorised-dealer bank keyed to shipping-bill number; DGFT scrip credit statement feed; scheme-code to appendix lookup rule (DTA to 4R; AA, EOU, SEZ to 4RE); RoSCTL rate master for Chapter 61, 62, and 63 lines that run in parallel; foreign-currency to INR revaluation logic at e-BRC realisation date; per-shipping-bill exception queue with resolution owner.
- **Output:** A monthly RoDTEP reconciliation pack: opening claim-provisional balance, period shipping bills filed with appendix and entitlement, period e-BRCs realised with revalued entitlement, period scrip credits received, period exceptions by failure mode (wrong appendix, stale HS code, missing e-BRC, revaluation gap, per-unit cap breach), and closing claim-provisional balance. Per-shipping-bill drill-down surfaces stuck value with resolution owner. Parallel RoSCTL reconciliation runs on the same base for Chapter 61, 62, and 63 shipping bills. The pack feeds the export finance report to the CFO and the DGFT scrip verification defence file.

### RoSCTL Claim Reconciliation for Garment and Made-Ups Exporters

Source: https://www.terra-insight.com/insights/rosctl-claim-reconciliation-garment-made-ups-india/

- **Problem:** A Bengaluru or Tiruppur knitted-garment exporter shipping Chapter 61 apparel to the United States or European Union must file two parallel scrip claims — RoSCTL and RoDTEP Appendix 4R — against every shipping bill, each with its own rate schedule, its own scheme flag on the export declaration, and its own timeline for scrip issuance. The claims are contingent on e-BRC issuance by the authorised dealer bank once foreign remittance is realised. Manual reconciliation misses shipping bills that were filed without one or both scheme flags, over-claims RoSCTL on shipping bills where realisation fell short of declared FOB, and fails to detect the ITC-04 job-work chain exposure that would create a downstream scrip clawback if the underlying yarn dispatch triggers Section 143 CGST deemed-supply.
- **Logic:** Build a shipping bill register keyed by shipping bill number and date; ingest the export declaration flags for RoSCTL and RoDTEP scheme codes; ingest the e-BRC feed from the authorised dealer bank and match by shipping bill number to compute realised value against declared FOB. Compute the RoSCTL claim as realised FOB value multiplied by the HS Code-wise rate notified by the Ministry of Textiles; compute the RoDTEP claim as realised FOB value multiplied by the Appendix 4R rate for DTA exports (or Appendix 4RE rate for AA/EOU/SEZ exports). Track scrip issuance timelines on the DGFT portal and alert on shipping bills approaching the FTP-notified realisation deadline without e-BRC. Cross-link every shipping bill to the ITC-04 job-work chain that produced the exported goods and surface any Section 143 1-year clock exposure that would jeopardise the scrip claim retrospectively.
- **Config:** Shipping bill register with shipping bill number, date, port of export, HS Code, description, quantity, declared FOB value, currency, and scheme flags (RoSCTL YES/NO, RoDTEP Appendix 4R YES/NO); Ministry of Textiles RoSCTL rate schedule by 8-digit HS Code and validity period; DGFT RoDTEP Appendix 4R rate schedule by 8-digit HS Code with validity period (currently till 31 March 2026 per Notification 10/2025-26); e-BRC feed integration with authorised dealer bank identifier, AD Code, and BRC serial number; realisation timeline configuration (nine months default from date of shipment, extendable per FTP); ITC-04 job-work chain linkage by SKU-to-shipping-bill mapping; Section 143 1-year clock configuration keyed to the original principal-to-hop-1 yarn dispatch date; scrip ledger integration with DGFT portal for scrip issuance tracking and usage against Basic Customs Duty on subsequent imports.
- **Output:** A shipment-level scrip claim pack: shipping bill number, LEO date, HS Code, declared FOB, realised FOB from e-BRC, realisation shortfall (if any), RoSCTL rate and claim value, RoDTEP Appendix 4R rate and claim value, combined scrip credit, and scrip issuance status on DGFT portal. Realisation timer view highlights shipping bills approaching the FTP-notified deadline without e-BRC, giving the export finance team runway to escalate remittance follow-up. ITC-04 linkage view highlights shipping bills whose underlying yarn dispatch is at 270+ days on the Section 143 clock, giving operations the runway to close the chain before deemed-supply triggers. Scrip ledger view tracks scrip credit balance, transfers, and utilisation against import Basic Customs Duty.

### Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic

Source: https://www.terra-insight.com/insights/round-number-clustering-fraud-detection/

- **Problem:** A person constructing fabricated bank statement transaction amounts manually tends to choose psychologically round figures, producing a higher concentration of amounts ending in multiple zeros than genuine spending data would generate. Standard transaction review does not measure this distribution.
- **Logic:** Compute the proportion of transaction amounts that end in three or more zeros across the full statement. Exclude ATM withdrawal transactions from this calculation — Indian ATMs dispense in ₹100/₹200/₹500 multiples, making round-number ATM transactions structurally normal. If the adjusted concentration exceeds a calibrated threshold for the account type, flag for human review.
- **Config:** ATM withdrawal exclusion: identify transactions with ATM/ATW/cash withdrawal keywords in the description. Adjust baseline threshold for accounts where informal business or contractor payments explain elevated round-number rates. Apply check separately to credits and debits to detect selective fabrication of income entries.
- **Output:** Round-number concentration percentage (ATM-adjusted), classification (within normal range / elevated / high — review), and a breakout showing round-number rate for credits versus debits separately, presented in the fraud signals section of the analysis report.

### Rubber and Polymer Component Reconciliation for Indian Auto Suppliers: Hoses, Bushes, Seals

Source: https://www.terra-insight.com/insights/rubber-polymer-component-reconciliation-auto-india/

- **Problem:** An Indian rubber-component supplier produces fuel hoses, cooling hoses, suspension bushes, fluid seals, vibration isolators and gaskets across five elastomer families (NBR, EPDM, CR, silicone, SBR), each with a distinct compound formula carrying natural rubber, synthetic polymer, carbon black, plasticiser, vulcanising chemicals and protectants. Reconciliation must close compound-to-cured-part identity across mixing, moulding or extrusion, curing and trimming, with first-pass cure yield of 88-95 percent and irrecoverable scrap, index-linked RMPV per ingredient (natural rubber against Kerala / Kottayam RSS-4 published price, synthetic against monomer index, carbon black against feedstock index, oils against crude), Ind AS 16 mould-cycle amortisation, Section 393(1) Sl. 6(i) codes 1023/1024 TDS on conversion-service billing or Section 194Q on goods sale, and 18 percent GST on conversion under HSN 9988 or chapter-40 GST on finished component sale.
- **Logic:** Maintain compound master per part with ingredient list (natural rubber percentage, synthetic polymer percentage, carbon black grade and loading, plasticiser type and quantity, accelerator package, sulfur loading, protectants) and per-ingredient index reference. Per shift, log compound mixed, parts moulded or extruded, parts cured, parts passed inspection, parts scrapped. Close compound-to-cured-part identity per shift. Compute per-ingredient RMPV claim against monthly index. Post mould-cycle amortisation under Ind AS 16. Map TDS deduction lineage to Section 393(1) Sl. 6(i) codes 1023/1024 on conversion-service streams or Section 194Q on goods-sale streams. Track first-pass cure yield per mould per part as quality-cost signal.
- **Config:** Compound master per part with ingredient list and per-ingredient index reference; natural rubber RSS-4 Kottayam monthly average calendar; synthetic polymer index master per family; carbon black grade master with feedstock index; processing oil master with crude index; mould master with cycle-counter and expected cycle life; per-part first-pass cure yield norm; conversion-versus-goods-sale flag per OEM contract with payment-code map (Section 393(1) Sl. 6(i) codes 1023/1024 versus Section 194Q).
- **Output:** A monthly rubber-component reconciliation statement closing compound-to-cured-part identity per shift per mould; per-ingredient RMPV claim ledger with Kottayam RSS-4 reference and synthetic-polymer index lineage; first-pass cure yield dashboard with drift alerts; mould-amortisation register under Ind AS 16; TDS payment-code register split between Section 393(1) Sl. 6(i) codes 1023/1024 and Section 194Q with quarterly Form 26Q export; and an audit-ready ingredient-traceable batch log that ties to compound mixing records and physical stock.

### Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults

Source: https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india/

- **Problem:** Buyer loses ITC when supplier hasn't been paid within 180 days (Rule 37) or hasn't filed GSTR-3B by September 30 (Rule 37A). 18% interest applies on utilized ITC.
- **Logic:** Monitor payment aging per supplier invoice for Rule 37 (180-day trigger) and supplier GSTR-3B filing status for Rule 37A (September 30 trigger). Re-availment tracked separately — not subject to Section 16(4) time bar.
- **Config:** Rule 37: 180-day window from invoice date, proportionate reversal, 18% interest under Section 50. Rule 37A: reversal by November 30, re-availment when supplier files.
- **Output:** Automated reversal alerts at 150-day mark, GSTR-3B reversal entries, re-availment tracker when payment made or supplier files, and interest liability calculation.

### Rule 37 ITC Reversal Risk on OEM Unpaid Invoices: What Auto-Component CFOs Must Know

Source: https://www.terra-insight.com/insights/rule-37-itc-reversal-oem-receivables-auto-india/

- **Problem:** Indian Tier-1 and Tier-2 auto-component suppliers face Rule 37 of the CGST Rules requiring 100% reversal of Input Tax Credit, plus 18% per annum interest under Section 50, on the proportionate unpaid value of supplier invoices that cross 180 days from invoice date. The cascading short-pay from OEM down to Tier-1 to Tier-2 means that unpaid invoice residuals build up systematically, the 180-day clock runs silently in the background, and the reversal lands as an audit surprise unless every payable is aged in 60 / 90 / 150 / 180-day buckets with a reconciliation engine surfacing the day-150 prep entries and the day-180 final reversals automatically.
- **Logic:** Maintain a vendor-invoice ledger keyed by invoice date, taxable value, IGST/CGST/SGST split, payments-against-invoice history, and ageing-as-of-today computation. Run the daily age engine: for every invoice where unpaid amount > 0 and age > 180 days, compute the unpaid-proportion factor, multiply by the original ITC amount on that invoice, and surface a GSTR-3B Table 4(B)(2) reversal candidate. Stamp each candidate with the date credit was originally availed so Section 50 interest can be computed from availment-date to reversal-date. On any subsequent payment to the supplier, restore the proportionate credit via Table 4(A)(5) of the same period's GSTR-3B.
- **Config:** Vendor master keyed by GSTIN, invoice ledger with date / taxable value / GST split / payment history, ageing buckets at 60 / 90 / 150 / 180 days with band-specific action triggers, Section 50 interest calendar keyed by date of original credit availment, Rule 37 reversal queue feeding GSTR-3B Table 4(B)(2), credit re-availment queue feeding GSTR-3B Table 4(A)(5) on payment confirmation, Section 17(5) gating classifier so blocked credits skip the Rule 37 workflow.
- **Output:** A daily Rule 37 ageing dashboard by vendor and invoice, a 30-day forward-look queue of invoices approaching day 180, a GSTR-3B Table 4(B)(2) auto-prep file for the current return period with computed reversal amounts and Section 50 interest, a credit re-availment register for invoices paid post-reversal, and an audit-defensible trail of every reversal-and-restore cycle keyed to the cash-payment record.

### Rule 55 Delivery Challan for Auto Components: FI Material, KLT Bins, Job Work Movement

Source: https://www.terra-insight.com/insights/rule-55-delivery-challan-auto-component-fi-bins-job-work/

- **Problem:** An auto-component Tier-1 generates dozens of distinct goods movements every day that are not tax-invoice supplies — free-issue steel coil arriving from the OEM or nominated mill against a return obligation, returnable KLT bins and metal stillages going out with finished-part despatches and coming back empty, and job-work despatches under Section 143 to platers, heat-treaters, machinists, painters and phosphaters — each requiring a Rule 55 delivery challan in a FY-unique series, each surfaced through the e-way bill regime above ₹50,000 consignment value, each subject to its own statutory return clock, and each carrying a deemed-supply trigger (FI non-return, KLT non-return, Section 143 one-year/three-year lapse) that converts the movement retrospectively into a taxable supply with GST plus 18% interest exposure if the registry is not watertight.
- **Logic:** Issue one Rule 55 delivery challan per non-supply goods movement in a FY-unique series; classify the movement at issue as FI inward, KLT outward, KLT inward, job-work outward, job-work inter-hop, or job-work inward; tie each challan to its return clock (FI per contract, KLT per float-aging window, Section 143 one-year inputs / three-year capital goods); cross-link the dispatched challan to its eventual return GRN or supply event; surface the open-balance position per counterparty per challan; alert 60 and 30 days before any deemed-supply trigger; flag URP consignees and unregistered transporters; generate e-way bill on the challan basis above ₹50,000; cross-reconcile the job-work bucket to ITC-04 and the FI bucket to the OEM FI ledger before each statutory cut-off.
- **Config:** Challan series per plant GSTIN and per movement type; counterparty master (OEM, nominated mill, job-worker, transporter) with GSTIN/URP flag and return-clock policy; FI material register linked to the OEM FI ledger; KLT bin master with float-aging band; Section 143 challan tracker with one-year / three-year clocks per input vs capital classification; e-way bill rule per consignment value; alert thresholds 60 and 30 days; deemed-supply provisional accrual policy for finance.
- **Output:** A running Rule 55 challan register cross-tied to each return event; an open-balance position per FI lot, KLT bin float and Section 143 challan with days-to-deemed-supply countdown; the ITC-04 pre-filing pack for the job-work bucket; the OEM FI reconciliation pack; the bin-float aging position; and a board-visible deemed-supply risk register listing every open challan within 60 days of its statutory window.

### Rule 55 Delivery Challan Reconciliation for Textile Job-Work

Source: https://www.terra-insight.com/insights/rule-55-delivery-challan-textile-job-work/

- **Problem:** Indian textile mills routinely send greige fabric to external washers, dyers, printers, and finishers under Rule 55 delivery challans — sometimes 300 to 800 challans a month per branch — and every outbound challan starts a Section 143 clock that expires at 365 days for inputs or three years for capital goods. The outbound challan register, the return-inward challan register, the quarterly ITC-04 filing, and the GSTR-1 non-taxable movement must line up per challan across the entire cycle, but the four data sources sit in different systems — the mill's ERP outbound module, a job-worker's manual return-inward book, the GST portal ITC-04 draft, and the GSTR-1 filing pack — and no native cross-foot exists. A single missed return-inward challan can silently retro-supply a whole consignment months after the fact, triggering interest under Section 50 from the original outbound date and a Section 122 penalty risk on the sequence integrity.
- **Logic:** Build a per-challan register keyed by outbound challan number that carries: outbound challan date, consignee (job-worker) GSTIN and name, HSN and description, quantity dispatched, taxable value, LR and vehicle number, expected return date under Section 143 (outbound date plus 365 days for inputs or plus three years for capital goods), and status flag (open, returned, deemed-supplied). On every return-inward event, match the return challan to the outbound line by challan reference, close the outbound line, and record any quantity variance for wastage reconciliation. Before every ITC-04 filing cycle, cross-foot the register against the ITC-04 draft Tables 4, 5A, and 5B — any outbound challan without a corresponding ITC-04 outbound line or any return-inward without an ITC-04 inward line is a filing gap. Run an ageing report on the open universe keyed to the Section 143 clock — anything crossing day 300 gets a jobsite follow-up, and anything at day 360 gets a deemed-supply provision so the mill's month-end books carry the correct liability.
- **Config:** Rule 55 challan master with per-branch serial sequence (unique per financial year per place of business, sixteen-character limit, chronological order enforced); job-worker master with GSTIN, PAN, address, capacity category (dyeing / printing / washing / stitching / embroidery), and Section 143 tenure flag (inputs = 365 days, capital goods = 3 years); outbound challan register from ERP with challan number, date, consignee GSTIN, HSN, quantity, LR / vehicle; return-inward register from ERP or job-worker portal with return challan number, date, reference to outbound challan, quantity received, quantity wastage; ITC-04 draft feed from the GST portal per filing cycle; GSTR-1 outward register per tax period; ageing bucket configuration (0-90 / 91-180 / 181-300 / 301-365 / 365+ days from outbound); deemed-supply provision rule for the 365-plus bucket.
- **Output:** A cycle-end reconciliation pack: opening open-challan universe, period outbound challans issued, period return-inward challans received, period challans deemed-supplied, period wastage variances, closing open universe — reconciled to the ITC-04 filing and the GSTR-1 non-taxable-movement working. Per-job-worker ageing buckets surface stuck consignments with LR references, expected return dates, and the Section 143 clock reading. The 365-plus bucket feeds a deemed-supply provision in the month-end books, and the sequence-integrity check confirms no gaps or back-dating in the per-branch challan series before the GSTR-1 and ITC-04 filings are submitted.

### Rule 89(5) 2-Year Time Limit for Textile Refund Claim Reconciliation

Source: https://www.terra-insight.com/insights/rule-89-5-2-year-time-limit-textile-refund-claim/

- **Problem:** A textile principal running a persistent inverted-duty accumulation across a financial year faces two independent risks. First, the accumulated Rule 89(5) entitlement is a working-capital-heavy asset that only converts to cash on filing Form GST RFD-01. Second, the entitlement is time-barred by the Section 54(1) 2-year window from the relevant date defined in Explanation 2(e), meaning an un-filed FY balance permanently forfeits the cash refund at the end of the 24-month window. Without a monthly refund pipeline reconciled against a 2-year clock per FY and a D-90 escalation trigger, tier-2 principals routinely discover time-barred exposure only at year-end audit — by which point the remedy is a P&L write-off, not a refund file.
- **Logic:** Build a per-FY inverted-duty accumulation ledger that ingests the electronic credit ledger, the outward supply pattern (turnover of inverted-rated supply and adjusted total turnover), and the tax payable on inverted-rated supply, and computes the Rule 89(5) maximum refund per month post-Notification 14/2022 (Net ITC excludes input services and capital goods). Anchor a 2-year clock per FY at 31 March of the accumulation FY. Track the cumulative refund pipeline in three states: filed and acknowledged (RFD-02), sanctioned (RFD-06), and rejected or deficiency-memo (RFD-08 or RFD-03 needing re-file). Compute un-filed FY balance = accumulation entitlement − cumulative filed. Escalate at D-90 before the FY 2-year expiry if any un-filed balance exists. Write-off log records any balance that crosses expiry unfiled.
- **Config:** FY-anchored accumulation register with monthly turnover of inverted-rated supply, Net ITC (post Notification 14/2022, excluding input services and capital goods), adjusted total turnover, and tax payable on inverted-rated supply; Section 54(1) 2-year clock configuration with FY-end anchor date (31 March of accumulation FY) and expiry-plus-24-months compute; RFD-01 filing status feed (RFD-02 acknowledgement, RFD-03 deficiency memo, RFD-06 sanction, RFD-08 rejection); escalation threshold at D-90 before expiry to CFO and tax lead; permanent write-off log for time-barred balances; audit committee disclosure feed for any material write-off in the reporting period.
- **Output:** A month-end textile refund pipeline pack: opening un-filed FY balance by accumulation FY, additions in the period (RFD-01 filed), reductions in the period (RFD-06 sanctioned, RFD-08 rejected, RFD-03 re-file required), closing un-filed balance by FY, and days-to-expiry per FY. FY balances within D-90 of expiry are surfaced in a dedicated escalation section with the responsible tax lead named and the required action (file RFD-01 or resolve deficiency memo). Any FY balance that crossed expiry in the period is booked to the permanent write-off log with the amount, the accumulation FY, the relevant date used for the 2-year computation, and the reason for non-filing — providing the audit committee an unambiguous view of every time-barred forfeiture.

### Rule 89(5) Inverted-Duty Refund Reconciliation for Textile India

Source: https://www.terra-insight.com/insights/rule-89-5-inverted-duty-refund-textile-india/

- **Problem:** An integrated Indian textile mill runs a permanent inversion. Yarn output is taxed at 5%, fabric output at 12%, but dyes, sizing chemicals, packaging, spares, and consumables arrive at 18%. Every month the electronic credit ledger accumulates more ITC than can be discharged against output tax, and unless the mill claims a Rule 89(5) refund monthly, the balance sits idle while the two-year time-limit from the relevant end-of-month date silently consumes the eligible window. Add the July 2022 amendments — Net ITC excludes input services and capital goods per Notification 14/2022, and Notification 09/2022 restricts the refund on specified woven cotton and synthetic filament fabrics — and the reconciliation surface splits into a monthly Net ITC ledger, an inverted-rated turnover ledger with HSN restriction flags, an adjusted total turnover computation, and a running two-year forfeiture watchlist. The gap between what the mill could legitimately claim and what actually lands in the bank account routinely runs to 15 to 35 percent of the theoretical maximum.
- **Logic:** Build a monthly Net ITC ledger by parsing GSTR-2B into three streams — inputs, input services, capital goods — using HSN and supplier-line classification. Only the inputs stream is eligible under Notification 14/2022. Build a parallel outward supply ledger from GSTR-1: inverted-rated supply (yarn 5%, non-restricted fabric 12%), other taxable supply, zero-rated and exempt supply. Apply the Notification 09/2022 restriction flag to remove restricted HSN turnover from the inverted-rated numerator. Compute Rule 89(5): Max Refund = (Inverted-rated turnover × Net ITC ÷ Adjusted total turnover) − Tax payable on inverted-rated supply. Maintain a two-year time-limit register tagging each month's claim with its filing deadline; alert on any month within 90 days of expiry. Reconcile the cumulative refunds claimed against the electronic credit ledger drawdown and the refund credited to the bank account, so that shortfalls, deficiency memos, and rejected line items surface in the same view.
- **Config:** Chart-of-accounts mapping linking every GSTR-2B inward supply HSN to one of three ITC streams (inputs, input services, capital goods); an outward HSN master flagging inverted-rated supply, restricted-refund goods per Notification 09/2022, and zero-rated supply; a Rule 89(5) formula engine with configurable rounding; a two-year time-limit register keyed by claim month with the relevant date derived from Section 54 and Circular 125/44/2019; a Statement 1A generator producing invoice-level backup for RFD-01; a cross-foot check to the electronic credit ledger and to the bank credit; a workflow for deficiency memos (RFD-03) and rejected line resubmissions.
- **Output:** A monthly RFD-01 reconciliation pack: Net ITC (inputs only), inverted-rated turnover after HSN restriction, adjusted total turnover, tax payable on inverted-rated supply, computed Rule 89(5) maximum refund, and the amount actually claimed on RFD-01. Statement 1A produced with invoice-level backup. A rolling two-year forfeiture watchlist showing every unfiled or partially filed month with days-to-expiry. A cumulative reconciliation from opening ITC ledger balance through period availment, period utilisation, period refund claimed, and period refund credited to bank — surfacing gaps for auditor review before month-end close.

### RuPay Credit-Card-on-UPI: The 2% Surcharge Hidden Inside "UPI"

Source: https://www.terra-insight.com/insights/rupay-credit-card-on-upi-2-percent-surcharge-india/

- **Problem:** Indian OTT, SaaS, D2C and other subscription merchants frequently treat the gateway settlement file's single "UPI" line as the zero-MDR rail mandated in January 2020. That assumption silently absorbs RuPay-credit-card-on-UPI volume which carries approximately 2% interchange above a ₹2,000 ticket — split roughly 1.5% to the issuing bank and 0.5% to the network and acquirer — under NPCI's October 2022 enablement. The customer pays nothing extra. The merchant pays the full cost. Without per-sub-instrument splitting at the gateway feed mapping stage, the leakage compounds every billing cycle and shows up as unexplained variance between contracted UPI economics and actual settlement net.
- **Logic:** Pull settlement files at the lowest available sub-instrument granularity from every payment aggregator. Map UPI to two distinct sub-buckets: bank-account UPI (expected MDR 0%) and RuPay-credit-on-UPI (expected interchange 0% at or below ₹2,000, ~2% above ₹2,000). Compute effective rate by sub-instrument as fee divided by gross. Flag any non-zero MDR on the bank-account UPI bucket and any UPI line where the effective rate is consistent with a card-grade interchange. For above-₹2,000 RuPay-credit-on-UPI tickets, compute expected cost as gross × 2% and compare to actual fee column; surface deviation. Reconcile GST 18% as a separate line on the fee only.
- **Config:** MDR rule set per gateway and per sub-instrument with explicit RuPay-credit-on-UPI carve-out from the generic UPI bucket. Ticket-size threshold of ₹2,000 carried as a rule parameter for tier switching from 0% to ~2%. BIN-or-instrument-code mapping table that resolves the gateway feed's sub-instrument tag to (a) bank-account UPI, (b) RuPay credit on UPI, (c) PPI/wallet on UPI. GST-on-MDR retention flag enforcing 18% on fee only, never on transaction value. Reconciliation variance threshold at the sub-instrument level so a single "UPI" bucket cannot conceal mixed-MDR volume.
- **Output:** A monthly per-sub-instrument settlement report distinguishing zero-MDR bank-account UPI from chargeable RuPay-credit-on-UPI, with effective-rate, expected-cost, actual-cost and variance columns. A drill-down register of every above-₹2,000 RuPay-credit-on-UPI transaction with computed expected interchange. A GST-on-MDR audit trail with input-tax-credit alignment to the aggregator's monthly tax invoice. A reconciliation discipline note for the finance controller showing what percentage of the "UPI" line was actually zero-MDR and what percentage carried interchange — the basis for renegotiation and for accurate contribution-margin reporting.

### Rule 89(5) for Pharma Formulations: The Complete Refund Playbook

Source: https://www.terra-insight.com/insights/rule-89-5-inverted-duty-refund-pharma-formulations-complete-guide/

- **Problem:** A Tier-1 integrated pharma formulator running formulation plants at Ahmedabad in Gujarat, Baddi in Himachal Pradesh and Sikkim, with an aggregate FY 2026-27 domestic Chapter 30 turnover of the order of Rs 8,500 crore, must file a separate Form GST RFD-01 per state GSTIN monthly against accumulated inverted-duty ITC. The 22 September 2025 rate reset moved all Chapter 30 formulations to 5 percent output while packaging remained at 18 percent Chapter 39 and Chapter 48, solvents at 18 percent Chapter 27, active pharmaceutical ingredients at 5 percent Chapter 29, and excipients at 5 to 12 percent — locking structural credit into the electronic credit ledger every tax period. Each plant's monthly refund quantum, illustratively of the order of Rs 42 to 58 crore depending on the API-to-solvent input mix, must be defensible in the Notification 14/2022 amended Rule 89(5) formula, must correctly exclude input services and capital goods from Net ITC, must carve out the Notification 09/2022 Chapter 27 solvent proportion disclosure, and must reconcile the plant's GSTR-1 output register and GSTR-2B input register at invoice level.
- **Logic:** Build a per-plant per-tax-period refund workbook keyed on the plant's state GSTIN. Extract the Chapter 30 5 percent outward supply from GSTR-1 into the Turnover of inverted-rated supply base. Extract the Chapter 29 API, Chapter 39 and 48 packaging, Chapter 27 solvent, and excipient ITC from GSTR-2B into the Net ITC pool — decomposed by HSN chapter so the composition is transparent. Separately identify and hold aside the input-services ITC (freight, external analytical laboratory, plant maintenance, engineering consulting) and the capital-goods ITC (reactors, granulators, compression machines, packaging lines) — these do not feed the Net ITC numerator but do sit in the electronic credit ledger as ordinary ITC. Apply the Notification 14/2022 amended Rule 89(5) formula. Prepare the Statement 1A invoice-level annexure. Attach a Chapter 27 solvent proportion disclosure showing the solvent leg of Net ITC. File Form GST RFD-01 monthly. Track the RFD-04 provisional refund receipt and the RFD-06 final sanction against a treasury projection.
- **Config:** Plant master with GSTIN, state, HSN Chapter 30 sub-category assignment (3003 bulk drug, 3004 finished dosage form), and expected monthly outward supply volume; input HSN register with per-vendor per-invoice HSN classification anchored to Chapter 29 (2941 antibiotics as APIs, other Chapter 29 organic chemicals), Chapter 27 (industrial solvents — hexane, isopropyl alcohol, methanol, toluene, methyl ethyl ketone), Chapter 39 (polymer films, HDPE bottles, blister foils), Chapter 48 (cartons, leaflets), and excipient chapters 11, 17, 38, 3505; Net ITC composition register per HSN chapter per tax period; input-services ledger and capital-goods ledger held separate; Rule 89(5) refund workbook per plant per tax period with the amended-formula computation; Statement 1A invoice-level annexure builder; Chapter 27 solvent carve-out disclosure line; Form GST RFD-01 electronic filing feed; treasury projection against RFD-04 provisional and RFD-06 final sanction timing; two-year filing-window monitor from the relevant date under Section 54.
- **Output:** A month-end multi-plant Rule 89(5) refund pack: per-plant per-GSTIN Turnover of inverted-rated supply, Adjusted Total Turnover, Net ITC decomposed by input HSN chapter with the Chapter 27 solvent proportion disclosed as a distinct line, input-services and capital-goods ITC identified and excluded from the numerator, the amended-formula maximum refund computation, the Statement 1A invoice-level annexure, and the Form GST RFD-01 draft ready for portal submission. A rolling treasury projection maps each filed RFD-01 to its expected RFD-04 provisional receipt (within seven days) and RFD-06 final sanction (post-scrutiny) so the finance team can size the working-capital gap between accrued refund and cash receipt. At year-end the pack reconciles the aggregate claimed refund per GSTIN to the aggregate sanctioned refund and surfaces the deficiency-memo (Form GST RFD-03) rejection reasons for the following-year workbook refinement.

### RuPay Debit MDR Reconciliation for Indian Merchants: Zero-MDR Audit Path

Source: https://www.terra-insight.com/insights/rupay-debit-mdr-reconciliation-india/

- **Problem:** RuPay debit P2M MDR has been zero by mandate since 1 January 2020, but two leakage modes persist. The first is direct billing error, where a non-zero MDR is deducted on a RuPay debit transaction in the settlement file. The second is routing error, where a RuPay-issued debit card is co-badged through Visa or Mastercard at cap-bound MDR instead of through the RuPay rail at zero. Default gateway dashboards rarely break out debit MDR by network, leaving both modes invisible without per-transaction reconciliation.
- **Logic:** Reconciliation classifies each debit transaction by network using the BIN (first six digits of the card number), recomputes expected MDR as zero for RuPay debit and as the contracted rate (capped at 0.40% or 0.90% subject to per-transaction Rs 200 / Rs 1,000 caps) for Visa and Mastercard debit, and compares to the actual MDR deducted. Any non-zero MDR on a RuPay debit transaction is flagged as a recoverable billing error. The Visa and Mastercard volume is further sliced against a RuPay-eligible BIN list to quantify the routing-shift opportunity from steering co-badged cards through the RuPay rail.
- **Config:** BIN-to-network classifier (RuPay vs Visa vs Mastercard vs co-badged), zero-MDR enforcement rule for RuPay debit, RBI cap enforcement (0.40% / 0.90% with per-transaction caps of Rs 200 / Rs 1,000) for non-RuPay debit, monthly per-network effective-rate report, quarterly RuPay-eligible BIN audit against acquirer routing policy.
- **Output:** Per-transaction exception list of non-zero MDR billed on RuPay debit transactions (recoverable from the gateway), per-network effective-rate dashboard for the finance team, BIN-mix routing report quantifying the rupee opportunity from shifting co-badged volume to RuPay, and a clean debit-MDR line in the monthly expense book separated from gateway platform fee and GST.

### SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching

Source: https://www.terra-insight.com/insights/saas-subscription-reconciliation-india/

- **Problem:** SaaS companies collect annual subscriptions upfront but must recognize revenue monthly under Ind AS 115, creating a deferred revenue liability that diverges from cash receipts over the subscription lifecycle.
- **Logic:** Match cash receipt to subscription contract, generate monthly revenue recognition schedule, reconcile deferred revenue balance against P&L recognized revenue and bank collections.
- **Config:** Ind AS 115 five-step model, GST 18% on SaaS (SAC 998314), LUT for export services, FIRC for USD collections, monthly recognition schedule.
- **Output:** Deferred revenue aging report, MRR-to-cash reconciliation, Ind AS 115 disclosure schedule, and GST output liability register.

### RuPay Debit vs Visa/Mastercard Debit MDR: Why Network Choice Drives Merchant Cost

Source: https://www.terra-insight.com/insights/rupay-debit-vs-visa-mastercard-debit-mdr-india/

- **Problem:** Debit MDR in India is split along network lines: RuPay is zero by mandate, Visa and Mastercard remain under the 2017 RBI cap. Merchants whose debit volume skews toward Visa and Mastercard pay full cap-bound MDR on every transaction that could have been routed through RuPay at zero cost, and many gateways do not surface this network mix in their default reporting.
- **Logic:** Reconciliation classifies each debit transaction by network (BIN-derived), recomputes expected MDR as zero for RuPay and as the contracted rate (capped at 0.40% or 0.90%) for Visa and Mastercard, and compares to actual MDR deducted. Any non-zero MDR on RuPay debit is flagged as a billing error. Per-network effective-rate analysis quantifies how much of the Visa and Mastercard volume is on RuPay-eligible BINs that could have been steered through the RuPay rail.
- **Config:** Network-mapped MDR rule set per gateway, BIN-tier classifier (RuPay vs Visa/Mastercard vs co-badged), zero-MDR check for RuPay debit, RBI cap enforcement (0.40% / 0.90% with Rs 200 / Rs 1,000 per-transaction caps) for non-RuPay debit, monthly per-network effective-rate report.
- **Output:** Per-transaction MDR variance report with recoverable over-charges on RuPay debit, per-network effective-rate dashboard, BIN-mix optimisation report quantifying potential savings from steering RuPay-eligible cards through RuPay rails, and a clean fee-line reconciliation feeding the monthly expense book.

### SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose

Source: https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india/

- **Problem:** Indian CTOs and CFOs default to on-premise reconciliation deployments assuming that RBI localisation, SEBI cloud framework, and DPDP Act 2023 forbid SaaS — but this assumption costs 2–4x TCO over three years for most NBFCs, manufacturers, and IT services firms where AWS Mumbai SaaS is fully compliant.
- **Logic:** Match deployment model to regulatory class: scheduled banks, insurance companies, and PSUs under sovereignty mandates require on-premise or dedicated private cloud; all other Indian enterprises are cleared for SaaS hosted in AWS ap-south-1 subject to ISO 27001:2022 and DPDP Act documentation. Evaluate TCO across hardware, IT staff, patching, DR, and scaling cost against subscription fees over a 3-year horizon.
- **Config:** Deployment decision matrix keyed on entity type (NBFC, bank, insurer, PSU, mid-market private, listed private), data residency requirement (ap-south-1 sufficient vs. a genuine on-premise mandate), and VPC tenancy (shared SaaS or dedicated VPC). Vendor produces region configuration evidence, ISO 27001:2022 scope letter, and DPDP Act compliance note for each scenario.
- **Output:** A documented deployment choice defensible to the board, audit committee, and regulator, with a 2–4 week go-live for SaaS or a phased infrastructure-plus-application rollout for a genuine on-premise mandate, and a 3-year TCO model showing the cost difference quantified.

### Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams

Source: https://www.terra-insight.com/insights/sage-reconciliation-india/

- **Problem:** Sage X3 and Sage 300 run meaningful Indian mid-market manufacturing and distribution footprints (often in foreign-subsidiary entities on a global Sage stack) but ship with lighter India localisation than SAP or Oracle — pushing TDS Form 26AS matching, GSTR-2B reconciliation, and platform settlement entirely to an external layer, while CARO 2020 still mandates a voucher-level audit trail.
- **Logic:** Bolt an external reconciliation layer via Sage X3 Syracuse web services (REST/SOAP) or Sage 300 Web API, with scheduled CSV/XML exports from the X3 batch server or Sage 300 Macros as the bulk data path. Ingest GSTR-2B, Form 26AS, bank MT940, and payment gateway files externally, run multi-pass matching with variance classification, and write cleared-status and variance codes back via REST API without bypassing Sage's Audit Log or Transaction History.
- **Config:** Sage X3 or Sage 300 connector using Syracuse web services or Sage 300 Web API, scheduled batch export to SFTP, Audit Log enabled for CARO 2020 compliance, GSTR-2B JSON ingestion, Form 26AS parser, and writeback jobs that preserve voucher-level edit log per Companies (Accounts) Rules April 2023.
- **Output:** A reconciled Sage X3 or Sage 300 ledger with external statutory and settlement matching applied, CARO 2020 voucher-level audit trail intact, and cleared-status plus variance classification visible in Sage for partner and statutory auditor review.

### Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment

Source: https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india/

- **Problem:** A single bulk salary NEFT for 400 employees appears as one bank debit but must align with a 400-row payroll register containing gross pay, Section 192 TDS, PF (12% employee plus 3.67% EPF plus 8.33% EPS plus EDLI plus admin), ESI (3.25% plus 0.75%), and professional tax. TDS, PF, and ESI generate three separate challan debits on three different portals with three different deadlines.
- **Logic:** Four-way reconciliation matches (1) bulk salary NEFT debit to the sum of employee net pay using the bank bulk-payment acknowledgement file with per-employee UTR; (2) Section 192 TDS debit to Challan ITNS 281 CIN (BSR code plus date plus serial) on TRACES by the 7th; (3) PF debit to EPFO ECR portal TRRN by the 15th; (4) ESI debit to ESIC portal challan by the 15th. Off-cycle arrear payments are tagged with a distinct reference code.
- **Config:** Bulk-payment acknowledgement file ingestion, Challan ITNS 281 CIN tracker, EPFO TRRN tracker, ESIC employer-registration-number tracker, and off-cycle payment tagging.
- **Output:** Employee-level matched net pay ledger, Section 192 TDS credit aligned to Form 26AS via BSR CIN, reconciled PF contribution against EPFO ECR, reconciled ESI contribution against ESIC challan, and off-cycle arrear audit trail.

### SAP ABAP Custom Reports Indian Auto-Component Tier-1s Actually Build

Source: https://www.terra-insight.com/insights/sap-abap-custom-reports-auto-component-reconciliation/

- **Problem:** Indian auto-component Tier-1 manufacturers on SAP S/4HANA all end up building the same 8-12 custom ABAP Z-reports because standard SAP does not run the auto-component reconciliation streams as standing exception processes. The Z-report family forks per OEM customer over time, the maintenance burden compounds to ₹50-80 lakh per year at a 4-OEM Tier-1, and the rebuild-backlog estimates exceed the original build effort by year 3-4. The result is a no-end-state custom-ABAP run-rate that drives the build-vs-buy reconsideration at OEM customer number three.
- **Logic:** Enumerate the recurring Z-report list (CUM drift, ASN ageing, OEM debit-note decomposition, RMPV claim, ITC-04 generation, free-issue reconciliation, tonnage-rate billing, Section 393 / 394 deduction split), document the source SAP tables and IDoc message types each Z-report consumes, quantify the build effort and the ongoing per-Z-report maintenance burden, identify the OEM-customer-count threshold at which the custom-ABAP economics break, and frame the companion-product alternative that consumes SAP standard extracts and runs the standing-exception streams externally.
- **Config:** SAP S/4HANA install with auto-component-specific MM and SD configuration, Z-namespace ABAP development for ZSAR_CUM_DRIFT, ZSAR_ASN_AGEING, ZSAR_DEBIT_NOTE_DECOMP (typically forked per OEM by year 2), ZSAR_RMPV_CLAIM, ZSAR_ITC04_GEN, ZSAR_FREE_ISSUE_RECON, ZSAR_TONNAGE_BILL, ZSAR_TDS_SECTION_393, source-table catalogue (EKKO / EKPO / EKES / EKBE for procurement, VBAK / VBAP / LIKP / LIPS / VBRK / VBRP for sales, MARM / MARC / MCHB for material and batch, J_1IG and J_1IS family for India localisation, WITH_ITEM for withholding tax), IDoc message-type registry, scheduled job framework for nightly Z-report execution.
- **Output:** A custom-ABAP Z-report inventory typically counting 8-12 reports at a mid-Tier-1, annual maintenance run-rate of ₹50-80 lakh fully-loaded, forking pattern per OEM customer that compounds maintenance burden non-linearly, and a build-vs-buy boundary at OEM customer number three beyond which a unified reconciliation companion product replaces the Z-report family with substantially lower run-rate and faster cycle time.

### SAP Companion Products for Auto-Component Reconciliation: Why Native SAP Falls Short

Source: https://www.terra-insight.com/insights/sap-companion-product-positioning-auto-india/

- **Problem:** Indian auto-component Tier-1 manufacturers on SAP S/4HANA discover that the auto-component reconciliation streams (CUM drift, OEM debit decomposition, RMPV claim, ITC-04 multi-hop, free-issue Rule 55, Section 143 alerting, OEM portal extracts) are not transactional postings — they are cross-system, cross-time, cross-currency reconciliation processes that the SAP transactional architecture was not designed for. Solving them through SAP customisation creates the ZSAR_* Z-report family, which forks per OEM customer and compounds to ₹50-80 lakh annual maintenance run-rate at a 4-OEM Tier-1 with no end-state.
- **Logic:** Treat SAP as the transactional system of record, run the standing-exception reconciliation streams externally through a companion product connected via standard SAP extract interfaces (IDoc DELFOR01 / DESADV01 / INVOIC02, OData on NetWeaver Gateway, scheduled standard report exports), keep all custom code outside SAP's core, surface exceptions through the companion's dashboards, and optionally write back exception state to SAP user-defined fields. Decommission the Z-report family in tranches as the companion takes over each stream.
- **Config:** SAP S/4HANA install with standard MM, SD, FI, CO modules and India Localisation enabled, ALE / EDI subsystem with partner profiles for OEM-facing IDoc exchange, OData services on NetWeaver Gateway exposed for scheduling agreement / GRN / invoice register / withholding tax register queries, scheduled standard report exports nightly to SFTP, companion reconciliation product on AWS Mumbai with auto-component industry preset, daily extract consumption from SAP and from OEM portal exports, reconciliation streams running externally, optional write-back of exception state to SAP user-defined fields, Income Tax Act 2025 payment codes 1001-1092 configured in SAP withholding tax and overlaid in the companion's tax overlay.
- **Output:** An SAP-companion reconciliation architecture: SAP retains transactional system-of-record status with no custom code added beyond what already exists, the companion runs the seven standing-exception streams (four-clock three-way match, CUM drift, debit decomposition, RMPV claim, ITC-04 multi-hop, free-issue Rule 55, OEM portal extracts) as continuous exception management with ageing, root-cause classification and resolution workflow, the ZSAR_* Z-report family decommissioned in tranches over 12 months, ABAP team redirected to core SAP roadmap, total cost of ownership materially lower than the build path beyond OEM customer number three.

### SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short

Source: https://www.terra-insight.com/insights/sap-fi-reconciliation-india/

- **Problem:** SAP S/4HANA and ECC's India localisation handles TDS posting (J1INCHLN, J1INMIS) and GST tax determination but does not connect to TRACES for Form 26AS matching, does not pull GSTR-2B JSON from the GST portal, and does not disaggregate NACH batch credits from NPCI XML — leaving Indian SAP customers to reconcile outside the system in spreadsheets.
- **Logic:** Bolt a reconciliation layer on top of SAP FI via one of three integration patterns: scheduled SFTP file export from background jobs in SM36, RFC-enabled BAPI calls (BAPI_GL_ACC_GETBALANCE plus custom Z-BAPIs), or IDoc (FINSTA or custom reconciliation IDocs). Ingest Form 26AS, GSTR-2B, NACH NPCI files, and bank MT940 externally, run multi-pass matching with tolerance bands, and post cleared items back to SAP via BAPI.
- **Config:** SAP connector configured per client with background job in SM36 for scheduled export, Z-BAPI templates for TDS and GST open-item pulls, FINSTA IDoc schema for writeback, field mappings from WITH_ITEM, BSIK/BSIS, J_1IEWTNO, and J_1IG* tables, and multi-entity routing for company codes.
- **Output:** A reconciled SAP FI ledger with Form 26AS, GSTR-2B, NACH, and bank variances all matched externally and cleared back to SAP — TDS receivable, ITC, and bank GL balances reliable at month-end, with an audit trail surviving SAP sign-off and statutory audit.

### SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps

Source: https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india/

- **Problem:** Indian manufacturers running SAP MM-FI rely on the GR/IR clearing account to close three-way match, but SAP standard does not catch India-specific gaps — GST inclusive/exclusive variance between PO and invoice, TDS posting timing mismatches under Section 393, J1IGN stock-issue transactions outside MIGO, OBYC GR/IR account misassignment by valuation class, cross-GSTIN consolidation when one company code spans multiple plant GSTINs, and the post-cutover remapping from legacy 194-series WHT codes to Section 393 codes 1001-1092.
- **Logic:** Treat SAP standard 3-way match as the rate-and-quantity backbone (GR/IR clearing closes to zero on clean matches) and layer an India-specific reconciliation rule set on top: (a) compare PO tax code to invoice tax code at MIRO and flag mismatches; (b) verify TDS WHT type and Section 393 code alignment per vendor; (c) consolidate cross-GSTIN at company-code level by plant GSTIN; (d) flag Section 17(5) blocked-credit material types at MIRO; (e) cross-era map legacy 194-series codes to new 393-series codes for pre-1-April-2026 transactions still being reconciled.
- **Config:** SAP TAXINN tax procedure with India GST condition records, OBWO withholding tax types per Section 393 payment code (1001-1092), OBYC GR/IR account determination per valuation class, plant master with GSTIN mapping, vendor master with PAN/GSTIN/MSME flag, J1IGN configuration for stock issues, e-invoice integration for IRN capture, and the India-localised reconciliation rule set on top of MIRO.
- **Output:** A daily SAP MM-FI close where GR/IR clearing balances to zero on matched invoices, India-specific exceptions (GST mismatch, TDS code error, Section 17(5) flag, cross-GSTIN drift, J1IGN open challan) surface in a separate exception queue with variance codes mapped to SAP-standard transactions, and cross-era 194-to-393 mapping handles the FY 2025-26 to FY 2026-27 cutover without losing audit traceability.

### SAP Scheduling Agreement Reconciliation for Auto Component Suppliers: What SAP Doesn't Do

Source: https://www.terra-insight.com/insights/sap-scheduling-agreement-reconciliation-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers on SAP S/4HANA discover within 18 months of go-live that SAP handles scheduling-agreement document mechanics, EDI 830/862/856 transmission, delivery creation, GRN, AR/AP, and three-way match brilliantly — but does not handle CUM drift as a standing reconciliation exception, RMPV index recomputation, Section 143 deemed-supply alerting, tooling amortisation cap monitoring, KLT bin float with GST exposure, or FOMP back-charge reason-coded decomposition. The custom-ABAP rebuild fails by OEM number three. The SAP-companion product thesis: connect to SAP via standard extracts, run the missing reconciliation streams externally, write back exception status.
- **Logic:** Map SAP's native capabilities against the 10 auto-component reconciliation streams (OEM settlement, EDI/ASN with CUM, RMPV, quality debits, Section 143 job-work, free-issue steel, consignment, KLT bins, tooling, PLI/export), identify which streams SAP handles natively (document mechanics, EDI transmission, GRN, AR/AP) and which streams SAP does not handle as a standing reconciliation process (CUM drift, RMPV recomputation, Section 143 alerting, tooling cap, bin float). The companion product connects via SAP standard extracts (idoc, custom report scheduled exports, file drops), runs the missing streams as continuous reconciliation, and surfaces exceptions back to SAP through user-defined fields or external dashboards.
- **Config:** SAP S/4HANA module map (MM, SD, FI, CO), SAP scheduling-agreement document type catalogue (LP for delivery schedule, LPA for forecast), EDI IDoc message-type registry (ORDERS, DELFOR, DESADV, GSVERF), SAP standard extract endpoints (scheduling-agreement header, item, schedule lines, GRN, MIRO), companion-product reconciliation streams mapped to extract sources, deemed-supply alerting calendar, RMPV index recomputation engine, FOMP debit decomposition workflow.
- **Output:** An SAP-companion reconciliation architecture: SAP retains transactional system-of-record status, the companion product runs the 10 auto-component reconciliation streams as continuous exception management with CUM drift register, RMPV claim sheet, Section 143 deemed-supply early-warning, tooling cap monitor, KLT bin float register, FOMP reason-coded decomposition — all surfaced through dashboards with write-back to SAP user-defined fields for exception status.

### SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing

Source: https://www.terra-insight.com/insights/sbi-bank-reconciliation-india/

- **Problem:** SBI handles PSU, government, and PFMS-heavy current account flows — with longer 50-character narrations, PFMS credits tagged as PFMS/[scheme]/[FY]/[ref], and GSTN refund credits formatted as GSTN REFUND [GSTIN]/ARN-[ref]/[period]. Standard private-bank parsers mis-handle these formats and CSV-only YONO Business accounts lose structured data.
- **Logic:** SBI-specific parser separates YONO Business CSV from CMP or CMS MT940 routes. PFMS credits are classified by scheme code and routed to the matching receivable (MNREGS, GST refund, subsidy). GSTN refund credits are matched to the corresponding RFD-01 ARN plus tax period. Normalisation flattens SBI's longer narrations before UTR extraction.
- **Config:** YONO Business CSV ingestion with DD/MM/YYYY date format, MT940 for CMP or CMS accounts, PFMS-scheme routing table, and ARN-to-tax-period mapping for GSTN refunds.
- **Output:** Reconciled SBI current account ledger with PFMS credits posted to correct scheme receivables, GSTN refund credits matched to RFD-01 claims, and multi-bank normalisation enabling side-by-side HDFC-ICICI-SBI reporting.

### Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs

Source: https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india/

- **Problem:** Scanned bank statement PDFs from PSU and co-operative banks arrive as low-quality images that standard PDF parsers cannot read, blocking credit file completion.
- **Logic:** An OCR pipeline pre-processes each image to correct skew, contrast, and noise before text extraction, with a premium cloud fallback for documents that fail automated confidence thresholds.
- **Config:** Lenders submit the statement PDF through the analysis platform; no manual pre-processing is required — the pipeline detects whether a document needs OCR automatically.
- **Output:** A structured transaction table with extracted date, narration, debit, credit, and balance fields, validated against balance-chain consistency checks to catch OCR extraction errors.

### Scheduling Agreement vs Purchase Order: Financial Implications for Indian Auto Component Suppliers

Source: https://www.terra-insight.com/insights/scheduling-agreement-vs-purchase-order-auto-india/

- **Problem:** Indian auto-component finance teams inherit scheduling-agreement-based OE supply and continue running it through PO-model finance logic — per-shipment AR rows, PO-due-date aging, invoice-date revenue recognition, and PO-to-GRN three-way matching. The model breaks at the first year-end: revenue is over-recognised inside delivery tolerance, GSTR-2A/2B reconciliation drifts, AR aging shows phantom overdues, and the Section 393(1) Sl. 6(i) TDS base on conversion charges does not tie to Form 26AS.
- **Logic:** Treat the scheduling-agreement number plus release ID plus ASN plus GRN plus periodic tax invoice as the canonical match key — not the absent per-shipment PO number. Recognise revenue under Ind AS 115 at OEM-confirmed GRN quantity, not at dispatch and not at firm call-off. Raise the GST e-invoice as a periodic consolidation tied to confirmed-received quantity for the billing window. Age receivables from GRN-date plus payment term, not from invoice-date. Compute the Section 393(1) Sl. 6(i) TDS base on conversion portion of periodic invoices.
- **Config:** Customer master with scheduling-agreement number as parent, plant code and ship-to point as sub-records, delivery tolerance and reset marker per agreement. Release-ID indexing for 862 firm call-offs. ASN-to-GRN match with originating-call-off traceability. Periodic tax-invoice generator that bills confirmed-received quantity per window. AR aging clock anchored to GRN date plus term. TDS receivable register tied to conversion-charge invoice lines.
- **Output:** An SA-aware reconciliation pack per OEM showing scheduling agreement to release to ASN to GRN to periodic invoice, with delivery-tolerance handling at the ASN level and Ind AS 115 control-transfer recognition at GRN. AR aging is GRN-anchored. Section 393(1) Sl. 6(i) TDS base reconciles to Form 26AS cleanly. Year-end audit position is defensible from the canonical SA-release-ASN-GRN-invoice chain rather than reconstructed retroactively.

### Scholarship and Grant Disbursement Reconciliation for Indian Educational Institutions

Source: https://www.terra-insight.com/insights/scholarship-grant-disbursement-reconciliation-india/

- **Problem:** Indian educational institutions must reconcile scholarship and grant disbursement across the NSP DBT flow, state portals (SSP, Mahadbt, DCE, ePass), institutional aid, eligibility verification, sanctioned-vs-credited gap, fee-offset accounting through pass-through accounts, and C&AG / statutory audit evidence under GFR 2017 — all while keeping the pass-through balance zero per scheme per period and producing the beneficiary-level audit trail.
- **Logic:** Maintain a scholarship master per scheme per student per year keyed by sanction order; verify eligibility evidence per scheme rules; ingest sanctioned lists from NSP / state portal and bank credit advices; for direct-to-student schemes hold evidence only; for institution-routed schemes post fee-offset through a pass-through account and reconcile pass-through to zero per scheme per period; produce GFR 2017 utilisation evidence.
- **Config:** Scholarship configuration with scheme master (NSP central schemes, state schemes by state, institutional schemes), per-student per-year sanction order register, eligibility evidence vault (caste, income, domicile, attendance, marks), bank credit ingestion across DBT and state PFMS routes, fee-offset workflow through scheme-specific pass-through accounts, GFR 2017 utilisation certificate builder.
- **Output:** A scheme-and-year close where every sanction order reconciles to bank credit and to student fee-offset entry, every direct-to-student credit holds the evidence record, every pass-through account zeros out per period, every ineligibility finding traces to recovery action, and the C&AG / statutory audit evidence file produces beneficiary-level traceability under GFR 2017.

### Secondary Sales Gap and Stock-in-Trade Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/secondary-sales-gap-stock-in-trade-fmcg/

- **Problem:** Indian FMCG brands operate two structurally lagged sales ledgers — primary sales from the brand to the distributor or CFA and secondary sales from the distributor to the retailer reported via DMS. The arithmetic gap between them is stock-in-trade, the pipeline inventory sitting in the channel, and it is the canonical demand-truth signal for the category. DMS feeds routinely run 2 to 3 days behind real secondary transactions, distributor cycle-boundary timing distorts month-end reporting, and trade-spend accruals booked against primary sales rather than confirmed secondary pull-through inflate stock-in-trade and convert into stale Section 15(2) claims when the pipeline fails to sell through.
- **Logic:** Build the canonical stock-in-trade equation per distributor per SKU per period: closing stock-in-trade equals opening stock-in-trade plus primary sales minus secondary sales minus returns minus damages. Source primary sales from SAP SD or equivalent order-to-cash module net of credit notes, secondary sales from the DMS or distributor portal net of retailer returns, RTV returns from the reverse-logistics ledger, and damages from the breakage-and-damage register. Run a DMS-feed completeness check at every cycle close — file presence, row count variance versus trailing average, schema integrity, partition coverage — and refuse to book trade-spend accruals against distributors whose feed is incomplete. Cross-validate calculated stock-in-trade against the distributor's declared closing stock and surface variances beyond tolerance for sales-and-operations review.
- **Config:** Distributor master with GSTIN, PAN, CFA mapping, geography, DMS connection metadata; SKU master with HSN, category, current MRP, current trade-margin structure; primary-sales feed from the brand's order-to-cash with invoice and credit-note flow; secondary-sales feed from DMS with daily granularity and a configurable feed-completeness SLA per distributor; RTV register from reverse logistics; breakage-and-damage register from regional claims processing; scheme master with Section 15(2) treatment flag governing accrual eligibility; stock-in-trade target band per category (typical 14 to 35 days of secondary sales); cycle-boundary lock window that holds month-end accrual until DMS feed completeness exceeds threshold.
- **Output:** A per-distributor per-SKU stock-in-trade register reconciled cycle by cycle, with primary-to-secondary ratio drift, stock-in-trade days-of-secondary-sales, RTV and damage trend, and a DMS-feed completeness score. Channel-stuffing signature alerts at the quarter close — primary-versus-secondary growth gap, pipeline DSO extension, post-stuffing RTV spike, stale-claim conversion rate. A scheme-accrual eligibility filter that books trade-spend only against confirmed secondary pull-through, isolating stale-claim exposure to the speculative-accrual leg. A cross-foot of the channel inventory liability into the distributor receivable and trade-spend GL accounts, with audit-grade variance documentation for Ind AS 115 revenue recognition disclosure.

### School and College Fee Reconciliation for Indian Educational Institutions

Source: https://www.terra-insight.com/insights/school-college-fee-reconciliation-india/

- **Problem:** Indian schools and colleges must reconcile term-fee demand against receipts across cash, cheque, NEFT and gateway channels, accrue late fees per bye-laws, process mid-term refunds under AICTE or institutional policy, hold the fee-committee or FRA-approved fee rate as the ceiling, and produce audit-ready evidence under Societies Registration or Section 8 Companies frameworks — all while reconciling gateway MDR and GST 18% on MDR.
- **Logic:** Maintain a per-student fee demand register keyed by program × class × term × fee head; ingest receipt entries from cash counter, bank deposit slips, NEFT advice and gateway settlement files; match three-way against gateway transaction ID and bank credit net of MDR; age unpaid balances and accrue late fee per bye-laws; on refund, reconcile to original receipt and apply FRA-approved rate ceiling check; produce mandatory disclosure schedules and audit evidence.
- **Config:** Education fee configuration with program × class × term fee-head master, bye-law-driven late-fee rule, AICTE or institutional refund policy schedule, FRA approval order register where applicable, gateway settlement file ingestion (Razorpay Edu, BillDesk EduPay, ICICI Eazypay, Eduvanz, HDFC Smarthub), MDR + GST 18% recognition rule, bank reconciliation across multiple collection accounts, refund workflow with original-receipt linkage.
- **Output:** A term-end fee close where every demand reconciles to receipt and outstanding, every gateway settlement ties gross-to-net-of-MDR-and-GST against bank credit, every refund traces to original receipt with FRA-approved-rate compliance, late-fee accrual matches bye-law calculation, and the mandatory disclosure schedules align with the audit-defensible fee register.

### Section 115BAA vs PLI: Choosing the Concessional 22% Regime

Source: https://www.terra-insight.com/insights/section-115baa-vs-pli-pharma-concessional-rate-election/

- **Problem:** A Tier-1 R&D-active generic pharma formulator with an approved Section 35(2AB) in-house R&D facility and an active PLI Scheme for Pharmaceuticals allocation faces the Section 115BAA election decision for FY 2026-27. The election offers a concessional 22 percent corporate tax rate — approximately 25.17 percent effective after ten percent surcharge and four percent health-and-education cess — in place of the standard 30 percent regime, but requires irrevocable surrender of the Section 35(2AB) weighted deduction, Section 32AC/32AD, Section 33AB/33ABA, Section 35AD, Section 35CCC/35CCD, and all Chapter VI-A deductions other than Section 80JJAA. The PLI grant income itself is not surrendered — it flows through as taxable book income in either regime. The decision requires a defensible five-year projection worksheet that quantifies the Section 35(2AB) surrender loss against the eight-percentage-point rate reduction on the entire taxable income base (including the PLI grant), overlays the Section 115JB MAT-switch-off effect, and stress-tests the irrevocability under downside scenarios on R&D spend, PLI grant flow, and pre-deduction taxable income.
- **Logic:** Build a per-year projection for FY 2026-27 through FY 2030-31 with three input lines: pre-deduction taxable income, projected Section 35(2AB) claim quantum at the AY 2021-22 onward 100 percent straight-deduction rate, and projected PLI grant flow from the DoP portal disbursement schedule. Compute two scenarios per year: NORMAL regime — tax equals 30 percent (plus surcharge and cess) on (pre-deduction taxable income minus Section 35(2AB) deduction plus PLI grant), with the Section 115JB MAT computation running in parallel as the floor at 15 percent of book profit including PLI grant, and the higher of the two applied; SECTION 115BAA regime — tax equals 22 percent (plus surcharge and cess) on (pre-deduction taxable income plus PLI grant), with the Section 35(2AB) deduction surrendered (added back to the taxable base) and MAT expressly not applicable per Section 115JB sub-section (5A). Sum the tax across the five-year window under both scenarios. Elect Section 115BAA if the aggregate is lower. Overlay a downside-sensitivity block — R&D spend spike, PLI grant shortfall, brought-forward loss ineligibility — before locking the irrevocable election.
- **Config:** Per-year projection line master: pre-deduction taxable income, Section 35(2AB) approved R&D facility claim quantum, PLI grant projected disbursement per DoP portal schedule; deduction surrender schedule per Section 115BAA sub-section (2) with Section 35(2AB), Section 32AC/32AD, Section 33AB/33ABA, Section 35AD, Section 35CCC/35CCD, Chapter VI-A ex-80JJAA marked; corporate tax rate schedule for both regimes with surcharge and cess overlay; Section 115JB MAT rate at 15 percent and the sub-section (5A) opt-out flag for the Section 115BAA scenario; five-year projection window aligned to the PLI Scheme's FY 2022-23 through FY 2027-28 disbursement tail plus two subsequent years; irrevocability warning banner; downside-sensitivity block for R&D spend, PLI grant shortfall, brought-forward loss ineligibility; net-present-value discount rate for aggregating the tax difference across the five-year window.
- **Output:** A per-year Section 115BAA vs normal-regime tax comparison for FY 2026-27 through FY 2030-31 showing pre-deduction taxable income, Section 35(2AB) deduction, PLI grant flow, computed tax under each scenario, MAT overlay in the normal scenario, and the NPV-aggregated five-year tax under each regime. The recommendation output states the electing regime, the estimated five-year tax saving in Rs crore, and the downside-sensitivity outcomes under R&D spike, PLI shortfall, and brought-forward loss ineligibility scenarios. The worksheet is signed off by the CFO and outside tax counsel before the irrevocable election is filed in the annual return of income.

### Section 143 CGST for Pharma: ITC-04 Quarterly Return Reconciliation

Source: https://www.terra-insight.com/insights/section-143-cgst-job-work-pharma-formulations-itc-04/

- **Problem:** An illustrative Tier-1 pharma brand-owner running a Section 80-IE Sikkim unit as market authorisation holder sends active pharmaceutical ingredients and intermediates along with formulation specifications to a Baddi (Himachal Pradesh) third-party loan-licensee manufacturer for tablet compression, coating, and blister packaging. Q1 FY 2026-27 (April to June 2026) sees 45 Rule 45 dispatch challans covering an illustrative Rs 12.5 crore API and intermediate value; 42 return challans covering Rs 11.8 crore worth of processed goods flow back to the Sikkim principal's premises; three challans covering Rs 0.7 crore remain with the Baddi job-worker at 30 June 2026. Form GST ITC-04 for Q1 FY 2026-27 is due 25 July 2026 and reconciles four movements: goods sent to the job-worker, goods received back, goods sent from one job-worker to another, and goods still with the job-worker at quarter-end with challan age tracked against the one-year window for inputs and the three-year window for capital goods. The cross-state Sikkim-to-Baddi movement makes the job-worker's HSN 9988 job-work charges invoice an IGST 12 percent supply; the principal claims input tax credit on that IGST subject to Section 16 conditions. Because the Baddi loan-licensee is MSME-registered, the principal's job-work-charge payable sits inside Section 43B(h) scope with the 45-day payment ceiling. The reconciliation exposure is threefold: (a) a Rule 45(4) deemed-supply trigger on any challan that crosses the one-year window without return; (b) an input-tax-credit break on the job-work-charge IGST where the job-worker's GSTR-1 does not flow through to the principal's GSTR-2B in time; (c) a Section 43B(h) year-end disallowance on any job-work-charge payable outstanding beyond 45 days at 31 March.
- **Logic:** Build a challan-level movement register keyed to the Sikkim principal's GSTIN, with every Rule 45 outward dispatch tagged with the challan number, date, HSN chapter (2941 for antibiotics, 3003 for bulk drug intermediates), quantity, value, receiving job-worker's GSTIN, and expected return date (dispatch date + eleven months, giving one month buffer before the twelve-month deeming trigger). Match every inward return-of-goods challan to the corresponding outward dispatch — one-to-one where the full batch returns, one-to-many where the batch is split across multiple returns. Compute the outstanding-with-job-worker position at quarter-end and age each outstanding challan against the one-year window. Trigger a preemptive return, transfer to another job-worker under the Section 143(1)(a) proviso, or Rule 45(4) deemed-supply invoice at month eleven for any challan approaching the deeming date. Ingest the job-worker's HSN 9988 job-work-charge invoices and match each invoice to the specific dispatch challan (or challan set) that it covers; reconcile the invoice-side IGST 12 percent to the principal's GSTR-2B auto-populated ITC pool for the tax period. On the accounting and tax side, book the job-work-charge payable per invoice; flag every job-worker as MSME-registered or non-MSME; run a 30-45-90 day aging bucket per MSME-registered job-worker; schedule payment against the 45-day Section 43B(h) ceiling. File Form GST ITC-04 quarterly on the GST portal within twenty-five days from quarter-end, presenting the four-movement reconciliation and any Rule 45(4) deemed-supply crystallisation.
- **Config:** Principal plant master keyed to state GSTIN (Sikkim, Baddi, Ahmedabad, etc.), each with the Section 80-IE / 80-IC / commercial classification and unit-level GST profile; job-worker master with GSTIN, MSME registration status (Udyam certificate reference), state, HSN 9988 job-work-charge rate agreed in the manufacturing services agreement, and Section 15 MSMED Act payment terms; input HSN mapping for API and intermediates (Chapter 29 including 2941 antibiotics, Chapter 30 including 3003 bulk drug); Rule 45 challan-level register with outward dispatch date, quantity, value, receiving job-worker, and expected return date; return-of-goods challan register with inward date, quantity, value, and match to the source outward challan; challan-level ageing report with 6-month, 9-month, 11-month, and 12-month buckets; Rule 45(4) deemed-supply trigger workflow at the 11-month mark for preemptive action; job-work-charges invoice-to-challan-batch match register; job-worker HSN 9988 GST classification (IGST 12 percent for cross-state, CGST 6 percent + SGST 6 percent for intra-state); GSTR-2B ITC reconciliation for the job-work-charge IGST; job-work-charge payable ageing (30-45-90) per MSME-registered job-worker; Section 43B(h) year-end disallowance workflow; Form GST ITC-04 quarterly filing calendar (25 July, 25 October, 25 January, 25 April) per principal GSTIN.
- **Output:** A quarterly ITC-04 pack per principal GSTIN: the four-movement reconciliation (goods sent to job-worker, goods received back, goods sent job-worker to job-worker, goods still with job-worker at quarter-end) at challan level with values and quantities; an outstanding-with-job-worker ageing report against the one-year window for inputs and the three-year window for capital goods, with any challan crossing 11 months flagged for preemptive return or transfer action; a Rule 45(4) deemed-supply crystallisation log for the quarter with the deemed-date, deemed-value, deemed-tax and Section 50 interest computed; a job-work-charges invoice-to-challan match register with the IGST 12 percent (or CGST 6 percent + SGST 6 percent) ITC claim reconciled to GSTR-2B; a Section 43B(h) MSME 45-day payable ageing per MSME-registered job-worker with the year-end disallowance forecast; and the Form GST ITC-04 draft filing template ready for GST portal submission on or before the 25th of the month succeeding the quarter.

### Section 143 Deemed Supply — 1-Year Job-Work Return Rule for Textile

Source: https://www.terra-insight.com/insights/section-143-deemed-supply-textile-job-work-1-year-rule/

- **Problem:** Indian textile principals under the Section 143 CGST job-work regime send yarn, greige fabric, semi-processed cloth, and specialised inputs to external knitters, dyers, weavers, and finishers under Rule 55 delivery challans, retaining ownership throughout. Section 143(3) imposes a strict 1-year clock (3 years for capital goods) from the dispatch date. If the goods are not received back within the window, the original outward movement is retro-treated as a taxable supply from Day 0 — GST liability crystallises at the taxable value of the dispatch, Section 50 interest runs at 18% per annum from the dispatch date, and self-assessment must be reported in the GSTR-3B for the month the anniversary falls. In multi-hop textile chains passing through spinning, knitting, dyeing, weaving, and finishing units, a single-owner view of the pending balance across all hops is the difference between clean ITC-04 filing and a Section 73/74 notice.
- **Logic:** Build a pending-balance register keyed by delivery challan number. Each row captures: challan date, job-worker GSTIN, HSN, description, quantity dispatched, taxable value, process turnaround expected, and the 1-year statutory deadline. Inward return challans consume the pending balance line-by-line, matched by challan reference and reconciled at quantity level with a defined shrinkage allowance per process. A daily job runs the residual-balance report and flags every open challan at D-90 (early warning), D-60 (escalation to job-worker), and D-30 (senior-management alert). The register locks at each ITC-04 cut-off and generates the return. Any line crossing D+0 (past the anniversary) triggers a GSTR-3B self-assessment worksheet computing the deemed-supply tax and Section 50 interest, and disclosure in the next GSTR-1.
- **Config:** Delivery challan master with challan number, date, job-worker GSTIN, HSN, description, quantity, taxable value, expected turnaround, and 1-year deadline (3-year for capital goods flag); process turnaround matrix per operation (spinning, knitting, dyeing, weaving, printing, finishing) with shrinkage allowance percentage; job-worker master with GSTIN, PAN, ITC-04 reporting flag, and Section 393(1) Sl. 4 payment code (1023 for material-supplied job-work, 1024 for non-supplied); escalation thresholds (D-90, D-60, D-30) with distribution list per threshold; GSTR-3B self-assessment worksheet template for deemed-supply lines; GSTR-1 disclosure template for deemed outward supplies; ITC-04 cadence (half-yearly for turnover up to ₹5 crore, quarterly above).
- **Output:** A live pending-balance register showing every open job-work challan with days-since-dispatch and days-to-anniversary. A residual-balance dashboard by job-worker highlighting D-90, D-60, D-30, and past-anniversary lines. A GSTR-3B self-assessment worksheet for any past-anniversary lines with tax and Section 50 interest computed. A GSTR-1 outward-supply disclosure entry. An ITC-04 return generated from the register at each cut-off, tied mathematically to opening balance plus inputs sent minus inputs received equals closing balance. A monthly leakage report for finance and audit — clean job-work chains sustain zero deemed-supply crystallisations year on year.

### Section 143 Deemed Supply: What Happens When Job-Work Goods Don't Return in Time (Auto Components)

Source: https://www.terra-insight.com/insights/section-143-deemed-supply-auto-component-india/

- **Problem:** Section 143 of the CGST Act lets an auto-component Tier-1 principal send inputs or capital goods to platers, heat-treaters, machinists, painters and phosphaters on Rule 55 delivery challans without paying GST on dispatch — a concession structural to the auto manufacturing model — but conditioned on a one-year return clock for inputs and a three-year clock for capital goods running from the original principal-dispatch date even across multi-hop inter-job-worker movements; if the clock lapses, Section 143(3)/(4) deems the original dispatch to be a supply on its original dispatch date with GST plus Section 50 interest at 18% per annum from that date, and on a typical Tier-1 with 50,000 components dispatched annually across 12 job-workers a 1.5% non-return rate compounds into ₹14 lakh of tax-plus-interest exposure that surfaces only at quarterly ITC-04 or at GST audit under Section 65.
- **Logic:** Stamp every Rule 55 dispatch challan with original-dispatch date, job-worker GSTIN, input vs capital-goods classification, jigs/fixtures/moulds/dies flag (no clock), and statutory clock (1 year inputs, 3 years capital); track the single original clock across all Table 5C inter-job-worker hops without resetting; match return GRN within tolerance to close the challan; surface open-balance per job-worker; alert 60 and 30 days before the statutory window; recommend expedite-return or substitution; trigger deemed-supply provisional accrual at the 30-day band; carry the accrual through the quarter; reverse on physical return; reconcile to ITC-04 at quarter-end and to the principal's challan register.
- **Config:** Job-worker master with GSTIN, PAN, process type, registration status; Rule 55 challan series per plant per movement type; classification rule per dispatch (inputs / capital goods / jigs-fixtures-moulds-dies); multi-hop routing graph per part programme; alert thresholds 60 and 30 days; deemed-supply provisional accrual policy with finance sign-off; ITC-04 calendar by turnover band; substitution-return policy for at-risk batches.
- **Output:** An open-balance position per job-worker per quarter with days-to-deemed-supply countdown; the deemed-supply provisional accrual register and the GST-plus-interest exposure schedule; the ITC-04 pre-filing pack with original-dispatch clocks intact; the substitution-return work list; and a board-visible Section 143 risk dashboard showing exposure per programme and per job-worker.

### Section 15(2) CGST Trade Discount Valuation Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/section-15-2-cgst-trade-discount-valuation-fmcg/

- **Problem:** The Section 15(2) read with 15(3) CGST three-prong test is the single most common audit query in FMCG trade-spend reviews. Brands running 40-plus active schemes across general trade, modern trade, quick commerce, and BTL marketing typically do not maintain a per-scheme classification register; the commercial team launches schemes without finance sign-off on the Section 15(3) treatment; the TPM portal issues credit notes without capturing distributor ITC reversal evidence; CBIC Circular 92/11/2019 Type-C secondary-market schemes are routinely misclassified as Type-B post-supply discounts. The result is either over-claimed GST relief (Section 74 exposure at extended limitation) or under-claimed relief (over-stated tax cost by 5 to 18 percentage points of trade spend), and stake at year-end ranges from 0.3 to 1.2 percent of revenue depending on portfolio mix.
- **Logic:** Maintain a per-scheme treatment register keyed by scheme code with classification ex-ante into one of four buckets: Type-A invoice-recorded (Section 15(3)(a)), Type-B post-supply qualifying (Section 15(3)(b)), Type-B post-supply non-qualifying (settled as financial credit note), or Type-C secondary-market reimbursement per Circular 92/11/2019 (outside Section 15(3) entirely). For Type-B schemes, route the credit-note posting through a three-prong gate that verifies the scheme circular pre-dates the dispatch (timing prong), the credit note references the underlying invoice numbers (linkage prong), and the distributor ITC reversal evidence is on file before the GSTR-1 amendment is filed (reversal prong). For schemes where the reversal evidence is pending past 30 November of the following FY, re-classify as non-qualifying and reverse the GST credit in the next amendment cycle.
- **Config:** Scheme master with code, percentage, geography, category, validity dates, Type-A/B/C classification flag, Section 15(3) qualifying flag (for Type-B), and rate-effective-date for pre- versus post-22-September 2025 supplies; distributor master with GSTIN, PAN, ITC-reversal acknowledgement evidence link; credit-note template with mandatory invoice-reference array and Section 15(3) treatment tag; ITC-reversal evidence intake (revised GSTR-3B Table 4(B)(2) entry or CA-certified acknowledgement) with cut-off enforced at 30 November of the following FY; GSTR-1 amendment cycle linkage to the credit-note register; quarterly Section 15(3) per-scheme audit against the three-prong rule.
- **Output:** A per-scheme Section 15(2) treatment register that classifies every active and prior-FY scheme into Type-A/Type-B-qualifying/Type-B-non-qualifying/Type-C, with the underlying agreement, invoice-linkage, and distributor ITC-reversal evidence stored against each Type-B-qualifying credit note. Quarter-end reports surface schemes with pending ITC-reversal evidence by ageing bucket, schemes mis-classified as Type-B that fail the three-prong test, and schemes mis-classified as Type-A that lack invoice-level recording. The register feeds the GSTR-1 amendment cycle, the year-end Ind AS 37 contingent-liability disclosure, and the statutory audit query response on trade-spend GST treatment.

### Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track

Source: https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india/

- **Problem:** GST input tax credit is permanently and irrecoverably lost if not claimed by November 30 of the following financial year. No recovery mechanism exists after this deadline.
- **Logic:** Track every purchase invoice against GSTR-2B appearance. Flag invoices approaching the Section 16(4) deadline where supplier has not filed GSTR-1. Distinguish from Rule 37/37A reversals which have no time bar on re-claims.
- **Config:** Deadline: November 30 of following FY (Finance Act 2022 amendment). Section 16(2)(aa) prerequisite: invoice must appear in GSTR-2B. Rule 36(4): ITC cannot exceed GSTR-2B.
- **Output:** ITC at-risk report by deadline proximity, supplier follow-up queue for unfiled GSTR-1, and claimable ITC register reconciled to GSTR-2B before the November 30 cutoff.

### Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence

Source: https://www.terra-insight.com/insights/section-16-itc-ims-regime-india/

- **Problem:** Section 16 of the CGST Act has five conditions for ITC claim, each with its own evidence requirement. The IMS regime adds explicit Acceptance as a Rule 36(4) compliance step. The audit defence package is now a five-artefact chain per invoice that spreadsheet workflows cannot reliably maintain at scale, leaving listed entities and high-volume buyers exposed to ITC reversal in statutory GST audit.
- **Logic:** The compliant ITC workflow links five evidence artefacts per invoice: tax invoice, goods or services receipt evidence, supplier GSTR-1 filing proof, IMS Accept timestamp, and 180-day payment evidence. Each artefact is captured at the appropriate workflow stage and bound to the GSTR-3B Table 4 line where the ITC was claimed. Rule 37 reversal at day 181 is triggered automatically for unpaid invoices, with re-claim on subsequent payment.
- **Config:** Tax invoice repository linked to purchase register, GRN or service-acceptance system integration, IMS Accept timestamp capture at decision time, supplier payment tracking with 180-day alert, and Rule 37 reversal automation tied to GSTR-3B Table 4(B).
- **Output:** Per-invoice five-artefact audit pack, Rule 36(4) compliance dashboard, Rule 37 reversal report per period, and GSTR-3B Table 4 ITC line reconciled to the underlying evidence chain ready for statutory audit defence.

### Section 393(1) Sl. 6(i) TDS on Auto-Component Job Work: Rate, Threshold and FY 2026-27 Compliance

Source: https://www.terra-insight.com/insights/section-194c-tds-auto-component-job-work-india/

- **Problem:** Tier-1 auto-component manufacturers deduct TDS on every conversion-charge invoice from plating, heat-treatment, machining, painting and assembly job-workers under Section 393(1) Sl. 6(i) of the Income Tax Act 2025 (payment codes 1023 / 1024, replacing legacy Section 194C from 1 April 2026), at 1% for individual/HUF job-workers and 2% for company/LLP/firm job-workers, subject to thresholds of ₹30,000 per single contract and ₹1,00,000 aggregate per job-worker per financial year — and the principal must track cumulative payments per job-worker PAN to know exactly when the aggregate threshold is breached, deposit the deducted TDS on the prescribed challan by the 7th of the following month, file Form 168 quarterly, reconcile to each job-worker's Form 26AS / AIS reflection, and maintain a clean cross-reference to legacy Section 194C entries for Q4 FY 2025-26 and earlier.
- **Logic:** Tag every job-worker in the master with PAN, legal form (individual/HUF/company/LLP/firm), GSTIN and applicable Section 393(1) Sl. 6(i) rate; capture every conversion-charge invoice and accumulate gross paid per PAN per financial year; check both thresholds (₹30,000 per invoice and ₹1,00,000 aggregate per FY) before each payment; deduct TDS on first breach and on every subsequent payment in the year; deposit on the monthly challan by the 7th with payment codes 1023 / 1024; file Form 168 quarterly with cumulative per-PAN totals; cross-reconcile to job-worker Form 26AS / AIS via PAN; maintain cross-era 194C ↔ 393(1) Sl. 6(i) cross-reference for at least one full FY cycle.
- **Config:** Job-worker master with PAN, GSTIN, legal form, applicable Section 393(1) Sl. 6(i) rate (1% or 2%) and Section 206AA fallback at 20% on missing-PAN; per-FY cumulative threshold tracker per PAN; monthly TDS challan calendar (7th of following month); quarterly Form 168 calendar; deductee invoice register with cross-era 194C / 393(1) Sl. 6(i) code mapping; reconciliation link to Form 26AS / AIS download per job-worker.
- **Output:** A live deductee dashboard per job-worker showing cumulative gross paid for the year, threshold-breach status, TDS deducted to date, challan deposit confirmation per month, Form 168 filed position per quarter, and the cross-tie to Form 26AS / AIS — with cross-era reconciliation to legacy 194C entries preserved through the FY 2026-27 cycle.

### Section 194O TDS at 0.1% (Was 1%): Current Rate History Under Income-tax Act 2025

Source: https://www.terra-insight.com/insights/section-194o-tds-0-1-percent-current-rate-history-india/

- **Problem:** Indian e-commerce participants selling through Amazon, Flipkart, Meesho, Myntra, ONDC, and SaaS marketplaces face a Section 194O TDS regime whose specified rate dropped from 1% to 0.1% on 1 October 2024 and whose legacy section number changed from 194O of the Income-tax Act 1961 to §393(1) Sl. 8(v) payment code 1035 of the Income-tax Act 2025. Operators continuing to deduct at the old 1% rate, books still accruing TDS receivable at 1%, and Form 26AS / Form 168 entries that mix pre-October-2024 and post-October-2024 invoices all create silent reconciliation errors that surface only at year-end.
- **Logic:** Reconciliation classifies every operator-facilitated sale on its payment-date stamp, applies the rate-by-date schedule (1% if payment date before 1 October 2024, 0.1% if on or after, 5% override under §394A if PAN/Aadhaar not furnished), computes the expected TDS on the gross sale value (not net settlement), and matches against the operator's deduction line on the settlement file plus the corresponding entry in Form 26AS / AIS / Form 168 quarterly statement, with the threshold exemption (₹5,00,000 cumulative for resident Individual/HUF with PAN) applied year-to-date per operator.
- **Config:** Operator-settlement-file connector with sale-date, payment-date, gross-amount, marketplace-commission, and TDS-deduction extraction; rate-by-date schedule keyed on payment date with cut-over 1 October 2024 (1% to 0.1%); PAN/Aadhaar-furnished flag per operator-participant relationship driving the §394A 5% override; participant-type classifier (resident Individual/HUF vs company/firm/LLP) gating the ₹5,00,000 threshold; cumulative year-to-date threshold counter per operator; Form 26AS / AIS / Form 168 matcher with quarter-specific reconciliation cadence.
- **Output:** A per-transaction Section 194O expected-vs-actual TDS variance report with recoverable over-deduction (operator still applying 1%), shortfall flags (TDS not deducted where threshold has been breached), threshold-trip alerts when year-to-date facilitated sales cross ₹5,00,000 for a resident Individual/HUF, and a quarterly cash-flow forecast for TDS receivable to be claimed in the next ITR.

### Section 194Q on API Purchases: The Buyer-Seller Reconciliation

Source: https://www.terra-insight.com/insights/section-194q-tds-api-raw-material-purchase-pharma-reconciliation/

- **Problem:** A Tier-1 pharma formulator running an aggregate FY 2026-27 procurement spend of the order of Rs 82 crore on Chapter 29 active pharmaceutical ingredients from a single Tier-2 Chapter 29 API supplier — with parallel procurement across forty to sixty such suppliers at varying spend bands — must operate a per-supplier-PAN Section 194Q cumulative-purchase register, identify the threshold-crossing month in which the buyer's TDS obligation supersedes the seller's Section 206C(1H) TCS collection, coordinate a written intimation to the seller from the crossing month onward, reconcile the buyer's payment code 1031 TDS filing on Form 168 against the seller's credit statement, and maintain a Section 201(1A) interest exposure register for any delayed-deduction gap. Failure at any step produces a mid-year mutual-exclusion breach in which either the seller continues Section 206C(1H) TCS collection when the buyer is already deducting Section 194Q TDS (over-collection on the same transaction) or the buyer fails to deduct Section 194Q TDS after threshold crossing (Section 201(1A) interest exposure and TDS-demand-order risk).
- **Logic:** Build a per-supplier-PAN cumulative-purchase register keyed to the seller's PAN, refreshed on every invoice receipt. Compare the running cumulative purchase from the seller-PAN in the current financial year against the Rs 50 lakh Section 194Q threshold. Flag the invoice on which the cumulative crosses the threshold. From that invoice's tax-year month onward, apply the 0.1 percent Section 194Q TDS deduction on the incremental sum above Rs 50 lakh at the earlier of credit to the seller's account or payment. Issue a written intimation to the seller confirming the buyer is deducting Section 194Q TDS from the crossing month onward. Coordinate with the seller's accounts receivable team to confirm cessation of any Section 206C(1H) TCS collection on subsequent invoices to the same buyer. File the quarterly TDS return under payment code 1031 on Form 168. Reconcile the seller's credit statement post-quarter against the buyer's filed deductions per PAN. Maintain a Section 201(1A) interest exposure register tracking any month in which the deduction was delayed past the crossing point.
- **Config:** Vendor master with per-supplier PAN, GSTIN, financial-year-to-date cumulative purchase value, threshold-crossing flag, threshold-crossing invoice number and date, Section 194Q applicability trigger status (buyer's turnover in the immediately preceding financial year > Rs 10 crore verified), Section 206C(1H) TCS collection history from the seller (with per-invoice TCS amount), written-intimation-to-seller flag with intimation date, quarterly payment-code-1031 TDS filing status per PAN, Form 168 filing acknowledgement number per quarter, seller's credit statement reconciliation status per quarter, Section 201(1A) interest exposure per PAN per delayed-deduction month, and audit trail for CBDT Circular 13/2021 mutual-exclusion compliance.
- **Output:** A month-end vendor-master Section 194Q status pack: per-supplier-PAN cumulative purchase against the Rs 50 lakh threshold with a flag on suppliers whose threshold crossed during the tax-year month, the payment-code-1031 TDS deduction summary for the month with per-invoice detail, the coordination-intimation status to sellers whose threshold crossed, the reconciliation of the seller's credit statement against the quarterly filed deductions, the Section 201(1A) interest exposure summary for any delayed-deduction gaps, and the audit trail supporting the CBDT Circular 13/2021 mutual-exclusion position. Year-end the pack rolls up to the aggregate Section 194Q TDS deducted per PAN, the aggregate Section 206C(1H) TCS collected pre-crossing by the same PAN's suppliers, and the interest exposure register for the assessing officer's scrutiny cycle.

### Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus

Source: https://www.terra-insight.com/insights/section-194t-partner-firm-tds/

- **Problem:** From April 1, 2026, every partnership firm and LLP must deduct 10 percent TDS under Section 194T on salary, remuneration, commission, bonus, and interest paid to partners, aggregated per partner, once the ₹20,000 annual threshold is crossed. Missing the deduction triggers Section 201(1) assessee-in-default liability plus a 30 percent Section 40(a)(ia) disallowance of the partner expense.
- **Logic:** Track cumulative credits per partner across all payment types — monthly remuneration, commission, bonus, and annual interest on capital — and trigger 10 percent TDS on the first credit after the running total crosses ₹20,000. Deduct at credit to the partner current account or payment, whichever is earlier, including year-end bulk credits. Report in Form 140 under Section 393(3) Serial 7, payment code 1067, and issue Form 131 certificates to each partner.
- **Config:** Per-partner cumulative credit counter across remuneration, commission, bonus, and interest. Payment code 1067 mapping for Form 140 under the 2025 Act. Form 131 certificate workflow per partner per quarter.
- **Output:** Correct 194T deductions from the first qualifying credit, protected partner expense deduction with no Section 40(a)(ia) disallowance, reconciled Form 168 credits under the partner's PAN, and timely Form 131 certificates for each partner's ITR claim.

### Section 271DB: ₹5,000/Day Penalty for Not Offering UPI/RuPay (₹50 Cr+ Turnover)

Source: https://www.terra-insight.com/insights/section-271db-penalty-upi-rupay-50-cr-turnover-india/

- **Problem:** Businesses with previous-year turnover above ₹50 crore face a ₹5,000-per-day penalty under Section 271DB if any sales channel fails to offer the electronic modes prescribed under Rule 119AA — UPI bank-account, BHIM-UPI QR, and RuPay debit. The gap typically opens on a non-website channel (B2B portal, mobile app, call-centre payment link) where the default payment options were chosen for operational convenience and never reviewed for §269SU compliance. The penalty accrues per day from the date the gap opened, not the date it was discovered — so detection lag is real liability.
- **Logic:** The audit logic is a channel-by-channel acceptance matrix. For every sales channel through which the business accepts payment, confirm that all three prescribed modes are (a) configured at the gateway, (b) enabled at the merchant checkout layer, and (c) actually selectable in the customer-facing flow. Any channel that fails any of the three tests is a §271DB exposure. Quantify exposure as ₹5,000 multiplied by the number of days since the prescribed mode was last verified as available on that channel.
- **Config:** Channel-acceptance matrix per sales surface (website, mobile app, B2B portal, in-store POS, IVR, payment link), prescribed-mode flag per channel for UPI bank-account / UPI QR / RuPay debit, last-verified-date per channel-mode cell, daily-penalty accrual schedule, and evidence-archive policy keyed to quarterly checkout audits.
- **Output:** Section 271DB exposure schedule with per-channel days-of-non-compliance and rupee penalty; rectification action list with owner, gateway change-request reference and target-restore date; auditor-ready evidence pack of checkout screenshots and gateway configuration logs per channel.

### Section 35(2AB) for Pharma R&D: The DSIR Reconciliation Playbook

Source: https://www.terra-insight.com/insights/section-35-2ab-weighted-deduction-pharma-r-and-d-reconciliation-guide/

- **Problem:** A large Indian pharma company with a DSIR-approved in-house R&D centre must reconcile its R&D cost-centre general ledger through four filters before the deduction can be claimed under Section 35(2AB) — the Ind AS 38 six-condition development-phase test that decides which cost is capitalised as intangible in the books, the revenue-versus-capital classification that decides which cost sits in each Form 3CL sub-schedule, the DSIR-listed-item filter that decides which cost is eligible at all, and the double-deduction bar that removes any cost also claimed under another chapter. The four filters interact and are not order-independent — a capitalised development-phase intangible is still revenue-expensed for tax under Section 35(2AB), and a DSIR-listed capital equipment item is capital under 35(2AB) even where it is capitalised in the books under Ind AS 16. Manual reconciliation across four filters typically loses 3 to 5 percent of the claim quantum, mis-classifies the revenue-versus-capital split, and leaves the Ind AS 12 deferred tax liability under-recognised — exposing the company to an assessment-stage disallowance and to a Section 143(3) adjustment at scrutiny.
- **Logic:** Extract the R&D cost-centre general ledger by natural account and by cost element for the previous year, tag each cost element against the DSIR-listed item taxonomy (positive list per DSIR/Sec35(2AB)/1/2021 for revenue expenditure; positive list for capital expenditure with land and building excluded), tag each cost element against the Ind AS 38 development-phase indicator (capitalised as intangible in books versus expensed), and tag each cost element against any other-chapter deduction flag (double-deduction bar). Aggregate the DSIR-listed revenue expenditure by month against the R&D cost centre control account. Aggregate the DSIR-listed capital expenditure by asset class against the fixed-asset register. Feed both aggregates into the Form 3CL preparation working paper and cross-check against the statutory auditor's independent test-of-detail sample. Compute the Ind AS 12 deferred tax on the delta between book carrying amount (Ind AS 38 intangible plus Ind AS 16 fixed-asset residual) and tax written-down value (nil for revenue-expensed items, capital-goods depreciation base for capex items). Produce the Form 3CLA quantum for the return of income and the deferred-tax movement schedule for the notes to the financial statements.
- **Config:** R&D cost centre master with cost centre code, natural account code, DSIR-listed-item flag (revenue or capital or excluded), Ind AS 38 phase flag (research or development or not-applicable), Ind AS 38 six-condition-test date stamp per capitalised intangible, other-chapter deduction flag; DSIR facility master with Form 3CM approval reference, approval validity period, list of approved R&D programmes, list of approved scientific personnel; fixed-asset register with asset code, capitalisation date, DSIR-eligibility flag, Ind AS 16 depreciation, income-tax depreciation under Section 32, and delta for deferred tax computation; auditor working-paper cross-reference schedule for the Form 3CL sample; Section 115BAA election flag at the assessee level; entity master with Section 92BA related-party transaction flag on backward-integration API transfers to formulation plants under the same group.
- **Output:** A year-end DSIR reconciliation pack: R&D cost centre extract tagged by DSIR-listed status and Ind AS 38 phase, revenue expenditure aggregate by month against the R&D control account, capital expenditure aggregate by asset class against the fixed-asset register, Form 3CL preparation working paper with the certified quantum split by revenue and capital, Form 3CLA schedule for the return of income, Ind AS 12 deferred tax movement showing the timing difference between book and tax treatment, and — where the group operates a backward-integration API transfer to a related formulation plant — the Section 92BA specified domestic transaction schedule with Rule 10D documentation cross-reference.

### Section 393(1) Sl. 4 (194C) Contract Manufacturing and Co-Pack TDS for FMCG

Source: https://www.terra-insight.com/insights/section-393-194c-contract-manufacturing-fmcg/

- **Problem:** Indian FMCG brands running contract-manufacturing and co-pack relationships across cookies, biscuits, snacks, and beverages must apply Section 393(1) Sl. 4 of the Income-tax Act 2025 — successor to legacy Section 194C — on every conversion-charge invoice, but the operational execution runs across three disconnected registers: the accounts-payable co-pack invoice ledger, the TDS deduction and challan register, and the contractor's Form 26AS. Payment code 1001 (1 percent for Individual/HUF) and payment code 1023 (2 percent for other constitutions) must be assigned per contractor PAN, thresholds (₹30,000 single-invoice, ₹1,00,000 FY aggregate) trigger deduction, ingredient-supply model complicates the gross-versus-net conversion-charge decision, and the CGST Schedule II Entry 3 job-work classification determines that the contract belongs in Sl. 4 not Sl. 8. Broken reconciliation leaves the brand exposed to Section 396(3) interest on under-deduction and creates 26AS gaps that surface as contractor disputes at year-end.
- **Logic:** Build a contractor master keyed by PAN, constitution flag (Individual/HUF vs other), FSSAI licence number, contract effective dates, applicable payment code (1001 or 1023), and rate. Feed the accounts-payable invoice ledger into a rolling per-contractor per-FY aggregate that rate-flags any invoice crossing ₹30,000 individually or breaching the ₹1,00,000 FY cumulative. For each triggered invoice, compute TDS on the gross conversion charge (excluding brand-supplied ingredient movements under ITC-04 job-work challan, which are not consideration to the contractor), post the deduction to the deduction register, generate the challan for ITNS 281 payment by the 7th of the following month, and feed the deduction into the quarterly TDS return. Three-way reconcile the invoice ledger to the deduction register to the Form 26AS extract each quarter. Flag failures by mode — deduction booked but not paid, challan paid but not filed, wrong payment code, PAN mismatch — and route each to its corrective action within the return-revision window.
- **Config:** Contractor master with PAN, constitution flag, FSSAI licence, contract effective dates, and default payment code (1001 or 1023); invoice ledger feed from accounts payable with contractor PAN, invoice number, invoice date, gross value, GST split, and reimbursement flag; ITC-04 job-work challan feed from the plant's movement register (so brand-supplied ingredient movements are excluded from the deductible base); TDS challan register with CIN, deduction period, and payment code; quarterly TDS return submission (Form 26Q under legacy, successor equivalent under 2025 Act) with per-deductee PAN and payment code; Form 26AS extract per contractor per quarter for three-way match; interest calculator under Section 396(3) at 1 percent per month for late deduction and 1.5 percent per month for late deposit; contract file with the underlying agreement citing FSSAI numbers of both parties and the ingredient-supply schedule.
- **Output:** A quarterly contract-manufacturing TDS reconciliation pack: opening contractor liability, period conversion-charge invoices, per-contractor rolling FY aggregate showing threshold-crossing dates, per-invoice TDS deducted split by payment code (1001 vs 1023), challans paid with CIN references, TDS return filed with acknowledgement, and Form 26AS three-way reconciliation status per contractor. Failures are split by mode — deduction gap (needs additional deduction plus Section 396(3) interest), challan gap (needs late-payment challan plus interest), return-filing gap (needs revised return), payment-code gap (needs return correction). The pack feeds the year-end audit under CARO 2020 clause 3(vii) and the Section 396(3) interest exposure disclosure.

### Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation

Source: https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation/

- **Problem:** Section 393 of the Income Tax Act 2025 consolidates 194C, 194J, 194H, 194I, 194A, and 194Q into sub-clauses of a single section from April 1, 2026. TDS receivable ledgers that only store legacy codes will show false gaps against Form 26AS entries carrying 393(1) Sl. 6(i), 393(1) Sl. 6(iii), 393(1) Sl. 1(ii), 393(1) Sl. 2(ii), 393(1) Sl. 5, and 393(1) Sl. 8(ii) identifiers.
- **Logic:** Store both code sets side by side at the ledger level, linked through a section mapping master. Match each TDS receivable entry to Form 26AS using the code that applies on its deduction date, not a single fixed code per vendor. Ignore bank narration for section identification — it lags legislative changes — and rely on TRACES return data as the authoritative source.
- **Config:** Section mapping master with sub-clause metadata. Ledger field that holds both legacy section and 2025 Act sub-clause. Cross-era matching mode with transaction-date routing.
- **Output:** TDS receivable ledgers that reconcile cleanly against Form 26AS across the FY 2025-26 to FY 2026-27 transition, correct aggregate credits for IT and services companies receiving TDS under multiple sub-clauses, and an audit trail traceable to the section code active on each deduction date.

### Section 393(2) TDS on Foreign Software Licences: Royalty vs Service Distinction

Source: https://www.terra-insight.com/insights/section-413-tds-foreign-software-license-india/

- **Problem:** Indian buyers of foreign software licences — AWS, Microsoft, Adobe and similar — must classify each contract as royalty (TDS at treaty rate under Section 393(2), payment code 1057 under §393(2) Sl. 17) or business income (no TDS without PE) post the Engineering Analysis ruling, while also screening for equalisation levy on digital services.
- **Logic:** Apply a contract-by-contract test on copyright transfer, customisation, and source-code rights; collect TRC, Form 10F and PE declaration before deducting at the DTAA rate; file Form 15CA/15CB before each remittance; reconcile the TDS challans, return, and books monthly.
- **Config:** Section 393(2) + payment code 1057 under §393(2) Sl. 17 for royalty and FTS, Engineering Analysis SC ruling 2021, Equalisation Levy Act 2016, Section 10(50) exemption when EL applies, Forms 15CA/15CB pre-remittance, DTAA rate v domestic rate test.
- **Output:** Foreign vendor master with royalty / EL / business-income classification, TDS deduction register tied to challans, Form 26Q reconciliation, and a Form 15CA/15CB log keyed to each outward remittance.

### Section 43B(h) MSME 45-Day Powerloom Procurement Reconciliation for Textile

Source: https://www.terra-insight.com/insights/section-43b-h-msme-45-day-powerloom-procurement-textile/

- **Problem:** A Surat synthetic mill or Bhilwara suiting principal buying grey fabric from 40 to 80 Udyam-registered powerloom weavers per quarter must reconcile every supplier invoice against the Section 43B(h) 45-day clock — measured from acceptance of goods, not from invoice date — and flag any invoice paid beyond the window for permanent-year disallowance and Section 16 MSMED compound interest. The mill's payable ageing typically shows a bi-modal distribution: 60 to 70 percent of invoices are paid inside 45 days (fully deductible), and a long tail of 30 to 40 percent slips to day 60 to 90 because of working-capital pressure at quarter-end, disputed short-shipments, or GRN-to-invoice gaps that hold the payment cycle. Manual tracking on a spreadsheet cannot distinguish Udyam-registered micro/small from medium (medium is outside 43B(h)) and cannot compute the 3× bank-rate compound interest with monthly rests for the Section 22 disclosure. Year-end discovery via Form 3CD reporting is the standard failure mode.
- **Logic:** Build a Udyam MSME supplier register keyed by URN with Micro/Small/Medium classification tier (only Micro and Small trigger 43B(h)), URN verification date (portal check at least once per FY), written-agreement flag (agreement in writing extends the clock to 45 days; absence collapses it to 15 days), and product tier (manufacturer vs trader — CBDT clarification excludes traders). For every supplier invoice, capture GRN date (which anchors the acceptance-of-goods date and starts the clock) and payment date, and compute days elapsed from GRN to payment. Bucket invoices into three states: paid within window (deductible), paid beyond window (deduction disallowed in year of accrual, moves to year of actual payment), and unpaid at year-end (permanent disallowance in current year and Section 16 interest running). Compute the Section 16 compound-interest liability at 3× the prevailing RBI bank rate with monthly rests from day 46 to the earlier of payment date or 31 March. Aggregate the disallowance for the tax computation and the Section 22 audit disclosure.
- **Config:** Udyam supplier master with URN, PAN, Micro/Small/Medium tier, manufacturer-vs-trader flag, and Udyam portal last-verified date; written-agreement flag per supplier (default 15-day window if no agreement; 45-day window if agreement); GRN-to-invoice register matching purchase order, GRN, and supplier invoice with acceptance date driven by GRN completion; payment register keyed by supplier and invoice; RBI bank rate feed (current and historical, for computing period interest); Section 43B(h) year-end cutoff at 31 March (or specified year-end); Section 16 MSMED interest computation with monthly compounding; TDS taxonomy — payment code 1023 (Section 8 Sl. 4, principal-supplied material weaver job-work) or code 1024 (weaver-sourced material outright purchase) depending on commercial pattern per supplier.
- **Output:** A month-end Section 43B(h) exposure pack: total accrued value from Udyam-registered Micro and Small suppliers in the period, split by paid-within-window (deductible), paid-beyond-window (deduction moves to year of payment), and unpaid (permanent disallowance risk if not paid by year-end). Supplier-level 45-day clock with days-elapsed-since-GRN for every open invoice, sorted by exposure. Section 16 MSMED interest computation with month-rest accrual at 3× the RBI bank rate, aggregated for the Section 22 audited-statement disclosure. Year-end Form 3CD line for the tax-audit report — 43B(h) disallowance figure and Section 23 MSMED interest inadmissibility figure — ready for the auditor. Payment-window alerts at day 30, day 40, and day 44 give the finance team enough runway to prioritize the invoice for release.

### Section 52 TCS on Quick Commerce FMCG — 2026 Reconciliation Guide

Source: https://www.terra-insight.com/insights/section-52-tcs-quick-commerce-fmcg-reconciliation/

- **Problem:** Quick commerce ECOs — Blinkit, Zepto, Swiggy Instamart, BBNow — facilitate the supply of FMCG goods by registered brands and sellers and collect TCS under Section 52 CGST at the notified 0.5% rate (down from the 1% statutory ceiling effective 10 July 2024 via Notification 15/2024-CT). The brand is the supplier of record; the ECO is not the deemed supplier under Section 9(5) because goods do not fall within the four notified service categories. The reconciliation pain sits at three points: matching per-order net taxable value across thousands of daily orders from each ECO to the consolidated GSTR-8 line; accepting or rejecting the TCS line on GSTR-2A Part-C; and tying the accepted credit in the electronic cash ledger back to output GST liability for the period.
- **Logic:** Build a per-order outward-supply register from each ECO's settlement file — GSTIN of brand, GSTIN of ECO, order date, order ID, net taxable value, gross GST, TCS at 0.5%. Aggregate to ECO-month totals. Parse GSTR-8 / GSTR-2A Part-C for the matching ECO-month TCS line. Match by ECO GSTIN and period. Classify the variance into one of: ECO under-reported (file a correction request), brand register includes returns/cancellations not yet reflected in GSTR-8, or genuine timing lag (next-month resolution). Accept the matched line on GSTR-2A Part-C; the credit lands in the electronic cash ledger; tie the cash-ledger accretion to output GST utilisation for the period.
- **Config:** ECO master with GSTIN, platform name, contract effective dates, applicable TCS rate (0.5% notified or 0.25% + 0.25% intra-state split); brand GSTIN master across states; settlement-file format per ECO with order-level net taxable value; period calendar with GSTR-8 filing date (10th of succeeding month); GSTR-2A Part-C scrape configured per GSTIN per period; output GST liability feed from the brand's GSTR-1/3B; cash-ledger movement feed; HSN-rate master post-22 September 2025 GST 2.0 transition (5% slab on soaps/shampoos/toothpaste/biscuits/chocolates; 40% NSAB slab on aerated and sweetened beverages).
- **Output:** A monthly Section 52 TCS reconciliation pack per ECO: gross outward supply via platform, net taxable value (post returns/cancellations), TCS collected at 0.5%, GSTR-8 line filed by ECO, accepted on GSTR-2A Part-C, credit accretion in the electronic cash ledger, utilisation against output GST liability for the period. Variance register flags ECO under-collection, brand register over-statement, and timing lags by line. The pack feeds GSTR-1 outward supply reporting, GSTR-3B output-tax-utilisation working papers, and the year-end GSTR-9C reconciliation with primary-source citation to Section 52 and Notification 15/2024-CT.

### Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk

Source: https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation/

- **Problem:** Under Section 43B(h), payments to MSME-registered suppliers must be made within 15 or 45 days of acceptance. Overdue payments are disallowed as business expenditure in the payer's ITR.
- **Logic:** Match each MSME vendor invoice to its payment date. Calculate days outstanding from acceptance date. Flag invoices exceeding 15-day or 45-day thresholds. Validate vendor MSME status via Udyam portal.
- **Config:** 15-day threshold with written agreement, 45-day threshold without agreement, Udyam registration validation, acceptance date equals invoice date or goods receipt date.
- **Output:** MSME compliance tracker showing overdue invoices, estimated tax disallowance amount, vendor-wise aging report, and corrective payment priority queue.

### Section 54(3) RFD-01 for Pharma: The End-to-End Filing Workflow

Source: https://www.terra-insight.com/insights/section-54-3-cgst-rfd-01-pharma-inverted-duty-filing-workflow/

- **Problem:** A Tier-1 integrated pharma formulator running a Hyderabad plant with an illustrative August 2026 monthly Chapter 30 outward supply of the order of Rs 42 crore at 5 per cent output must close its books, file GSTR-3B by the twentieth of September, prepare Statement 1A and Statement 3A, compute the Rule 89(5) Maximum Refund Amount, draft the Rule 89(2)(l) declaration and Undertaking, upload the RFD-01 on the common portal, track the Form GST RFD-02 acknowledgement inside the fifteen-day Rule 90 clock, track the Section 54(6) provisional refund of 90 per cent inside the seven-day clock from acknowledgement, respond to any Form GST RFD-03 deficiency memo, and track the final Form GST RFD-06 sanction — all while the two-year filing window under Section 54 continues to run against the plant. The workflow must reconcile the RFD-01 draft against GSTR-3B Table 4 (eligible ITC) and Table 3.1 (outward tax liability), the Statement 1A input register against the plant's own purchase register and the GSTR-2B, the Statement 3A outward register against the filed GSTR-1, and the Section 54(6) provisional refund tracker against the treasury projection.
- **Logic:** The workflow runs in fifteen sequential steps per GSTIN per tax period. Close the plant's input register on the last day of the tax period. Reconcile the plant's accounting ITC ledger against the auto-populated GSTR-2B at invoice level. File GSTR-3B by the twentieth of the following month with Table 4 eligible ITC and Table 3.1 outward tax liability populated. Extract the outward supply detail from the filed GSTR-1. Build the Net ITC composition register decomposed by input HSN chapter, holding input-services and capital-goods ITC in separate ledgers that do not feed the Rule 89(5) numerator. Compute the Maximum Refund Amount using the Notification 14/2022 amended formula. Prepare Statement 1A (invoice-level input register) and Statement 3A (outward supply invoice register). Draft the Rule 89(2)(l) declaration and the Undertaking. Upload the RFD-01 with annexures. Track the RFD-02 acknowledgement inside the fifteen-day Rule 90 clock. Respond to any RFD-03 deficiency memo and refile. Track the RFD-04 provisional refund of 90 per cent inside the Section 54(6) seven-day clock from acknowledgement. Respond to any RFD-08 show-cause notice. Track the final RFD-06 sanction and update the treasury projection against the accumulated inverted-duty ITC position.
- **Config:** Plant master with GSTIN, state, tax-period cutover calendar, and the RFD-01 filing-window monitor keyed to the two-year Section 54 clock. Input HSN register keyed to Chapter 29 (2941 antibiotics, other organic chemicals), Chapter 30 (3003 bulk drug mixtures), Chapter 27 (industrial solvents — hexane, isopropyl alcohol, methanol, toluene, methyl ethyl ketone), Chapter 39 (polymer films, HDPE bottles, blister foils), Chapter 48 (cartons, leaflets), and excipient chapters 11, 17, 38, 3505. Net ITC composition register per HSN chapter per tax period with input-services and capital-goods ITC held separate. GSTR-3B Table 4 and Table 3.1 tie-out to the Net ITC and outward tax liability lines. Statement 1A invoice-level input register builder tied to the purchase register and GSTR-2B at supplier GSTIN and invoice number granularity. Statement 3A outward supply invoice register builder tied to the filed GSTR-1. Rule 89(2)(l) declaration and Undertaking template library. Form GST RFD-01 through RFD-08 lifecycle tracker with acknowledgement, provisional-refund, deficiency-memo response, and final-sanction date-stamps. Treasury projection against the Section 54(6) provisional refund of 90 per cent and the final Section 54(5) sanction timing.
- **Output:** A month-end multi-plant Section 54(3) RFD-01 filing pack per GSTIN: filed GSTR-3B with Table 4 and Table 3.1 populated, filed GSTR-1 outward supply detail, Rule 89(5) Maximum Refund Amount computation with amended-formula step, Net ITC composition decomposed by input HSN chapter with the Chapter 27 solvent proportion disclosed as a distinct line, Statement 1A and Statement 3A annexures tied out to the purchase register and outward register at invoice level, Rule 89(2)(l) declaration and Undertaking, RFD-01 draft ready for portal upload, and a rolling lifecycle tracker following RFD-02 acknowledgement, RFD-04 provisional refund, any RFD-03 deficiency memo response, and RFD-06 final sanction. A parallel treasury projection maps each filed RFD-01 to its expected 90 per cent provisional receipt inside the Section 54(6) seven-day window from acknowledgement, and to the final ten per cent balance receipt post Section 54(5) verification, so the finance team can size the working-capital gap between accrued refund and cash receipt at the plant and network level.

### Section 9(5) CGST Deemed Supplier — Cloud Kitchen FMCG Bridge

Source: https://www.terra-insight.com/insights/section-9-5-cgst-cloud-kitchen-fmcg-bridge/

- **Problem:** FMCG manufacturers supplying ingredients into cloud-kitchen brands that operate on Swiggy and Zomato are frequently confused about whether their B2B ingredient supply attracts Section 9(5) CGST deemed-supplier mechanics or stays under normal Section 9(1) forward charge. The confusion compounds when the same brand also sells packaged consumer products through Blinkit, Zepto, or Instamart where Section 52 TCS at 0.5% applies. Wrong classification breaks the GSTR-1 cycle in two ways — over-classification as Section 9(5) skips legitimate ITC on the supply leg, under-classification on the food-service downstream creates an ECO compliance gap, and the wrong placement in the channel-mix register distorts the trade-spend and TCS reconciliations downstream.
- **Logic:** Section 9(5) applies only to the four notified services — passenger transport (cab aggregator), housekeeping, restaurant service including cloud kitchen, and accommodation under specified tariff. The deeming binds the e-commerce operator as the legal supplier of that service. FMCG goods sold AS INPUTS to any Section 9(5) service stay under Section 9(1) at the ingredient HSN. FMCG goods sold AS PACKAGED CONSUMER PRODUCTS through an ECO platform are Section 9(1) supplies on which the ECO collects 0.5% TCS under Section 52 (rate effective 10 July 2024 per Notification 15/2024-CT). The classification logic walks the supply leg-by-leg: (a) is the leg a notified service? (b) is the leg a goods supply through an ECO? (c) is the goods buyer a downstream business that will use the goods as input to a Section 9(5) service? Each leg gets its own classification flag and feeds the appropriate GSTR-1, GSTR-3B, and ECO reconciliation track.
- **Config:** Customer master with GSTIN, customer-type flag (cloud-kitchen B2B / restaurant B2B / FMCG distributor / modern trade / quick-commerce ECO / direct consumer), and ECO platform identifier where applicable; SKU master with HSN, current GST rate post-22-September 2025, and consumer-product versus ingredient classification; channel-mix register splitting B2B ingredient supplies (Section 9(1) only) from quick-commerce ECO supplies (Section 9(1) plus Section 52 TCS 0.5%) from any Section 9(5) deemed-supplier exposure (none for the FMCG manufacturer); contract-manufacturing flag for private-label runs that trigger Section 393(1) Sl. 4 TDS at 1% (Individual/HUF, code 1001) or 2% (other resident, code 1023); GSTR-2X reconciliation feed from each ECO for TCS credit claims.
- **Output:** A monthly channel-classification register reconciling outward supplies to GSTR-1 by classification: Section 9(1) B2B ingredient supplies (to cloud kitchens, restaurants, foodservice operators), Section 9(1) FMCG goods through quick-commerce with Section 52 TCS reconciled separately, Section 9(1) general-trade and modern-trade flows. A separate watch-list flagging any Section 9(5) exposure (the FMCG manufacturer has none, but contract-manufacturing or co-pack arrangements with downstream restaurant brands require a check). Variance reports surface mis-classified invoices and feed the GSTR-1 amendment cycle and the Section 52 TCS credit claim in GSTR-2X.

### Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify

Source: https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india/

- **Problem:** Reconciliation platforms ingest the single most sensitive combination of Indian enterprise data — bank MT940 feeds, TDS certificates, GSTR-2B exports, payment gateway settlements — but generic SaaS security checklists miss India's sector-specific obligations under RBI Master Directions, SEBI cloud framework, IRDAI cyber guidelines, and DPDP Act 2023.
- **Logic:** Apply a 10-point India-specific security checklist: ISO 27001:2022 with scope including the reconciliation application, AWS Mumbai residency evidence, tamper-evident audit trail with user attribution and timestamps, role-based access with least-privilege design, CERT-In empanelled penetration testing annually, DPDP Act data processing agreement, data-in-transit and data-at-rest encryption, key management posture, incident response SLA, and sector-specific alignment where applicable.
- **Config:** Security due-diligence pack comprising ISO 27001:2022 scope letter, AWS ap-south-1 region configuration, pen-test report summary under NDA, DPDP Act DPA template, RBI/SEBI/IRDAI alignment notes per the buyer's sector, and a sample audit trail export demonstrating immutability.
- **Output:** A complete security-evidence file that survives CISO review, internal audit committee scrutiny, and sector-regulator inspection — before go-live, not after the first incident.

### SEIS Textile Services Export Reconciliation

Source: https://www.terra-insight.com/insights/seis-textile-services-export-reconciliation/

- **Problem:** An Indian textile design house or technical service exporter that historically claimed SEIS for pre-31-March-2021 service exports carries a persistent legacy reconciliation load — matching every FIRC-realised service invoice to the ANF 3B DGFT filing, tracking every duty credit scrip issued against every subsequent ICEGATE Bill of Entry where the scrip was tendered against customs duty, and closing residual scrip balance to the DGFT scrip-status portal. Scrips lapsed unnoticed against the 24-month validity clock, mis-tendered against non-eligible duty heads, or lost in inter-branch handovers surface at DGFT scrutiny audit or at the exporter's own statutory audit. SEIS is no longer accruing new entitlements, but the reconciliation load does not close until the last scrip is either fully utilised or lapsed and the DGFT audit window on the vintage claim closes.
- **Logic:** Build a legacy SEIS register keyed by claim vintage (FY 2019-20 and FY 2020-21 typically), and for each claim vintage carry the ANF 3B invoice list, the corresponding FIRC set, the CA-certified Net Foreign Exchange computation, the DGFT scrip issuance record, and the running scrip utilisation ledger. Run three keyed matches per vintage: invoice to FIRC (buyer, currency, amount, settlement date); FIRC to ANF 3B (invoice reference, INR equivalent, claim period boundaries); and ANF 3B claim value to scrip face value (Net Foreign Exchange × notified reward percentage). Track every scrip against a 24-month validity clock with alerts at 21, 22 and 23 months. For each utilisation event, ingest the ICEGATE Bill of Entry, verify duty-head eligibility, reduce the running scrip balance and record the residual. Reconcile the residual balance to the DGFT scrip-status portal monthly.
- **Config:** Legacy SEIS claim master with claim vintage FY, ANF 3B application reference, filing date, notified service heads claimed, and reward percentage applied per head. FIRC master keyed by FIRC number, authorised dealer bank branch code, foreign currency, foreign amount, INR equivalent, settlement date, purpose code, and remitting party. Service invoice master keyed by invoice number, invoice date, foreign buyer, service head, foreign currency amount, INR equivalent at invoice date, and settlement status. Scrip master keyed by DGFT scrip number, face value, date of issue, expiry date, transferred-out flag with transferee IEC if applicable, and running balance. Bill of Entry utilisation ledger keyed by BE number, ICEGATE date, port, scrip reference tendered, duty head against which scrip was tendered, and residual scrip balance after the event.
- **Output:** A vintage-wise SEIS legacy reconciliation pack: ANF 3B invoice list against FIRC set with three-match status per invoice; running scrip balance per scrip issued to the exporter with utilisation trail and expiry alerts; reconciliation of internal scrip balance to DGFT scrip-status portal; any invoice-to-FIRC mismatches flagged for internal audit trail (past claim windows are closed but the audit position must be reconciled); any FIRC-to-ANF 3B mismatches flagged as over-claim exposures pending DGFT scrutiny; and the residual utilisable scrip inventory tallied against pending Bill of Entry pipelines so the exporter can plan customs-duty tenders before the 24-month validity clock expires.

### Service Apartment and Extended-Stay Reconciliation in India

Source: https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india/

- **Problem:** A service apartment or extended-stay property — Oakwood, Saffronstays, Tata Tribute Living, Lemon Tree Service Apartments, Olive by Embassy — runs a billing model that does not look like a transient hotel. Stays of 30 days or more are often classified as renting of immovable property for GST, security deposits sit outside revenue as a refundable liability, the recurring monthly invoice cycle generates multiple bank credits per booking, and corporate guests (60 to 80 percent of revenue) deduct TDS under Section 393(1) Sl. 2(ii).D(b) payment code 1009 of the new Income Tax Act 2025 — the rent code that replaced legacy Section 194I — rather than at a hotel-services code. Manual reconciliation across the recurring-billing register, the deposit ledger, the F&B ledger, and the corporate TDS certificates rarely classifies each line correctly.
- **Logic:** Ingest the booking record with stay-length and contract-shape flags, the monthly recurring invoice register, the security deposit ledger, the F&B and auxiliary services ledger, the bank statement, and the corporate TDS certificates. Match each monthly NEFT or card receipt to its booking ID and its monthly invoice. Decompose every settlement into RENT_LINE (or HOTEL_ACCOMMODATION where stay length and contract do not qualify), F_B_REVENUE, AUX_SERVICES, DEPOSIT_RECEIVED, DEPOSIT_REFUNDED, DEPOSIT_FORFEITURE, and CORPORATE_TDS_RENT (Section 393(1) Sl. 2(ii).D(b), code 1009). Track the deposit as a balance-sheet liability and only recognise revenue against the rent and add-on lines.
- **Config:** Stay-length threshold and contract-shape flag for the rent vs hotel-accommodation classification, security deposit ledger account mapping, recurring-invoice schedule per booking with the monthly cycle date, F&B GST classification flag inherited from the property's room tariff slab, corporate TDS rate map keyed to Section 393(1) Sl. 2(ii).D(b) payment code 1009 (rent), and CORPORATE_TDS_RENT reconciliation against the property's TAN in Form 26AS-equivalent.
- **Output:** A reconciled view per booking that shows the recurring monthly rent line classified correctly for GST, F&B and auxiliary services tagged at their own rates, the security deposit tracked as a liability with refund or forfeiture events linked, every corporate NEFT matched to its monthly invoice with CORPORATE_TDS_RENT typed against payment code 1009, and a clean closing entry when the resident checks out — all backed by an audit-grade evidence trail.

### Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching

Source: https://www.terra-insight.com/insights/shopify-india-gst-reconciliation/

- **Problem:** Shopify India stores collect a single GST percentage per order but must file GSTR-1 with a CGST+SGST vs IGST split derived from each order's ship-to state under IGST Act Section 10 — while gateway payouts from Razorpay, PayU, or Cashfree arrive net of MDR, GST on MDR, and refund reversals that do not appear in the Shopify order export.
- **Logic:** Run a three-way match: Shopify order export (gross revenue, tax, shipping, discount), gateway settlement report (MDR, GST on MDR, refunds, payout batches), and bank credit. Derive CGST/SGST/IGST per order from ship-to state compared to seller's registered state. Gross up the gateway net to true revenue, book MDR as expense with 18% ITC, and reverse refund-period output tax against the original sale period.
- **Config:** Shopify connector pulling order, tax, and shipping lines; gateway adapters for Razorpay, PayU, Cashfree payouts; seller-state master with intra-state vs inter-state logic; composite-supply rules for shipping GST; refund-period reversal logic keyed to original sale period.
- **Output:** A GSTR-1 filing with invoice-level SGST vs IGST split matching the ship-to state rule, a reconciled gateway payout with MDR ITC claimable, and refund reversals applied to the correct period — with no place-of-supply mismatches or output-tax overstatement.

### Shrimp Aquaculture MPEDA Export Reconciliation India Cornerstone

Source: https://www.terra-insight.com/insights/shrimp-aquaculture-mpeda-export-reconciliation-india/

- **Problem:** A mid-sized Andhra Pradesh shrimp exporter shipping 800 MT per month of vannamei (Penaeus vannamei, whiteleg) in HOSO (Head-On Shell-On) and HLSO (Headless Shell-On) formats to the US, EU, and Japan at a weighted FOB average of USD 6,500 per MT — approximately Rs 5.4 crore of monthly export realisation — must reconcile MPEDA RCMC and Aquaculture Authorisation for every contracted farm, EIC pre-shipment antibiotic-residue lab certification per shipment lot, Section 54(3) zero-rated refund on Rs 22 to 28 lakh of accumulated feed (5 percent GST), packaging (18 percent), power (18 percent), and cold-chain (18 percent) ITC every tax period, RoDTEP scrip claim at the HSN 0306 rate per shipping bill FOB, e-BRC realisation within the FEMA nine-month window, and fx-variance GL treatment under Ind AS 21. A break at any hop — a missing sampling reference on the EIC certificate, a mis-classified ITC entry, an unreconciled shipping bill beyond 270 days — cascades into a MPEDA remedial audit, a USFDA import alert, a Section 54(3) refund rejection, or a FEMA contravention exposure.
- **Logic:** Build a farm-to-shipping-bill traceability spine keyed to the MPEDA farmer ID and the CAA farm registration, carrying the procurement lot through the processing plant lot number, the freezer batch, the pre-shipment sampling reference, the NABL EIA lab report number, the EIC export health certificate serial, and finally the shipping bill number filed at ICEGATE. Extract the shipping bill register for the period with FOB USD and INR values, LUT reference, and RoDTEP election. Match every export invoice against the corresponding shipping bill and the EGM at ICEGATE, and prepare the RFD-01 refund base under Rule 89(4) with the correct Net ITC (inputs and input services during the period, excluding sub-rule 4A/4B claims). Feed the RoDTEP claim register from the shipping bills that elected RoDTEP and reconcile the e-scrip credit at ICEGATE against expected scrip value (FOB × Appendix 4R rate). Ingest the e-BRC from the DGFT server keyed to SB number, compute realised INR at the AD bank credit rate net of charges, book the fx-variance to the dedicated forex GL under Ind AS 21, and age unreconciled shipping bills against the FEMA nine-month clock with escalations to the AD bank at 180 days and to the finance leadership at 270 days.
- **Config:** Farmer master with MPEDA farmer ID, CAA farm registration, farm survey number, tank area, water source, and effluent treatment reference; hatchery master with CAA authorisation number, SPF broodstock source, and lot lineage; feed supplier master with GSTIN, HSN 2309, 5 percent GST rate, and Section 43B(h) MSME flag; processing plant master with EIA plant approval number and processing lot numbering rule; sampling master with pre-shipment sampling reference format keyed to freezer batch; EIA lab master with NABL accreditation reference and analyte panel (chloramphenicol nil, nitrofurans nil, tetracyclines 100 ppb, sulphonamides USFDA-listed); Export Health Certificate serial series from the regional EIA; shipping bill register with SB number, date, ICEGATE reference, FOB USD/INR, LUT reference, RoDTEP election flag, and Drawback flag (mutually exclusive on RoDTEP); RoDTEP rate schedule from Appendix 4R keyed by HSN 0306 sub-heading; AD bank master for e-BRC upload and realisation tracking; fx-variance GL under Ind AS 21 with favourable and unfavourable buckets; and monthly RFD-01 reconciliation workbook keyed to the tax period.
- **Output:** A monthly export reconciliation pack: MPEDA and CAA compliance status across every contracted farm with traceability gaps flagged; EIC per-shipment sampling and lab certificate register with any non-compliance surfaced for rework or destroy; shipping bill register with RoDTEP and Drawback election status and scrip realisation reconciled against ICEGATE credit; Section 54(3) refund draft on Form RFD-01 with Rule 89(4) formula application, LUT reference, and export invoice ledger; e-BRC realisation register with fx-variance booked to Ind AS 21 GL and ageing report against the FEMA nine-month clock with 180-day and 270-day escalations; feed ITC and packaging ITC register at 5 percent and 18 percent respectively, keyed to tax period for the RFD-01 Net ITC computation. Year-end pack rolls up USFDA facility inspection readiness with the full farm-to-shipping-bill traceability spine reproducible on 24-hour notice.

### 10 Signs Your Reconciliation Process Is Broken

Source: https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india/

- **Problem:** A broken reconciliation process shows up as close cycles longer than 7 working days, recurring GSTR-2B mismatch notices, weekend work during month-end, suspense balances above ₹1 lakh persisting beyond 10 days, and repeated audit qualifications.
- **Logic:** Run a structured diagnostic against ten indicators: close duration, notice count, weekend work, suspense ageing, TDS mismatch volume, GSTR-2B exceptions, prior-month carry-forward, audit observations, spreadsheet-only trail, and turnover attributable to reconciliation work. Treat any three red flags as systemic, not ad hoc.
- **Config:** KPIs with thresholds (close ≤5 days, suspense ≤ ₹1 lakh for ≤10 days, zero avoidable notices), SLA-tracked exception queue, and a documented escalation path for each indicator.
- **Output:** A monthly diagnostic report that lets the CFO see whether the process is drifting toward audit risk, so intervention happens before the next statutory audit or GST scrutiny.

### Skylark Hatcheries Feed Formulation Reconciliation and FCR Metrics

Source: https://www.terra-insight.com/insights/skylark-hatcheries-feed-formulation-reconciliation-fcr/

- **Problem:** A broiler feed integrator running a 45-day contract-farming cycle across a Namakkal and Coimbatore catchment must reconcile the batch feed cost of a three-phase pre-starter, starter, and finisher formulation against per-cycle bird-lift, actual Feed Conversion Ratio against a contract FCR baseline of 1.65, the mortality register against the 10 percent standard allowance with 50/50 sharing of excess mortality, Section 143 CGST job-work provisions on the feed and chick dispatch to the grower, Section 194C code 1023 versus 1024 TDS classification at the per-bird growing-charge settlement, and Section 43B(h) MSME 45-day payment discipline on premix, methionine, and lysine additive suppliers. Manual reconciliation across the feed mill, the grower-network dispatch schedule, the daily mortality register, the ITC-04 filing, and the monthly grower settlement loses feed-cost variance attribution, mis-classifies TDS at the settlement run, and exposes the integrator to a Section 143(3) year-end disallowance on the MSME creditor line and a Section 65 GST audit exposure on the ITC-04 shortfall.
- **Logic:** Build a batch feed cost register keyed on the mill batch number with the ingredient composition and cost of each phase (pre-starter, starter, finisher), the throughput volume per phase, and the aggregate per-kg feed cost derived from the ingredient mix (maize, soya DOC, fishmeal, oil, mineral premix, methionine, lysine). Ingest the grower-network dispatch schedule with the feed truck manifest per grower per phase and the corresponding day-old chick placement count. Maintain a daily mortality register per grower keyed to the chick placement date and reconcile the cumulative mortality against the 10 percent allowance at lift. Compute actual FCR at lift as (aggregate feed dispatched to the grower during the cycle) divided by (live-weight aggregate of birds lifted at cycle close), and match against the contract baseline of 1.65 to derive the efficiency bonus or FCR chargeback. Key the per-bird growing charge to Section 8 Sl. 4 code 1023 (material supplied by principal) for TDS deduction at the settlement run; deduct on the labour component only. Extract the Section 143 dispatch-and-return register into Form ITC-04 for the quarterly filing. Flag every premix, methionine, and lysine supplier with MSME status on the supplier master and honour the 45-day payment discipline to avoid Section 43B(h) year-end disallowance.
- **Config:** Feed mill master with batch number, phase (pre-starter, starter, finisher), ingredient composition (maize percent, soya DOC percent, fishmeal percent, oil percent, mineral premix percent, methionine plus lysine percent), per-ingredient cost per kg, and derived batch-weighted feed cost per kg; grower master with grower code, PAN, GSTIN (typically not applicable at grower scale), Individual/HUF or non-Individual/HUF status for TDS code selection, TDS payment code 1023 (material supplied), and per-bird growing-charge slab; contract FCR baseline schedule (1.65 target, tolerance band, efficiency bonus curve per 0.05 FCR deviation, chargeback rate at marginal feed cost); mortality allowance schedule (10 percent standard, 50/50 sharing above); day-old chick placement register per grower per placement date; feed dispatch register per grower per phase; daily mortality register per grower with cause-of-death code where available; ITC-04 register per quarter aggregating dispatch and return per grower; Section 43B(h) MSME flag on premix, methionine, lysine, and vitamin premix suppliers with 45-day due-date monitor; FSSAI feed-batch lot traceability.
- **Output:** A cycle-close broiler contract-farming reconciliation pack per grower: day-old chick placement count, phase-wise feed dispatch totals, cumulative mortality register against the 10 percent allowance with a 50/50 sharing computation above the threshold, actual FCR computed against the 1.65 contract baseline with efficiency bonus or chargeback, per-bird growing charge derived on the labour component only, Section 8 Sl. 4 code 1023 TDS at 2 percent on the growing charge reconciled against the integrator's TDS remittance schedule, ITC-04 draft for the quarter reconciling feed and chick dispatch against grown-bird return within the Section 143 one-year timeline, and — at the batch level — a feed-cost variance report attributing per-kg cost movement to specific ingredient price changes (maize procurement rate, soya DOC landed cost, fishmeal cost, oil cost). Per-supplier MSME payment status monitor supports Section 43B(h) year-end deduction defence.

### Affordable Housing 1% GST vs Non-Affordable 5%: Boundary Conditions

Source: https://www.terra-insight.com/insights/slum-rehab-affordable-housing-gst-1-percent-cgst-real-estate-india/

- **Problem:** An Indian real estate developer selling residential apartments must apply either 1% GST (affordable housing under Notification 3/2019-CTR — carpet area ≤ 60 sq m metro / 90 sq m non-metro AND gross amount ≤ ₹45 lakh) or 5% GST (non-affordable) with a strict no-ITC condition under Section 17(5), while SRA and PMAY-CLSS projects also qualify for 1% irrespective of the general limits — and a single flat that breaches either boundary by a small margin jumps 5× in GST liability, exposing the developer to reclassification if the carpet-area register, agreement value and GSTR-1 filing do not reconcile.
- **Logic:** For every registered flat, capture RERA carpet area (net usable floor area per Section 2(k), excluding balconies and shafts) and gross amount charged (agreement value inclusive of preferential location, car parking and one-time deposits) at the moment of booking; test both against the metro/non-metro carpet limit and the ₹45 lakh value limit; classify the flat as affordable (1%) or non-affordable (5%) and lock the classification in the flat master; apply the classification consistently across every milestone invoice; block all input tax credit on real-estate inputs against real-estate output; and reconcile the per-flat classification against GSTR-1 line-items and against the RERA-registered carpet area at every quarter.
- **Config:** Flat master keyed by RERA registration + tower + flat number with RERA carpet area in sq m, agreement value in ₹, metro/non-metro city classification, SRA/PMAY-CLSS flag, affordable/non-affordable classification and locked GST rate; boundary rule engine that applies Notification 3/2019-CTR conditions and flags flats within ±5% of either limit for review; invoice engine that reads the classification from flat master and forces 1% or 5% on every milestone invoice; ITC blocking rule at project level with real-estate output tag; GSTR-1 line-item reconciliation to flat-master classification; RERA carpet-area cross-check at quarter close.
- **Output:** A per-flat GST classification register with RERA carpet area, agreement value, metro/non-metro flag, SRA/PMAY-CLSS flag, resulting classification and applicable rate, and a boundary-proximity flag on flats within ±5% of either affordability limit; a monthly reconciliation of invoice GST rates to classification with drift alerts; a per-project blocked-ITC register showing input GST claimed vs blocked; a quarterly GSTR-1 vs flat-master classification tie-out; an audit-ready evidence trail per flat linking carpet-area certificate, agreement, invoice and GSTR-1 line-item.

### Slab Discount Distributor Claim Recovery for FMCG

Source: https://www.terra-insight.com/insights/slab-discount-distributor-claim-recovery-fmcg/

- **Problem:** Indian FMCG distributor agreements run on monthly and quarterly volume slabs — 5% off below slab 3, 8% off at slab 3, 12% off at slab 4 — and the brand accrues the trade-spend liability every period, but the distributor's claim arrives weeks late, against a slab number that the brand's primary-sales engine does not agree with, and the GST treatment splits across Section 15(2)(a) for invoice-time discount and Section 15(3)(b) for retro slab credit notes. Without a reconciled slab master, a versioned distributor master, and a tight invoice-level discount audit, the brand either over-pays a tier it did not owe or under-recovers GST on a tier it did.
- **Logic:** Maintain a slab master per scheme per period with thresholds (cases or ₹), tier rate and effective dates; reconcile distributor self-report (secondary sales from DMS) against primary-sales achievement (manufacturer to CFA) and surface the stock-in-trade gap; for each distributor-month, recompute slab achieved on primary basis, compare to the slab tier applied in the invoice-level discount line and to the slab tier on which the claim was approved, and flag any three-way break; for retro slab credit notes, validate the Section 15(3)(b) triple-test (prior agreement, invoice-linkage, ITC reversal by recipient) before treating as GST-reducing.
- **Config:** Slab master with scheme code, period type (monthly/quarterly), tier thresholds in cases or ₹, tier rate %, effective from/to; distributor master with GSTIN, PAN, hierarchy (super-stockist / CFA / sub-stockist), and scheme eligibility flags; invoice-level discount field with scheme code, slab tier applied and the underlying achievement value; claim register with distributor-period-scheme key, claim amount, slab tier claimed and approval status; Section 15(2)(a) / 15(3)(b) treatment rule per scheme to drive GSTR-1 credit-note posting; monthly ageing buckets on stuck claims.
- **Output:** A month-end slab-discount reconciliation pack per distributor-scheme — primary-sales-based slab achieved versus claim-approved slab versus invoice-applied discount tier, a three-way break register with rupee impact, a Section 15(3)(b) eligibility check on every retro credit note with the prior-agreement / invoice-linkage / ITC-reversal flag, a stuck-claim ageing report, and the GSTR-1 credit-note line list ready for the next return cycle.

### Society Maintenance Charge Reconciliation: GST, Late-Fee, and Accounting under Section 22A

Source: https://www.terra-insight.com/insights/society-maintenance-charge-reconciliation-india/

- **Problem:** A housing society with 240 flats and ₹14,000 average monthly maintenance per flat — placing it above the ₹7,500 GST exemption threshold — must run a per-flat collection ledger, GST output at 18% on the full charge (cliff design, not just the excess), late-fee accrual and waiver tracking, sinking-fund earmarking with separate corpus accounting, Section 22A mutuality income classification, and bank-side reconciliation of member-wise UPI / cheque / NEFT collections every month, without which the audit by the registered auditor and the next AGM both surface unreconciled positions.
- **Logic:** Reconcile every member receipt at flat-and-month granularity, run the ₹7,500 threshold tracker forward by flat (cliff to 18% GST if breached), accrue late-fee at the bye-law rate on overdue receivables, earmark sinking-fund collection separately at receipt, classify each income stream as member-mutual (Section 22A exempt) or non-mutual (taxable), and reconcile member receipts to bank statement by UTR for UPI and NEFT, by cheque number for cheque collections.
- **Config:** Member master keyed by flat number with member name, contact, payment instrument preference; monthly charge schedule per flat with maintenance, sinking fund and any flat-specific levy; GST status flag (above or below ₹7,500); late-fee bye-law rate; income stream classification table (mutual vs non-mutual); bank statement ingestion for member receipt reconciliation.
- **Output:** A monthly close pack showing per-flat receipt status (paid / overdue / late-fee accrued), GST output on taxable charges, sinking-fund corpus position, mutual vs non-mutual income split for the period, and a member-by-member ageing for the managing committee; an annual ITR computation under Section 22A with the income classification breakdown; an audit-ready evidence file for the statutory auditor with bank reconciliation by member.

### Solar Rooftop Net-Metering Reconciliation for Indian C&I Customers

Source: https://www.terra-insight.com/insights/solar-rooftop-net-metering-reconciliation-india/

- **Problem:** Indian C&I customers running 100 kWp to 5 MWp rooftop solar plants under net-metering face a structural reconciliation gap — bi-directional meter reads from a single energy meter must be split into import and export legs and matched against the monthly DISCOM net-metering bill, banked units must be carried forward and aged month by month for APPC settlement at year-end, GST on PV modules under Notification 8/2021 sits at a different rate to inverter and BOS at 18% with works-contract treatment for EPC services, Section 32 accelerated depreciation under the Income Tax Act 2025 drives a book-vs-tax deferred-tax computation, and state-specific electricity duty plus cross-subsidy surcharge on the net import line break single-tariff journal entries.
- **Logic:** Reconcile bi-directional meter export and import registers against the DISCOM bill's net-metering line per month, maintain a running banked-units ledger with monthly accrual and drawdown ageing for APPC settlement at FY close, split each capital invoice into PV-module Notification 8/2021 line plus inverter and BOS at 18% plus EPC works-contract for ITC eligibility and fixed-asset cost capture, run book straight-line vs tax WDV renewable-block plus 32(1)(iia) additional depreciation parallel ledgers for deferred-tax tracking, and decompose the bill into energy charge plus demand charge plus electricity duty plus cross-subsidy surcharge for state-specific GL classification.
- **Config:** Bi-directional meter master keyed by meter serial with import and export register identifiers, DISCOM consumer master with category, contracted demand, tariff schedule and metering regime (gross/net/net-billing), banking ledger with monthly opening, accrual, drawdown and ageing buckets, APPC schedule table by DISCOM by financial year, GST treatment table for PV modules (Notification 8/2021 effective Oct 2021), inverter and BOS (18%) and EPC works-contract, fixed-asset register with book SLM useful life and tax WDV renewable-block rate plus first-year additional flag, and electricity-duty and cross-subsidy surcharge rate table by state by consumer category.
- **Output:** A monthly reconciled view per plant showing meter-read export and import vs bill export and import with variances flagged, banked-units running balance with monthly ageing and projected APPC settlement value at FY close, ITC on capital and EPC invoices split by GST treatment with the capitalised tax-inclusive cost feeding the FAR, parallel book and tax depreciation ledgers feeding the deferred-tax liability, and a decomposed bill ledger feeding separate GL lines for energy charge, demand charge, duty, surcharge and net payable that ties to the bank debit on the DISCOM payment date.

### Sorting Back-Charges from OEMs: How Indian Auto Suppliers Account for Them

Source: https://www.terra-insight.com/insights/sorting-back-charge-oem-accounting-auto-india/

- **Problem:** Indian Tier-1 auto-component suppliers face OEM sorting back-charges when defective parts are mixed into a dispatched batch and the OEM deploys a third-party sorting agency at the plant. Rates run ₹4-8 per part for visual sort, ₹15-25 per part for functional sort, ₹40-60 for NDT or X-ray sort. The OEM bills the supplier the sorting cost plus 18% GST. The supplier accounts for the principal as quality cost, claims 18% GST as ITC, and must reconcile the back-charge against the sorting agency report and the underlying dispatch invoice.
- **Logic:** On each sorting back-charge posting, link to the OEM's quality-incident report and the sorting agency report (defect count, sort hours, rate applied), validate against the contractual sort rate from the quality manual or MSA addendum, classify as accepted or contested based on defect attribution and sort-scope appropriateness, post the principal to quality cost centre, claim the 18% GST as ITC subject to GSTR-2B reflection and Rule 37 payment timing, and trigger Tier-2 passthrough back-charge where the defect is sub-vendor attributable.
- **Config:** OEM sort-rate matrix by sort type (visual / functional / NDT) and OEM customer, sorting back-charge register linking each back-charge to the source dispatch invoice via OEM quality-incident report, GST ITC tracking workflow with GSTR-2B match check, Rule 37 180-day payment-timing flag for ITC eligibility, contest queue with defect attribution and sort-scope tracks, Resident Quality Engineer monthly-fee subscription register where applicable.
- **Output:** A sorting back-charge ledger per OEM showing each back-charge with sort type, defect count, rate applied, principal, GST, ITC eligibility status, and contest status. A GST ITC reconciliation against GSTR-2B for sorting back-charges. An RQE monthly cost dashboard where applicable. A Tier-2 passthrough debit queue for sub-vendor-attributable sort events.

### SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove

Source: https://www.terra-insight.com/insights/sox-compliance-reconciliation-india/

- **Problem:** Indian subsidiaries of US-listed parents sit inside both SOX Section 404 (PCAOB AS 2201) and ICFR Section 143(3)(i), with material-subsidiary scope at 5% of consolidated revenue or assets. SOX demands quarterly CEO/CFO sub-certifications while ICFR is annual — reconciliation key controls (bank, intercompany, GSTR-2B, Form 26AS, payroll gross-to-net) are tested under both.
- **Logic:** Each reconciliation is documented as a SOX Key Control with assertion mapping (existence, completeness, accuracy, valuation, rights, presentation). Testing runs dual-purpose under PCAOB AS 2201: preparer plus reviewer plus sign-off-date verified for 30-80 key controls, with exception tracking aligned to material-weakness thresholds. The same controls are cross-referenced to ICAI SA 610 evidence for ICFR reporting to minimise duplicate testing.
- **Config:** Key Control register mapped to financial-statement assertions, quarterly sub-certification cadence, PCAOB plus ICAI evidence-vault integration, and US-IST sign-off timing rules.
- **Output:** Quarterly SOX sub-certification evidence pack, annual ICFR operating-effectiveness testing output, material-weakness tracker with remediation plan, and dual-framework audit trail for parent 10-K plus Indian Board Report.

### Spencer's Retail FMCG Settlement Reconciliation (RPSG)

Source: https://www.terra-insight.com/insights/spencer-retail-fmcg-settlement-rpsg/

- **Problem:** FMCG suppliers ship to individual Spencer's Retail store warehouses across the RPSG Group footprint but receive a single consolidated remittance from RPSG Group's central payables entity on a T+10 to T+14 cycle, with deductions that include per-SKU per-quarter listing fees, BTL gondola end-cap reimbursement offsets, and an optional prompt-payment discount. The settlement file consolidates dispatches from multiple stores into one net remittance, breakages and damages flow through return-to-vendor debit notes, and the Section 15(2) CGST treatment differs line by line — some deductions are Spencer's service invoices to the supplier (input credit available), others are Section 15(2) post-supply discounts (value reduction with credit note), and others sit as non-qualifying marketing expense. Suppliers reconciling at consolidated remittance level miss store-level and SKU-level variance, lose the GST credit-note window on the prompt-payment discount, and over-state revenue against the actual net realisation.
- **Logic:** Parse Spencer's central RPSG settlement file at three layers — the remittance summary (one row per payment cycle), the dispatch detail (one row per invoice per store warehouse with merchandise value, listing fee, BTL offset, prompt-payment discount, RTV debit), and the deduction breakdown (categorised per line type). Match each dispatch line to the supplier's outbound invoice register at invoice number plus PO number plus store warehouse code. Classify each deduction line into one of four buckets: Spencer's GST service invoice to supplier (supplier takes ITC), Section 15(2) qualifying post-supply discount (supplier issues credit note reducing taxable value), Section 15(2) non-qualifying scheme amount (supplier books as marketing expense at full GST cost), or merchandise debit (RTV, breakage, damage). Cross-foot the gross dispatch total minus categorised deductions to the net remittance received in bank, and provision any unmatched residue per CARO 2020 disclosure norms.
- **Config:** Master agreement with Spencer's Retail covering payment cycle (T+10 / T+14 / prompt-payment variant), listing fee schedule per SKU per quarter, BTL gondola end-cap rate card, RTV and damage debit rules, GSTIN of RPSG Group payables entity. Supplier outbound invoice register from SAP-SD or equivalent with invoice number, PO number, dispatch store warehouse code, merchandise line items, HSN, GST rate. Spencer's settlement file feed with remittance summary, dispatch detail, and deduction breakdown. Section 15(2) per-deduction-type treatment register flagged qualifying / non-qualifying. Pre-22-September 2025 versus post-22-September 2025 HSN rate switch for the affected categories. Form 26AS feed at supplier PAN for Section 393(1) Sl. 18 TDS reconciliation.
- **Output:** A weekly Spencer's reconciliation pack: gross dispatch value for the cycle, total per-SKU listing fee debit, total BTL gondola offset, total prompt-payment discount, total RTV and damage debit, net expected remittance, actual remittance received, residue unmatched. Per-store warehouse variance surfaces dispatches that did not settle on cycle (typically goods-received-not-acknowledged at store level). Per-SKU listing fee detail flags duplicate quarter charges (a common error when Spencer's planogram churns mid-quarter). A Section 15(2) per-deduction register feeds the GST credit-note cycle for the qualifying prompt-payment discount lines. Form 26AS reconciliation flags Spencer's commission TDS where the deductor TAN matches the RPSG Group payables entity.

### One PG Settlement Arriving as Two Bank Credits: Split Reconciliation

Source: https://www.terra-insight.com/insights/split-settlement-two-bank-credits-streaming-payment-gateway-india/

- **Problem:** Payment gateways in India occasionally settle a single confirmed amount as two bank credits — driven by NEFT/RTGS batching, high-value thresholds, or internal treasury logic at the PG's nodal bank. Reconciliation systems that match one PG settlement to one bank credit either flag a duplicate credit (double-counting revenue), raise a missing-second-half alarm (blocking closure), or lose the linkage between the two halves. The problem is more visible in subscription-heavy sectors — streaming, SaaS, edtech — where large monthly settlements often cross the RTGS threshold and split across rails within a 30-minute window.
- **Logic:** Group the bank credits by PG settlement identifier or narration substring, sum the grouped credits, and match the summed amount to the single PG-expected-settlement line. Hold the first credit as partially reconciled — matched by settlement ID, unmatched by full amount — and only close the line once the sum equals the PG-file amount. Never treat a matched-by-ID, unmatched-by-amount credit as a duplicate; never treat a partial credit as a missing settlement until the T+1 window expires.
- **Config:** Group-by rule on the PG settlement_id or narration key, tolerance band on the sum vs the PG expected amount (typically zero paise), and a T+1 waiting window before escalating a partial match to missing. Separate ruleset for intentional marketplace split settlements — those are matched one-to-one, not summed.
- **Output:** Every PG settlement closed against the correct sum of one or more bank credits, with UTR-level traceability from PG settlement ID to each bank credit. No duplicate revenue booked, no missing-settlement false alarms raised, and no confusion between rail-split settlements and intentional marketplace splits.

### Stamp Duty, Registration Fee, and GST: Three Separate Reconciliation Trails

Source: https://www.terra-insight.com/insights/stamp-duty-registration-real-estate-reconciliation-india/

- **Problem:** A buyer purchasing a flat from an Indian developer pays three distinct charges at registration — state stamp duty (typically 3-7%, varying by state, by property attributes and often by buyer gender), state registration fee (typically 1%), and central GST (5% non-affordable / 1% affordable / nil post-CC) — each collected on a separate rail with a separate receipt, none refundable once the deed is registered, and each requiring a discrete reconciliation trail against the sale deed line-items and against the Form 26AS 1% TDS credit under Section 393(1) Sl. 3(i) code 1010.
- **Logic:** Tie each of the four charge line-items on the sale deed to its external evidence: deed stamp-duty line to state stamp-portal receipt (GRAS / K-KAVERI / DORIS); deed registration-fee line to sub-registrar receipt (IGR / IGRSY); deed GST line to the developer's tax invoice under Section 31 CGST with GSTIN and correct rate (5% or 1%); Form 26AS TDS credit to the buyer's 1% Form 26QB challan. Confirm the deed value equals the higher of consideration or the state ready-reckoner / guidance / circle rate.
- **Config:** Sale deed master with agreement value, ready reckoner value, stamp duty amount, registration fee, GST amount, GSTIN of developer, CC date if applicable; state stamp portal receipt ingestion (GRAS, K-KAVERI, DORIS); sub-registrar receipt ingestion; developer GST tax invoice ingestion; Form 26QB challan register; Form 26AS credit ingestion for the buyer's PAN. Per-state stamp duty rate table with women concession flag and Metro-cess flag.
- **Output:** A per-unit reconciliation pack tying the sale deed line-items to four independent external receipts (state stamp portal, sub-registrar, developer GST invoice, TDS challan) with variance flags where any line-item disagrees with its external evidence; a per-state stamp duty rate calculation trace showing the rate applied, the base value (deed vs ready reckoner), and the resulting stamp duty owed vs paid; an audit-ready evidence trail per unit that any future resale title-diligence can consume in minutes.

### Stamping and Pressing Process Reconciliation for Indian Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/stamping-pressing-process-reconciliation-auto-india/

- **Problem:** An Indian Tier-1 stamping supplier running multiple press lines across 300- to 3,000-tonne mechanical and hydraulic tonnage classes must reconcile coil-weight inbound to part-weight outbound across five discrete process stages (blanking, drawing, forming, trimming, piercing), against contracted yield norms per part and per OEM, with die-set life tracking 800,000 to 1.2 million strokes, raw-material price-variance pass-through on tonnage-rate contracts, free-issue steel held memorandum-only under Rule 55 on the Section 143 job-work rail with no GST on the inbound dispatch, conversion-charge GST at 18% under HSN 9988, and Section 394 TCS at 1% under payment code 1071 on retain-and-sell of skeleton and trim scrap to external dealers.
- **Logic:** Maintain per-press-line and per-die-set master data of theoretical part weight, tonnage class, contracted conversion rate, die-stroke counter and refurbishment trigger. Per coil, log inbound free-issue weight (Rule 55 challan) and per shift log press-line throughput, dispatched part count, theoretical part weight × dispatched count, skeleton-scrap weighbridge, trim-scrap weighbridge, piercing-slug weighbridge and set-up scrap. Close the yield identity per coil and per shift; flag drift in dispatched part weight as die-wear signal; bill the conversion invoice at the contracted tonnage-class rate with 18% GST under HSN 9988; net scrap-credit on retain-and-sell at the contracted scrap price and collect Section 394 TCS code 1071 from the external dealer.
- **Config:** Press-line master with tonnage class, installed kilowatt rating and depreciation schedule; per-part master with theoretical weight, contracted yield norm, contracted process-loss tolerance per grade; die-set register with stroke counter, refurbishment trigger and rebuild log; coil-heat-traceable memorandum FI ledger per OEM per grade per coil under Rule 55; tonnage-rate conversion-rate matrix by press line; RMPV reference-index master (JPC HRC, JSW / Tata mill list) on owned-steel contracts; scrap-category master with per-category price; Section 394 TCS code 1071 buyer master for external scrap dealers.
- **Output:** A monthly press-line reconciliation statement closing the coil-to-part identity per coil, per shift and per part number across blanking, drawing, forming, trimming and piercing; die-wear drift flags ranked by adverse part-weight variance; a tonnage-class conversion invoice at contracted rates with 18% GST under HSN 9988 and Rule 55 challan cross-reference; scrap-credit netting record at agreed per-category prices; Section 394 TCS code 1071 register on external scrap sales reconciled to Form 27EQ; and an audit-ready memorandum FI ledger that ties to physical stock at any OEM-initiated count.

### Star Bazaar / Trent FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/star-bazaar-trent-fmcg-settlement/

- **Problem:** Star Bazaar / Trent Hypermarket settlement files arrive weekly or fortnightly with per-SKU per-store gross-sales lines, contracted margin, central scheme reimbursement, BTL allocation, and deductions for returns and damage — spread across the full Trent Hypermarket store network. The supplier's dispatch register lives in SAP or its DMS, the scheme master in the TPM tool, and the BTL approval log in a separate spreadsheet. When the supplier is a Tata-group brand like Tata Consumer's Tata Sampann, every line attracts an additional Section 92 / 92BA arms-length-pricing test because Trent and Tata Consumer are associated enterprises under common Tata Sons control. Mis-classified scheme lines, GSTIN mis-mapping across the two corporate GST footprints, and missing per-SKU TP benchmarking create both ITC blockages on Trent's side and transfer-pricing documentation gaps on Tata Sampann's side that surface at year-end audit.
- **Logic:** Parse each Star Bazaar settlement file into five streams — gross sales by SKU by store, margin / markdown, central scheme reimbursement, BTL allocation, deductions. Match the gross-sales stream to Tata Sampann's dispatch register by GSTIN-pair, SKU, store-DC mapping, and dispatch date. Classify each scheme line for Section 15(2) CGST treatment (invoice-recorded, post-supply qualifying, post-supply non-qualifying). For Tata-group intra-house flows, additionally tag each SKU line with a comparable arms-length benchmark drawn from Tata Sampann's non-Tata modern-trade settlements with DMart, Reliance Smart, and More Retail. Run ageing buckets — 0-14 / 15-30 / 31-60 / 60+ days from settlement file date — and surface any 60-plus intra-group items separately for related-party-disclosure flagging. Cross-foot the net receivable against the Trade Receivables GL line for the Trent legal entity and the Tata-group eliminations register before each month-end close.
- **Config:** Trent state-GSTIN master for Star Bazaar receiving entities (state-wise under Trent Hypermarket Private Limited); Tata Sampann state-GSTIN master for dispatching entities under Tata Consumer Products Limited; SKU master with HSN, GST rate (pre and post 22 September 2025 transition), MRP, and arms-length comparable price band; scheme master with code, percentage, validity dates, Section 15(2) treatment flag, and Tata-group intra-house indicator; BTL approval log with store-level allocation rules; Section 92BA threshold trigger per FY; Section 92D contemporaneous documentation template per SKU; settlement file parser with column map; ageing bucket configuration; related-party-disclosure flag for items over 60 days in the intra-group ledger.
- **Output:** A weekly Star Bazaar reconciliation pack: opening receivable, period dispatch, period settlement received (split by gross sales, margin, scheme reimbursement, BTL allocation, deductions), scheme classification by Section 15(2) treatment, intra-group items flagged for TP documentation and Ind AS 24 related-party disclosure, ageing buckets with the 60-plus universe ringfenced, and a per-SKU arms-length variance report comparing Star Bazaar prices to the brand's non-Tata modern-trade prices. The pack feeds the Trade Receivables GL, the Form 3CEB specified-domestic-transaction tagging, the GSTR-1 credit-note cycle, and the related-party-transaction note in the consolidated audit pack.

### Statutory Audit Checklist for Auto-Component Manufacturers: 47 Items for CAs

Source: https://www.terra-insight.com/insights/statutory-audit-checklist-auto-component-manufacturer-india/

- **Problem:** Statutory audit of an Indian auto-component Tier 1 has 47 reconciliation checklist items distributed across five high-risk areas — revenue (variable-consideration constraint, GRN cut-off, RMPV index formula, FOMP provision reasonableness), inventory (fixed-overhead absorption against normal capacity, abnormal-waste exclusion, free-issue steel ITC-04 four-way reconciliation, slow-moving and obsolete provision matrix), receivables (OEM debit-note exposure, short-pay decomposition by reason, ageing buckets), tax (Section 393/394 codes 1002/1071 reconciliation, GSTR-9 tie-up, Form 26AS three-way match), and capital goods (tooling Schedule II policy, Rule 43 proportional ITC reversal). A generic CARO 2020 checklist will miss all five.
- **Logic:** Risk-rate each of the 47 checklist items under SA 315 inherent risk plus control risk. Apply SA 330 substantive procedures proportionate to risk. Use SA 505 external confirmations for OEM debit-note exposure and bank balances. Use SA 540 procedures for variable-consideration estimates and slow-moving provisions. Test reconciliation evidence per item — scheduling agreement to call-off to GRN to invoice to payment for revenue; ITC-04 challan-out to challan-in to processing yield for free-issue steel; tooling-amortisation ledger to Rule 43 reversal for capital goods. Document the materiality and exception flagging per item.
- **Config:** 47-item checklist with risk rating per item, SA-reference per item (SA 315 / 330 / 500 / 505 / 540), audit procedure description per item, sample-size rule per risk band, exception threshold per item against performance materiality, OEM-master mapped to portal-data-source for substantive testing, ITC-04 quarterly filings register, Rule 43 reversal worksheet, RMPV claim register with constraint-policy tier.
- **Output:** An audit-ready 47-item checklist completed per engagement with evidence per item, risk-rated exception list with materiality flagging, working-paper file linking each tested item to its supporting reconciliation evidence and SA reference, a CARO 2020 paragraph 3 reporting matrix, and a management letter draft addressing identified internal-control weaknesses in the auto-component-specific risk areas.

### Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items

Source: https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india/

- **Problem:** Statutory auditors apply SA 320 performance materiality (typically 50-75% of 5% of PBT or 0.5% revenue benchmark) across five mandatory reconciliation areas: bank (SA 505 confirmations via DBCP), party balances, intercompany, statutory dues (TDS plus GST plus PF plus ESI), and inventory to GL. CARO 2020 Clause 3(ii)(b) adds quarterly BRS-to-bank-filed-returns reconciliation above ₹5 crore working capital.
- **Logic:** The year-end reconciliation pack is pre-built in the structure the auditor expects: BRS for every bank account, Form 26AS three-way match for TDS receivable, GSTR-1 to GSTR-3B to GSTR-9 for output tax, GSTR-2B to ITC for input tax, Rule 42/43 reversal schedule, statutory-dues aging, and intercompany confirmation matrix. Each item carries performance-materiality flagging for auditor sampling.
- **Config:** SA 320 performance-materiality threshold, SA 505 external confirmation tracker with DBCP integration where supported, CARO 2020 Clause 3(ii)(b) quarterly working-capital return matcher, and SA 330 risk-based testing rules.
- **Output:** Audit-ready reconciliation pack for 32 standard schedules, SA 505 external confirmation file, CARO 2020 working-capital reconciliation trail, and qualification-threshold alerts for items above performance materiality.

### Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View

Source: https://www.terra-insight.com/insights/statutory-payment-reconciliation-india/

- **Problem:** Indian companies make 5–6 statutory payments each month (TDS by 7th, GST by 20th, PF by 15th, ESI by 15th, professional tax, advance tax quarterly) across different portals with different match keys (Challan 281 CIN, GST CPIN, PF TRRN, ESIC IP, OLTAS CIN). Missing any deadline triggers Section 201(1A) 1.5%/month TDS interest or Section 50 GST interest.
- **Logic:** Build a single statutory payment register keyed on payment type, with each row linking the bank debit to the respective match key (CPIN, TRRN, CIN, BSR+serial) and the portal confirmation status. Reconcile bank debits to portal confirmations within 5 working days and flag any portal-pending item for inquiry.
- **Config:** Unified register across TDS, GST, PF, ESI, advance tax, and professional tax; deadline calendar with interest-rate library; bank narration parser for each payment type; portal-status tolerance of 5 working days.
- **Output:** A CFO-visible statutory payment dashboard with zero missed deadlines, zero Section 201(1A) or 50 interest charges, and an audit-ready compliance pack covering all five portals.

### Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS

Source: https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india/

- **Problem:** Integrated steel and metal manufacturers in India run a captive power plant rail with separate coal procurement and cost allocation, an inbound freight rail across rail (RR / FOIS) and road (LR / e-way bill) with GTA reverse-charge treatment, a GST rail handling inverted duty across coal (5%), sponge iron (18%) and finished steel (18%), a scrap recovery rail under Section 394 TCS, a Section 393(1) Sl. 8(ii) purchase TDS rail on iron ore and coking coal, and an export-duty rail for IBM-classified iron ore grades — each with its own statutory anchor and ledger trail.
- **Logic:** Run CPP as a separate cost centre with metered kWh allocation to consuming units; reconcile inbound freight at PO / GRN / e-way bill / GTA RCM self-invoice level; track accumulated inverted-duty ITC monthly to drive a Section 54(3) refund file; collect Section 394 TCS at 1% on every scrap sale ledger entry; trigger Section 393(1) Sl. 8(ii) deductions automatically when per-vendor purchases cross ₹50 lakh per year; tag IBM-classified iron ore grades for export-duty applicability.
- **Config:** Steel configuration with CPP cost centre and kWh allocation file, rail / road freight ingestion with e-way bill GSTIN matching, GTA reverse-charge flag per transporter, coal / sponge iron / steel GST rate map, accumulated ITC tracker for Section 54(3) refund, Section 394 TCS scrap-category map, Section 393(1) Sl. 8(ii) per-PAN year-to-date counter on iron ore / coking coal / refractories / ferro-alloys, IBM iron ore grade tag for export duty.
- **Output:** A monthly steel close where CPP cost allocates cleanly to consuming units, every inbound freight invoice ties to its e-way bill and GRN, accumulated inverted-duty ITC drives a quarterly Section 54(3) refund claim, Section 394 TCS on scrap sales ties to the quarterly TCS return, Section 393(1) Sl. 8(ii) purchase TDS triggers automatically at ₹50 lakh crossing per vendor, and export duty on IBM-classified iron ore reconciles to the shipping bill.

### Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics

Source: https://www.terra-insight.com/insights/stock-transfer-reconciliation-india/

- **Problem:** A multi-GSTIN Indian manufacturer moves raw material, WIP and finished goods between plants daily, with each movement carrying a different statutory treatment — same-GSTIN movements need a delivery challan only, different-GSTIN movements trigger Schedule I deemed supply with IGST or CGST+SGST, and inter-state movements above ₹50,000 need an e-way bill — and reconciling those movements against GSTR-1, GSTR-2B, the e-way bill portal and the receiving plant's GRN breaks at scale.
- **Logic:** Classify each stock movement at origin by sender GSTIN, receiver GSTIN, value and inter-state flag; route same-GSTIN movements to delivery challan only, different-GSTIN movements to a tax invoice with IGST or CGST+SGST as applicable; generate e-way bill where consignment value exceeds ₹50,000; tie each outbound stock-transfer invoice to a GSTR-1 line at the sending GSTIN, a GSTR-2B line at the receiving GSTIN, an e-way bill number, and an inbound GRN at the receiving plant.
- **Config:** Plant-to-GSTIN mapping; HSN-wise GST rate table; e-way bill threshold per state (₹50,000 inter-state baseline, state-specific intra-state thresholds); stock-transfer invoice series per sending GSTIN; ageing window for open outbound challans (target return or GRN within 7 days); reconciliation calendar tied to GSTR-1 due date (11th of following month) and GSTR-3B due date (20th).
- **Output:** A daily stock-transfer dashboard showing outbound challans and invoices by sender and receiver GSTIN, e-way bill status (generated, in-transit, delivered, expired), inbound GRN match status at the receiving plant, GSTR-1 reporting status at the sending GSTIN, and GSTR-2B appearance status at the receiving GSTIN — with variance codes STOCK_TRANSFER_OPEN, EWAYBILL_EXPIRED, GSTR1_NOT_REPORTED, GSTR2B_NOT_MATCHED, and CHALLAN_AGED.

### Diamond and Precious Stone Studding HSN 7102/7103 Reconciliation for Jewellers

Source: https://www.terra-insight.com/insights/stone-diamond-studding-hsn-7102-7103-gst-jewellery-reconciliation/

- **Problem:** A studded gold jewellery invoice in India carries at least two, and often four, distinct GST rates on the same bill — 0.25% on diamond and precious-stone value under HSN 7102 and 7103 (Schedule VI of Notification 1/2017-CTR), 3% on the gold setting under HSN 7113 (Schedule V), 5% on making charges under SAC 9988 (Notification 11/2017-CTR Entry 26), and 18% on ancillary components under HSN 7326, 4819, or general codes. The customer-facing bill must show each rate line separately, the GSTR-1 filing must aggregate the same lines into distinct tax-rate rows, the GL must recognise revenue by HSN, and the certification chain (IGI, GIA, HRD, or IIGJ report) must be traceable back to each stone value. Retailers who mis-classify diamond value at HSN 7113 (3%) instead of HSN 7102 (0.25%) over-collect from the customer by 2.75% on stone value and must correct via Section 34 credit note within the November-following-FY window.
- **Logic:** Build a line-item classifier that assigns each invoice line to one of four rate buckets — 3% (jewellery HSN 7113 or silver setting), 5% (making charges as job-work services under SAC 9988), 0.25% (diamond HSN 7102 or precious-stone HSN 7103), and 18% (presentation box, safety plate, general HSN 7326 or 4819). Split diamond and gold values on every studded piece using the certification report as the source of truth for stone value and the day's gold rate as the source of truth for metal value. Aggregate lines into GSTR-1 tax-rate rows and reconcile against the trial-balance revenue by HSN. Deduct Section 393(1) Sl. 15 (10% code 1005) TDS on IGI, GIA, HRD certification lab payments above ₹30,000 aggregate threshold. Cross-foot output tax collected to GSTR-3B output tax liability before month-end close.
- **Config:** Item master with HSN code, rate flag (3% / 5% / 0.25% / 18%), stone-master indicator with certification lab reference (IGI, GIA, HRD, IIGJ) and per-carat value; making-charges service line with SAC 9988 and 5% rate; gold master with day's rate feed from industry association (IBJA or MMTC-PAMP or PSU refinery quote) tagged to the invoice date; certification lab master with GSTIN, 18% GST rate flag, and Section 393(1) Sl. 15 (code 1005) TDS flag; ancillary items master (box, plate, clasp) with 18% rate and Section 17(5) or 54(3) attribution flag; customer master with GSTIN for B2B (rare in retail) and PAN capture above ₹2 lakh cash consideration threshold under Rule 114B; per-invoice audit trail linking stone value to certification report ID.
- **Output:** A monthly reconciliation pack: invoice-level tax-rate split by 3%, 5%, 0.25%, and 18%, aggregated to GSTR-1 tax-rate rows; GL revenue reconciliation by HSN (7113 gold, 7102 diamond, 7103 coloured stone, SAC 9988 making, 7326/4819 ancillary) with variance tolerance per line; certification traceability report — every stone value linked back to a certification report ID or a periodic price list entry; Section 34 credit note register for HSN mis-classifications caught in the November-following-FY window; ITC reconciliation on 18% certification lab invoices and 18% ancillary inputs against 3% and 0.25% output supplies (inverted-duty accumulation); Section 393(1) Sl. 15 TDS reconciliation at 10% code 1005 against certifying-lab PAN in Form 26AS.

### Straddle Invoices: Pharma Movements Across the 22-Sept-2025 Cutover

Source: https://www.terra-insight.com/insights/straddle-invoice-pharma-pre-post-22-sept-2025-reconciliation/

- **Problem:** A pharma formulator dispatching HSN 3004 formulations to distribution partners across the 22-September-2025 rate cutover faces a Section 14 CGST time-of-supply exposure on every invoice issued in the 21-30 September 2025 pipeline window. An invoice raised on 21-September-2025 at 12 percent for goods that are physically dispatched on 23-September-2025 and received at the distributor on 24-September-2025 falls under Section 14 Clause (b)(i) — supply made after the rate change, invoice issued prior, payment received after — and the applicable rate is the new 5 percent, not the 12 percent charged on the original invoice. Absent correction, either the supplier over-collects and over-remits 7 percentage points of GST that Section 14 does not permit, or the distributor claims ITC at 12 percent that Section 14 caps at 5 percent, exposing the distributor to a Section 73 or Section 74 demand at the next GSTR-2B or GSTR-3B scrutiny. Thousands of pipeline invoices in the pharma channel in the 21-30 September 2025 window are potentially affected.
- **Logic:** Extract every invoice issued between 21-September-2025 and 30-September-2025 from the supplier's ERP invoice register. For each invoice, cross-reference three date fields: the invoice date (from the ERP), the dispatch date (from the transporter's lorry receipt or the e-way bill), and the goods-received-date (from the distributor's goods-received-note where available, or the delivery-confirmation event from the transporter). Anchor the supply date to the dispatch date under Section 31 read with Rule 46, and classify the invoice against Section 14: Clause (a)(ii) if dispatch was before 22-September-2025 with invoice-and-payment sequence matching, or Clause (b)(i) if dispatch was on or after 22-September-2025 with invoice issued prior to and payment received after the cutover. Derive the applicable rate from the classification. Where the applicable rate diverges from the rate charged on the original invoice, generate a Section 34 credit note reversing the original tax charge and issue a fresh tax invoice at the corrected rate for the same taxable value and quantity. Feed the credit note into the supplier's GSTR-1 for the correct tax period and reconcile the flow into the distributor's GSTR-2B and GSTR-3B ITC claim.
- **Config:** Invoice master keyed on invoice number, invoice date, supplier GSTIN, recipient GSTIN, HSN code, taxable value, rate charged, and tax amount; e-way bill and lorry-receipt master keyed on invoice reference with dispatch date, transporter identifier, and vehicle registration; distributor goods-received-note master keyed on invoice reference with receipt date and receipt-quantity confirmation; Section 14 clause-classification rulebook keyed on the dispatch-date test (before vs on-or-after 22-September-2025) and the invoice-and-payment sequence; Section 34 credit-note template with mandatory fields per Rule 53 (original invoice reference, credit-note number, credit-note date, reason code, differential taxable value or tax component); GSTR-1 upload feed and GSTR-2B download feed keyed on supplier GSTIN and recipient GSTIN for the corresponding tax periods; distributor ITC reversal register with per-invoice ITC-eligibility flag and the Section 14 clause that governs the position.
- **Output:** A month-end straddle-invoice reconciliation pack for the 21-30 September 2025 window: full invoice inventory extract with dispatch date, receipt date, and Section 14 clause classification per invoice; Section 34 credit-note issuance schedule with reason codes and GSTR-1 period assignment; fresh invoice issuance schedule at the corrected rate matched one-to-one to the reversed original invoices; distributor-side ITC reversal register with the ITC-eligibility position, the applicable rate cap, and any GSTR-2B versus GSTR-3B differential to be flagged with the supplier; and an audit trail per invoice that a Section 65 audit team or a Section 61 scrutiny officer can walk from the original invoice through the Section 14 classification, the Section 34 credit note, the fresh invoice, and the ITC claim on both sides of the transaction.

### Sub-Stockist Secondary Sales Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/sub-stockist-secondary-sales-reconciliation-fmcg/

- **Problem:** Indian FMCG brands rely on the sub-stockist tier as the last reported handover before retail — but the DMS portal secondary-sales feed reported by the sub-stockist lags actual retail offtake by 7 to 14 days, the sub-stockist's own van-tally register tells a parallel story the field sales team trusts, and the retailer-funded scheme-claim submission arrives 30 to 60 days after the dispatch with claims tied to retailer codes the DMS may or may not recognise. Ghost retailer codes can inflate the secondary base by 4 to 9 percent at quarter-end, scheme payouts run against unverified sales, PLISFPI incremental-sales certification rests on a base the certifying CA cannot easily substantiate, and Section 393(1) Sl. 18 commission TDS is over-deducted when AP treats every sub-stockist payable as commission.
- **Logic:** Build a sub-stockist secondary-sales register keyed by sub-stockist code, retailer code, SKU, dispatch date, and scheme reference. Match each DMS-portal line against the corresponding van-tally entry for the same sub-stockist, retailer, SKU, and date — flag missing or mismatched lines. Match the retailer scheme-claim submission against the DMS line by retailer code, scheme code, and period — flag claims against retailer codes not present in the DMS master. Run an outlet-existence test on retailer codes appearing in DMS but not in the van-tally — these are candidate ghost codes. Classify variances as reporting lag, retailer-master gap, ghost code, returns adjustment, or scheme-claim inflation; raise an investigation case for each.
- **Config:** Sub-stockist master with sub-stockist code, GSTIN, PAN, super-stockist link, and Section 393(1) Sl. 18 TDS rate; retailer master with retailer code, GST registration status, geo-tag, last-audit date, and DMS-active flag; SKU master with HSN, GST rate (pre- and post-22-September 2025), and scheme-eligibility flags; DMS secondary-sales feed from Botree / Bizom / Salesworx with the standard line schema; van-tally feed from field sales (paper or app); retailer scheme-claim submission feed; outlet-audit completion register with last-visit date per retailer code.
- **Output:** A monthly sub-stockist secondary-sales reconciliation pack: total DMS-reported secondary, total van-tally secondary, the variance bridge by class (lag, master gap, ghost code, returns, claim inflation), a ghost-candidate retailer list ranked by exposure, a scheme-payout-at-risk register, a Section 393(1) Sl. 18 TDS reconciliation showing cash commission deducted versus scheme net-off (zero TDS), and the substantive-test audit trail the certifying CA uses for PLISFPI incremental-sales certification.

### Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching

Source: https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation/

- **Problem:** Indian SaaS and service exporters receive Stripe payouts as USD or EUR SWIFT inward remittances at three potentially different rates — invoice-date rate, Stripe's conversion rate, and the receiving bank's rate — creating forex gain/loss entries that are not fees. FEMA requires FIRC documentation for GST zero-rated export refund claims.
- **Logic:** Matching joins Stripe payout_id against the bank SWIFT credit using UTR plus payout date plus INR amount, then reconciles each payout_id to its underlying charges and Stripe processing fee (typically 2-3% plus fixed component). The forex difference between invoice date and settlement date is computed and routed to a forex gain or loss classification, separate from fee variance.
- **Config:** SWIFT narration parser for payout_id extraction, forex rate source per invoice date, Stripe fee rate table, and FIRC request workflow with the receiving bank.
- **Output:** Per-payout reconciled revenue with separated processing fee, forex gain or loss journal entry, FIRC-referenced export-proceed ledger aligned to FEMA timeline, and evidence pack for GST zero-rated refund claim.

### Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act

Source: https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143/

- **Problem:** Indian manufacturers running job-work programmes under Section 143 of the CGST Act dispatch inputs and capital goods to dozens of job-workers on delivery challans, with statutory return windows of one year for inputs and three years for capital goods — beyond which the original dispatch is deemed a supply and triggers GST with 18% interest — and the reconciliation between the dispatch challan register, the return challan, the ITC-04 quarterly return, and the Section 393(1) Sl. 6(i) TDS on job-work charges is a four-way control that breaks once challan volume exceeds 200-300 a month.
- **Logic:** Tag every Section 143 dispatch challan at origin with a job-worker GSTIN, an input/capital goods flag, a value and a statutory clock (1 year for inputs, 3 years for capital goods); match return challans against the dispatch register on goods description and quantity; roll up the open-position by job-worker into the quarterly ITC-04 (or annual where turnover is up to ₹5 crore); flag challans approaching their statutory window 60 days in advance; on job-work payment, run the Section 393(1) Sl. 6(i) TDS deduction at 1% (individual/HUF) or 2% (company/firm).
- **Config:** Job-worker master with GSTIN, PAN, TDS rate per Section 393 code, registered/unregistered status; challan series per principal GSTIN; statutory clock per challan (1 year inputs, 3 years CG, no clock for jigs/fixtures/moulds/dies); quarterly ITC-04 due date calendar; alert thresholds at 60 and 30 days before the statutory window; matching tolerance on returned quantity (e.g., 2% for process loss).
- **Output:** A daily job-work dashboard showing open dispatches by job-worker, days remaining to statutory window, returned-versus-dispatched reconciliation by goods description, quantity variance against process-loss tolerance, ITC-04 reporting status per quarter, and the Section 393(1) Sl. 6(i) TDS deducted on job-work charges with payment codes 1023 / 1024 tying to the monthly challan.

### Subscription vs Ad Revenue Reconciliation: Two Ind AS 115 Streams

Source: https://www.terra-insight.com/insights/subscription-vs-ad-revenue-streaming-multi-stream-reconciliation-india/

- **Problem:** Streaming and OTT platforms in India run two economically distinct revenue streams through a single payment gateway rail. Subscription is an over-time performance obligation under Ind AS 115.35 — recognised across the subscription period. Advertising is a point-in-time obligation under Ind AS 115.32 — recognised on impression. Both attract 18% GST but under different SACs (998431 vs 998365) and different TDS treatments on the receivable side. A single-stream reconciliation misses one of them and produces a broken GSTR-1 SAC declaration, an unreconciled deferred revenue balance, or both.
- **Logic:** Split every PG settlement line by revenue stream tag at capture (subscription_id vs campaign_id metadata), route each side to its own recognition schedule, then reconcile: subscription lines to the over-time deferred revenue ledger and the corresponding monthly revenue release; advertising lines to the point-in-time impression ledger where recognition has already occurred. Reconcile both streams separately to GSTR-1 by SAC (998431 vs 998365) and to Form 27EQ / Form 26AS for TDS suffered on the ad-network side. Cash from the PG settles once — accounting closes twice.
- **Config:** Stream classifier keyed on order metadata (subscription_id / campaign_id / impression_batch_id); Ind AS 115 recognition split (over-time straight-line for subscription vs point-in-time on impression for ad); SAC-wise GSTR-1 aggregation (998431 vs 998365); TDS receivable ledger split by section (194H code 1015 for network commission, 194C / 194J for direct advertiser).
- **Output:** Two independent revenue schedules tied to a single settlement file; deferred revenue movement schedule for subscription; impression-based revenue register for advertising; SAC-wise GSTR-1 supply values; TDS reconciled to Form 26AS entries by section; audit-ready evidence pack per stream.

### Subscription SaaS MDR Economics for Indian Businesses: AutoPay vs Cards vs eNACH

Source: https://www.terra-insight.com/insights/subscription-saas-mdr-economics-india/

- **Problem:** Indian subscription merchants — B2B SaaS, OTT, edtech, NBFC EMI — bill the same ₹2,499 ticket across three recurring rails with fundamentally different fee structures. UPI AutoPay carries zero network MDR but a gateway platform fee; card-on-file recurring carries the base card MDR plus a 0.99% subscription add-on plus GST; eNACH carries roughly ₹15 plus GST per debit with retry-cycle compounding. The finance team usually sees a single bundled gateway fee on the daily settlement file and cannot tell which rail is driving the burden. The annual stack on a 12,000-mandate book runs to several lakhs that the CFO's flat-MDR mental model never surfaces.
- **Logic:** Split the monthly settlement file by recurring rail — UPI AutoPay, card-on-file, eNACH. For UPI AutoPay rows confirm network MDR equals zero and check the gateway platform fee against the contracted rate. For card-on-file rows compute expected base MDR at the contracted slab and expected recurring add-on at the contracted rate, sum and compare to the actual fee. For eNACH rows attribute every successful and failed debit to the mandate identifier, classify failures against the NPCI return reason taxonomy, and sum per-debit fees plus GST. Reconcile per-transaction GST totals against the aggregator monthly tax invoice.
- **Config:** Per-mandate registry with rail, mandate creation date, status, sponsor bank or PSP, MDR contract reference. Channel-tagged settlement file pipeline that splits AutoPay, card-on-file, and eNACH. Base-MDR rule set by card network and slab. Recurring add-on rate by aggregator. UPI AutoPay platform-fee schedule. eNACH per-debit fee schedule plus GST 18% overlay. NPCI return reason code dictionary. Retry-cycle attribution by mandate identifier. Monthly aggregator tax invoice reconciliation. Variance register feeding the unit-economics dashboard.
- **Output:** A monthly subscription unit-economics dashboard showing network MDR, gateway platform fee, recurring add-on, eNACH per-debit and rejection fees with retry compounding, and GST on each, totalled against the contracted rate sheet by rail. A routing-mix report that tracks the rail share of the recurring book and flags drift. A retry-policy report by NPCI return reason code that tunes the retry cadence per code. A monthly GST reconciliation between per-transaction totals and the aggregator tax invoice for ITC alignment.

### Sugar Mill FRP Cane Payment Reconciliation India — 14-Day Rule + 15% Interest

Source: https://www.terra-insight.com/insights/sugar-mill-frp-cane-payment-reconciliation-india/

- **Problem:** A UP multi-plant sugar producer running ten plants at an aggregate crushing of 3.5 lakh MT per day at peak season must reconcile every grower's cane delivery slip against the plant weighbridge tally, roll every ryot's cumulative accrual into a mill account statement at FRP plus SAP top-up plus recovery-linked premium, settle each ryot within the 14-day statutory window under Sugarcane (Control) Order 1966 Clause 3(3A), and accrue 15 percent per annum arrears interest on any slip that misses the 14-day window from day 15 to the actual payment date. Manual reconciliation across ten plants during a seven-month crushing season loses per-slip interest accrual on delayed settlements, over-states season-end grower liability against the state cane commissioner's audit, and mis-classifies cane development expenditure between Section 37 revenue and Section 32 capital — exposing the mill to a cane commissioner interest demand, a Section 143(3) scrutiny disallowance on the cane development GL, and a Section 201 short-deduction demand on cane transport TDS mis-classification.
- **Logic:** Build a ryot master keyed on grower code, plant code, village catchment, PAN (where filed), and bank account for direct settlement. Ingest every plant weighbridge slip into a ryot-wise cumulative accrual line and compute per-slip FRP component (Rs per quintal at the notified season rate), SAP top-up component (per state notification), recovery-linked premium (0.1 percentage point of recovery above basic reference times the notified premium rate), and any cane development recovery deduction. Roll the per-slip accrual into a plant-level mill account statement and issue to the ryot or the ryot's cooperative society at the cadence agreed. Run a daily 14-day-window sweep during the crushing season, flag every unpaid slip past day 14, compute the delay-days from day 15 to today, and accrue simple interest at 15 percent per annum on the unpaid principal. On the settlement run for each ryot, pay principal plus accrued interest together and mark the interest accrual as discharged in the workbook. Separate the cane development GL between Section 37 revenue (seed distribution, training, road repair, transport subsidy) and Section 32 capital (equipment, permanent road construction) so the year-end tax computation is defensible. Key every cane transport contractor payment to Section 8 Sl. 4 code 1001 (Individual/HUF small transporter at 1 percent) or code 1002 (transport firm at 2 percent) for TDS reconciliation against Form 26AS at each transporter's PAN.
- **Config:** Ryot master with grower code, plant assignment, village catchment code, PAN (where filed), bank account, cooperative society code where applicable; plant master with plant code, weighbridge network, chief chemist reference for recovery-percentage certification, and cane accounts controller; cane price schedule with FRP rate per quintal by season, SAP top-up rate by state and season, recovery-linked premium slab (typically Rs per quintal per 0.1 percentage point above basic recovery); basic-recovery reference per state per season as notified by the cane commissioner; 14-day payment-window rule as system-level constant; 15 percent per annum interest-accrual rule as system-level constant; cane development GL master with Section 37 revenue versus Section 32 capital classification; cane transport contractor master with PAN and TDS payment code 1001 or 1002; EBP ethanol lifting master keyed to OMC contract (IOCL/BPCL/HPCL), feedstock category (C-heavy, B-heavy, cane-juice-direct), and notified ex-mill ethanol price by category; Section 43B(h) MSME flag on cane transport contractors and cane development suppliers (small transporters and cane seed vendors are frequently MSME-registered).
- **Output:** A daily crushing-season reconciliation pack per plant: opening ryot ledger balance, day's weighbridge tally by grower, per-slip FRP plus SAP plus recovery premium accrual, cumulative ryot accrual, 14-day-window sweep of unpaid slips with day-count and 15 percent per annum interest accrual, settlement-run schedule with principal plus interest payable per ryot, and settlement remittance record with mill account statement despatched to grower or cooperative society. A monthly cane-transport-contractor reconciliation pack with TDS code 1001/1002 classification and Form 26Q draft. A season-end cane development GL reconciliation with Section 37 revenue versus Section 32 capital split and the per-ryot benefit register as audit trail. A parallel distillery-lifting reconciliation for EBP-participating mills with per-tender lifting schedule, feedstock category tally, and OMC settlement invoice matched against ex-mill despatch record.

### Sugarcane SAP vs FRP Reconciliation — Uttar Pradesh + Punjab

Source: https://www.terra-insight.com/insights/sugarcane-sap-vs-frp-reconciliation-uttar-pradesh-punjab/

- **Problem:** A UP or Punjab sugar mill running a ryot-wise cane payment cascade against the 2024-25 season Central FRP of Rs 340 per quintal at 10.25 percent basic recovery, and a state-notified SAP of Rs 355 per quintal on UP general variety or Rs 391 per quintal on Punjab general variety, must reconcile the FRP baseline, the CACP sucrose recovery adjustment, the flat SAP top-up funded from the mill's operating margin, the 14-day payment liability under Clause 3(3A) of the Sugarcane (Control) Order 1966, the 15 percent per annum arrears interest on every balance unpaid beyond that window, and the parallel Section 43B(h) 45-day MSME clock where the cane grower is registered on the Udyam portal. Manual reconciliation across 50,000 to 200,000 ryot codes per mill loses per-delivery FRP-vs-SAP tagging, mis-computes the cane development levy base, and understates the 15 percent per annum arrears accrual on the cane commissioner weekly return — exposing the mill to interest recovery notices, crushing licence suspension risk, and (where the ryot is a registered MSME) a Section 43B(h) income-tax disallowance at year-end.
- **Logic:** Build a ryot-wise cane grower master keyed on the ryot code, cane development society, Aadhaar or bank-account destination, Udyam registration flag, and variety category, and expand every cane delivery slip into a session-level record with weighed quantity, variety, FRP portion per quintal (after CACP recovery adjustment), SAP top-up per quintal (flat, state-notified), aggregate payment liability, and 14-day due date. Age every unpaid balance against the 14-day Clause 3(3A) clock and against the 45-day Section 43B(h) clock in parallel, and accrue 15 percent per annum interest on the sugar-industry-specific 14-day bucket into a separate ledger line. Split the FRP portion and the SAP top-up as distinct posting lines so that the cane development levy computation, the state cane commissioner weekly return, and the mill margin analysis all draw from the same ryot delivery slip and reconcile against the mill's own bank payment file. At season close reconcile the certified sugar recovery percentage against the CACP basic-recovery-adjusted FRP payment already made per delivery, and generate a season-end true-up posting per ryot for premium (recovery above 10.25) or rebate (recovery below 10.25 subject to floor).
- **Config:** Ryot master with ryot code, village, cane development society, Aadhaar and bank IFSC/account, PAN (where filed), Udyam registration number and MSME classification flag; variety master with variety code, category (early/general/unsuitable in UP; general in Punjab), CACP-notified basic-recovery reference and premium/rebate rate; season master with FRP notification (Rs 340 per quintal at 10.25 percent for 2024-25), state SAP notification (Rs 355 UP general, Rs 391 Punjab general for 2024-25), and season start/close dates; cane delivery slip register keyed to delivery date, ryot code, weighed quantity, variety, and delivery centre; mill payment register keyed to payment date, ryot code, and payment mode (Aadhaar-linked direct benefit transfer, IMPS, or NEFT); Section 43B(h) MSME 45-day ageing configuration with year-end disallowance rule; state cane commissioner weekly return template with the FRP portion, SAP top-up, aggregate liability, paid amount, unpaid balance, and 15 percent per annum arrears interest accrual columns.
- **Output:** A season-long ryot-wise cane payment pack: cane delivery slip register with FRP portion, SAP top-up, aggregate liability, and 14-day due date per delivery; weekly cane commissioner return with paid-versus-unpaid balance and 15 percent per annum arrears accrual; parallel Section 43B(h) 45-day MSME ageing report with year-end disallowance workbook for the mill's Form 3CA-3CD filing; season-close CACP recovery adjustment true-up per ryot mapping the certified seasonal recovery percentage to premium or rebate against the base FRP; cane development levy computation base split between the FRP portion and the SAP top-up; and a mill-margin analysis showing the SAP-over-FRP delta absorbed from operating margin (Rs 15 per quintal in UP general variety, Rs 51 per quintal in Punjab general variety at 2024-25 season notifications).

### Super-Stockist and CFA (Carrying & Forwarding Agent) Reconciliation for FMCG

Source: https://www.terra-insight.com/insights/super-stockist-cfa-reconciliation-fmcg/

- **Problem:** Indian FMCG brands run two parallel distribution constructs in the same territory — super-stockists who buy on a primary tax invoice and own the inventory, and CFAs who receive Schedule I deemed-supply transfers without consideration and hold inventory on the brand's books as consignment agents. The two flows look similar on a distribution map but reconcile entirely differently: title transfer point, GSTIN of the inventory holder, TDS section under Section 393(1) Sl. 4 versus Sl. 18, ITC reversal regime, and audit evidence pack diverge at every step. Brands that run a single uniform process miss the Schedule I IGST on inter-state CFA transfers, mis-classify CFA service fee as super-stockist commission for TDS, fail to tie the CFA monthly stock statement to the brand inventory ledger, and surface the gap only at the year-end statutory audit — leaving roughly two percentage points of channel margin unreconciled every quarter.
- **Logic:** Operate two independent reconciliation regimes. For super-stockists: build a primary invoice register keyed by brand GSTIN and super-stockist GSTIN; pull the super-stockist's DMS dispatch file by SKU by sub-stockist by period; classify each delta into scheme reversal (Section 15(2) CGST), trade-margin adjustment, damage credit, or genuine inventory shortfall; reconcile the super-stockist commission flow to Section 393(1) Sl. 18 (legacy 194H) at 5% in Form 26AS. For CFAs: build a Schedule I transfer register keyed by brand mother-warehouse GSTIN and CFA depot GSTIN; pull the CFA monthly stock statement by SKU by batch; tie opening plus inward minus outward minus damages minus destruction to closing stock at the brand inventory GL; reconcile the CFA service-fee flow to Section 393(1) Sl. 4 (legacy 194C) at 2% in Form 26AS. Cross-verify by GSTIN that every CFA depot has a separate registration per Section 24(vii) and that inter-state Schedule I transfers carry IGST at the HSN rate effective on the transfer date.
- **Config:** Channel master classifying every partner as super-stockist (principal-to-principal) or CFA (Schedule I agent) or hybrid (both functions, with separate vendor codes); brand GSTIN master per mother warehouse and per CFA depot; primary invoice feed from SAP SD or equivalent at line level; DMS secondary dispatch feed from each super-stockist; CFA monthly stock statement feed with SKU-batch-level opening, inward, outward, damages, destruction, and closing; Schedule I transfer register tracking inter-state versus intra-state transfers with IGST or CGST plus SGST output liability; vendor master with PAN and Section 393(1) classification (Sl. 4 versus Sl. 18) per vendor code; HSN rate-effective-date register for the 22 September 2025 GST 2.0 transition; ageing rule for in-transit stock between mother warehouse and CFA depot; per-PAN TDS rule routing payments at 5% / 2% / 1% based on flow classification.
- **Output:** A monthly two-stream reconciliation pack: a super-stockist primary-vs-secondary register with per-partner ageing of stuck claims, scheme reversal classification under Section 15(2), and Section 393(1) Sl. 18 commission TDS reconciled to Form 26AS; and a CFA inventory-vs-stock-statement register tying every depot's closing balance to the brand inventory GL, Schedule I IGST output liability reconciled to GSTR-1 IGST inter-state supply lines, and Section 393(1) Sl. 4 service-fee TDS reconciled to Form 26AS. The 90+ day in-transit ageing bucket feeds CARO 2020 disclosure on inventory-in-transit, the Schedule I per-CFA register feeds the GSTR-1 outward supply schedule, and the consolidated commission-and-service-fee register supports the brand's TDS Form 26Q filing.

### Supplementary Invoices for RMPV Price Escalation: GST Section 34 Treatment for Auto Suppliers

Source: https://www.terra-insight.com/insights/supplementary-invoice-price-escalation-gst-section-34-auto-india/

- **Problem:** Auto-component RMPV clauses settle commodity-index movements between supplier and OEM at quarterly or six-monthly cadence; an upward index movement triggers a price escalation against dispatches that were correctly invoiced at the time. The supplier must push GST output liability on the escalation through either a supplementary invoice under Section 31(3)(c) or a debit note under Section 34(3) — only one is correct for a post-supply RMPV upward revision and the wrong document breaks the IRN flow, the GSTR-1 Table 9B linkage to the original invoice, and the OEM-side GSTR-2B reflection that allows the OEM to claim the additional ITC; on a typical wire-harness or sheet-metal Tier-1 doing ₹4.8 crore of base dispatches a 6-month RMPV upward revision of ₹38 lakh carries ₹6.84 lakh of incremental output GST at 18% that must move through the document chain cleanly.
- **Logic:** Classify the RMPV settlement letter by direction (upward or downward), settlement basis (quarterly or six-monthly), and underlying invoice cohort; for upward revisions select Section 34(3) debit note as the default document; reconfirm whether the original invoice was provisional (then Section 31(3)(c) supplementary invoice); generate a debit-note candidate keyed to each original invoice in the cohort with the proportionate escalation share; route the candidate through the IRP for IRN generation with the original invoice's IRN as linked reference; post the document to GSTR-1 Table 9B (CDNR) with reason code 'price revision'; track OEM acceptance through the Invoice Management System; reconcile the OEM's accepted set to the supplier's issued set.
- **Config:** OEM customer master with GSTIN and RMPV cadence; original tax invoice ledger with IRN, dispatch quantities and base rate; RMPV settlement letter ingest with index reference (JPC steel composite, LME copper, LME aluminium), settlement period and escalation amount; document-choice rule (Section 31(3)(c) for provisional originals, Section 34(3) for finalised originals); apportionment policy across original invoices in the cohort; IRP integration for IRN generation; GSTR-1 Table 9B export queue with original-invoice reference; OEM-side IMS acceptance tracking.
- **Output:** A daily RMPV upward-revision action queue ranked by OEM and settlement period; a debit-note generation pack with original-invoice apportionment, IRN payload, GSTR-1 Table 9B reason code and OEM-side acceptance status; an exception register flagging documents where the document type was switched (supplementary versus debit note) with audit trail; an output-tax addition view by OEM, programme and cohort; and an audit-defensible link from every debit note back to the triggering RMPV settlement letter and the original tax invoice cohort.

### Surat Synthetic Saree Domestic + Export Reconciliation

Source: https://www.terra-insight.com/insights/surat-synthetic-saree-domestic-export-reconciliation/

- **Problem:** A Surat polyester saree mill running a mixed 70 percent domestic + 30 percent export book must reconcile four parallel surfaces on the same inventory pool — GSTR-1 against the domestic invoice ledger on HSN 5407, shipping bill against RoDTEP Appendix 4R claim, e-BRC realisation against the export invoice register, and Rule 89(5) inverted-duty position on polyester-yarn-to-saree. A single mis-tagged SKU at the invoice level — a saree classified as HSN 5407 in the sales register but shipped under 5408 on the shipping bill, or an export invoice raised under LUT but the shipping bill filed with IGST payment — propagates through all four surfaces and leaks the RoDTEP claim, distorts the GST refund, and opens an EDPMS realisation gap.
- **Logic:** Split the outward supply register into domestic and export streams at the invoice level; reconcile the domestic stream against GSTR-1 Table 4 and GSTR-3B Table 3.1(a) at the buyer-GSTIN and HSN level; reconcile the export stream against the shipping bill filed on ICEGATE (matching invoice number, shipping-bill number, port code, date, FOB value) and against the RoDTEP scrip credit in the ECL wallet at the notified Appendix 4R rate; reconcile the export invoice against the e-BRC issued by the AD banker on EDPMS within the 9-month realisation clock; run the Rule 89(5) inverted-duty check monthly to confirm the expected nil position for the yarn-to-saree conversion and flag any HSN mis-classification that distorts the check.
- **Config:** SKU master with saree HSN classification (5407 synthetic filament, 5408 artificial filament, 6117 knitted made-ups, 6217 other made-ups), fibre content, and MMF category flag; buyer master with GSTIN, state code, and domestic-versus-export flag; RoDTEP scheme configuration with Appendix 4R rate per 8-digit HSN and shipping-bill claim-code mapping; ICEGATE shipping-bill ingest with invoice-to-SB link; EDPMS e-BRC ingest with SB-to-BRC link and realisation status; LUT number and validity period on the buyer or shipment master; Rule 89(5) inverted-duty check parameters (input HSN, output HSN, expected nil accumulation flag).
- **Output:** A month-end domestic-plus-export reconciliation pack: domestic sales register reconciled to GSTR-1 by buyer GSTIN and HSN with variance report; export invoice ledger reconciled to shipping bill by SB number, port code and FOB value; RoDTEP scrip claim ledger with expected credit at Appendix 4R rate versus actual ECL credit and open-claim ageing; e-BRC realisation report with days-to-9-month clock per open shipping bill; Rule 89(5) inverted-duty position confirming nil accumulation for the polyester-to-saree conversion and flagging any HSN mis-classification that would distort the check.

### Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders

Source: https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements/

- **Problem:** Bank statements of loan applicants or customers may contain AML-relevant patterns — hawala-associated counterparty names, structured transaction clusters, round-trip fund movements, and shell entity narrations — that create PMLA obligations for the regulated lender. Manual review at scale cannot reliably surface these patterns.
- **Logic:** Match transaction counterparty names and narration strings against lists of hawala-associated terms, shell entity indicators, and structured transaction patterns. Run round-trip matching on credit-debit pairs with the same counterparty within configurable time windows. Count sub-threshold transaction clusters to detect structuring. Identify dormancy-and-burst patterns and velocity anomalies.
- **Config:** Enable for NBFC compliance and credit underwriting workflows. Configure structuring threshold and round-trip time window based on lender policy and FIU-IND guidelines. Include counterparty name variants and informal remittance operator names for India-specific coverage.
- **Output:** AML risk section in the credit report with suspicious pattern types flagged, round-trip matched pairs listed, structuring cluster count, and a composite AML risk level for compliance team prioritisation.

### Swappable Battery-as-a-Service (BaaS) Reconciliation for Indian EV OEMs

Source: https://www.terra-insight.com/insights/swappable-battery-as-a-service-baas-reconciliation-india/

- **Problem:** An Indian swappable-BaaS operator with a 4,200-battery fleet across 580 swap stations confronts a dual-rail reconciliation problem: an asset ledger of per-battery Ind AS 36 CGUs with monthly capacity-fade impairment testing, and a revenue ledger of multi-component supplies (monthly subscription, per-swap fee, end-of-life battery resale) each with its own Ind AS 115 recognition pattern and GST classification. Layered on are Section 393 codes 1007/1009/1010 TDS to site hosts and aggregators, Section 394 code 1023 TCS on scrap battery sales, and a battery-circulation ledger that must tie each swap event to a specific battery serial number for audit traceability.
- **Logic:** Maintain a battery-asset master keyed by serial number with manufacturing date, chemistry, kWh nameplate, cumulative cycles, depth-of-discharge profile, current capacity-fade percentage, location (station-of-residence at any time), Ind AS 36 carrying value and impairment-flag status. Run a per-swap event ledger linking rider, station, batteries-in and batteries-out, swap-fee charged and BMS telemetry snapshot. Recognise monthly subscription over period and per-swap fee at event under Ind AS 115. Run quarterly impairment testing on the battery fleet with indicators trigger from BMS capacity-fade beyond threshold. Tie site-host accruals at agreed rental or commission rate; deduct Section 393 codes 1006/1009/1035 TDS at outbound payment; reconcile aggregator settlement files weekly; classify end-of-life battery resale at HSN 8507 (used) or 8548 (scrap) with Section 394 code 1023 TCS at 1 percent on scrap.
- **Config:** Battery-asset master with per-serial CGU tracking, BMS telemetry feed, cumulative cycles, capacity-fade, Ind AS 36 impairment status; swap-station master with site-host structure (rental / commission), CESL flag where applicable; rider master with subscription tier, GSTIN where corporate, and aggregator-of-origin where applicable; swap-event ledger with battery-in serial, battery-out serial, fee charged and GST output; site-host master with Section 393 code (1006 or 1009); aggregator master with Section 393 code 1035 and Section 52 CGST TCS flag; end-of-life-battery disposal register with HSN classification and Section 394 code 1023 TCS log.
- **Output:** A per-battery monthly asset-status report with cumulative cycles, capacity fade, Ind AS 36 carrying value and impairment flag; a per-swap-event ledger with rider, station, batteries-in/out and fee; monthly subscription revenue recognised over period plus per-swap fee at event with 18 percent GST output; site-host rental and commission accruals with Section 393 codes 1006/1009 TDS deducted; aggregator settlement reconciliation with Section 393 code 1035 TDS and Section 52 CGST TCS credit; end-of-life battery disposal register with Section 394 code 1023 TCS on scrap sales; quarterly Form 26AS chase by counterparty TAN.

### Swiggy Instamart FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/swiggy-instamart-fmcg-settlement-reconciliation/

- **Problem:** An FMCG brand running ₹1.5 to ₹2 crore monthly through Swiggy Instamart's dark-store network — densest in Mumbai, Bangalore, Delhi and Pune — receives settlement on a T+7 to T+14 cycle that varies by category and by dark-store cluster, with seven deduction lines per cycle including Section 52 TCS at the 0.5 percent notified rate, listing fee debits, BTL marketing claim deductions and per-dark-store fill-rate penalties. Without a per-dark-store reconciliation discipline, mid-tier brands routinely surrender ₹4 to 6 lakh of contestable listing-fee mis-pricing and ₹76,000 to ₹1.2 lakh of recoverable BTL-invoice GST ITC into a generic Instamart settlement clearing account, with the Section 9(5) versus Section 52 GST classification quietly mis-treated and the TCS credit never landing in the electronic cash ledger because the GSTR-8 reconciliation was never closed.
- **Logic:** Ingest the Swiggy Instamart settlement file at the dark-store grain rather than at the brand-GSTIN aggregate; decompose each dark-store invoice cluster into the seven canonical deduction buckets — item-level margin, listing fee (per dark-store, per SKU), BTL marketing claims (separate 18 percent GST line routed to marketing GL with ITC claim), scheme reimbursement classified by Section 15(2) treatment, fill-rate and dark-store-specific QC penalties, return-to-vendor credit notes, and Section 52 TCS at the 0.5 percent notified rate. Tag every outward supply in GSTR-1 with the Swiggy ECO GSTIN reference. Close the Section 52 three-way tie (settlement file ↔ Swiggy GSTR-8 ↔ brand GSTR-2A) on a monthly cadence. Apply the rate-by-date table for the 22 September 2025 GST 2.0 cut-over per HSN on every dark-store invoice. Reconcile the per-dark-store bank receipt against Swiggy's payment advice cluster.
- **Config:** Swiggy Instamart account master with dark-store register (Mumbai, Bangalore, Delhi, Pune dense clusters first); settlement file parser with per-dark-store decomposition; deduction-taxonomy mapping (margin, listing fee, BTL claim, scheme reimbursement, fill-rate penalty, RTV credit note, Section 52 TCS); SKU master with HSN, GST rate and 22 September 2025 cut-over flag; scheme master with Section 15(2) treatment flag per scheme code; BTL invoice register routed to marketing GL with separate ITC claim; Section 52 TCS register at the 0.5 percent notified rate (CBIC Notification 15/2024-CT); GSTR-1 tagging rule for ECO-collected supplies (Swiggy TCS-collector GSTIN); GSTR-8 ingestion per month from Swiggy; GSTR-2A TCS credit reconciliation rule; bank-statement matcher for net per-dark-store settlement receipts; Section 9(5) exclusion flag — FMCG goods are NOT in the deemed-supplier regime.
- **Output:** A monthly Swiggy Instamart reconciliation pack per dark-store cluster: gross invoice raised, seven-bucket deduction decomposition with named-dark-store breaks, BTL claim audit against JBP and execution evidence, net bank receipt tied to Swiggy's payment advice cluster, Section 52 TCS three-way tie (settlement file ↔ Swiggy GSTR-8 ↔ brand GSTR-2A), GSTR-1 outward-supply tagging audit trail, BTL invoice register with 18 percent ITC posture, scheme reimbursement ageing buckets (0-30 / 31-60 / 61-90 / 90+ days), GST 2.0 rate-by-date audit log on the 22 September 2025 cut-over per HSN, and a leakage summary surfacing unrecovered listing fees, mis-tagged BTL deductions, and any Section 9(5) versus Section 52 treatment error before the GSTR-3B cycle closes.

### Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation

Source: https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr/

- **Problem:** A multi-outlet QSR chain reconciling Swiggy Food and Swiggy Instamart payouts must handle commission tier complexity, SLA penalty deductions, ad-spend deductions, restaurant-borne discount components, the 7 to 14 day Partner Portal dispute window, Food vs Instamart channel split, Section 393 TDS at 0.1% under payment code 1035, Section 52 CGST TCS at 1%, GSTR-2B commission ITC matching, multi-GSTIN consolidation, and CARO 2020 audit evidence — across 30 to 100 outlets — and then evaluate whether manual Excel, an aggregator-side tool, or reconciliation infrastructure is the right fit.
- **Logic:** Walk each approach through one Swiggy weekly cycle: ingest the Food and Instamart settlement files at order level, classify Food vs Instamart channel with channel-specific GST treatment (5% no-ITC for prepared meals; 12% or 18% with ITC for Instamart categories), decompose commission and 18% GST on commission, accrue Section 393 TDS at 0.1% with payment code 1035 mapping, compute Section 52 CGST TCS with intra-state CGST/SGST or inter-state IGST split, separate platform-borne from restaurant-borne discounts, classify SLA penalties by category, link to POS gross sales, link to bank credit narration, match commission ITC against GSTR-2B, accept TCS into cash ledger via GSTR-8A, flag Section 9(5) GST liability, surface dispute candidates inside the Partner Portal window, and roll up across outlets, GSTINs, states, and channels.
- **Config:** Swiggy Food and Instamart settlement-file connectors with channel-specific rules; commission tier table per outlet agreement; Section 393 TDS calculator at 0.1% on gross supply with payment code 1035 mapping; Section 52 CGST TCS calculator with intra-state CGST/SGST and inter-state IGST split; SLA penalty parser with category mapping; restaurant-borne vs platform-borne discount classifier; GSTR-2B commission ITC matcher; GSTR-8A cash-ledger acceptance flow; Section 9(5) GST classifier; refund-period reversal logic; multi-outlet, multi-GSTIN, multi-state rollup; dispute-window flagging.
- **Output:** A reconciled Swiggy weekly cycle in which every order traces from gross sale through commission, GST, Section 393 TDS, Section 52 TCS, SLA penalty, and discount components to the bank credit; commission ITC is matched to GSTR-2B per GSTIN; Section 52 cash-ledger credit is accepted via GSTR-8A; dispute candidates are flagged before the Partner Portal cut-off; multi-outlet, multi-GSTIN, multi-state rollups close inside the month; and CARO 2020 audit evidence is one query away.

### Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties

Source: https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation/

- **Problem:** Swiggy's weekly restaurant settlement carries the same 194O and Section 52 deductions as Zomato but adds SLA penalties and restaurant-borne discount lines that vary order by order — and Swiggy Food and Swiggy Instamart use entirely separate payout files that must not be reconciled in the same workflow.
- **Logic:** Ingest the Swiggy Partner settlement file at order level, classify each order by Food or Instamart channel, separate platform-borne from restaurant-borne discounts, post commission and 18% GST on commission with ITC, accrue 194O TDS and Section 52 TCS as receivables, expense SLA penalties as a distinct ledger head, and surface dispute candidates within the 7 to 14 day Partner Portal window.
- **Config:** Swiggy Food and Instamart settlement file connectors with channel-specific rules; commission tier table per restaurant agreement; SLA penalty parser with category mapping; restaurant-borne vs platform-borne discount classifier; 194O 1% on gross taxable supply; Section 52 1% TCS with intra-state and inter-state split; weekly dispute-window flag.
- **Output:** A reconciled Swiggy weekly payout with each order traced to gross revenue, commission, GST, TDS, TCS, SLA, and discount components, with disputes auto-flagged before the Partner Portal cut-off and tax credits posted in time for monthly GSTR-3B and quarterly TDS reconciliation.

### Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate

Source: https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement/

- **Problem:** MSME credit assessments require a balance sheet view to determine net worth and working capital position, but most MSMEs do not maintain formal accounts — leaving lenders without the asset-liability picture needed for loan sizing.
- **Logic:** Bank statement data supports approximation of current assets (cash balances, receivables proxy from payment lag analysis) and current liabilities (NACH mandates, recurring payables). Fixed assets, depreciation, and equity are excluded from the output because they cannot be reliably inferred from transaction data alone.
- **Config:** Working capital window is configurable (3, 6, or 12 months). Receivables proxy lag thresholds are set per industry segment. Known NACH mandate amounts are used as the hard floor for current liability estimation. Owner withdrawal amounts can be treated as drawings (excluded from liabilities) or flagged for review.
- **Output:** Approximate current asset position, approximate current liability position, net working capital estimate, and cash and bank balance as at the analysis date. Output is labelled as bank-data-derived, not auditor-certified.

### Synthetic Financial Statements for MSME Credit: What They Are and How They Work

Source: https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india/

- **Problem:** Over 63 million Indian MSMEs lack audited financial statements, making them ineligible for formal credit despite viable businesses — the documentation gap is the primary reason for loan rejection, not business performance.
- **Logic:** Bank transactions contain the raw information needed to reconstruct financial statements — revenue patterns, cost flows, working capital cycles, and debt obligations are all embedded in transaction data and can be extracted through structured four-layer analysis.
- **Config:** The four layers are applied sequentially: (1) personal vs business transaction separation, (2) synthetic P&L construction, (3) synthetic balance sheet (working capital + net worth approximation), (4) synthetic cash flow classification into operating, investing, and financing activities.
- **Output:** A complete synthetic financial statement package: 12-month income and expense trajectory (P&L), working capital and net worth approximation (balance sheet), and cash flow classification — sufficient to calculate DSCR, size working capital facilities, and assess term loan eligibility.

### Tally Prime for Auto-Component Manufacturers: Reconciliation Limits and Workarounds

Source: https://www.terra-insight.com/insights/tally-prime-auto-component-reconciliation-limits-india/

- **Problem:** Indian auto-component Tier-1 manufacturers running Tally Prime as their accounting platform face a structural gap — Tally handles GST returns, e-invoice / e-way bill, TDS deduction including the new Income Tax Act 2025 codes 1001-1092, bank reconciliation and accounting fundamentals well, but does not support EDI / scheduling-agreement supply, CUM accounting, RMPV recomputation, FOMP debit decomposition, Section 143 deemed-supply alerting, multi-OEM programme tracking or tooling cap monitoring. The result is a Tally + Excel workflow where the OEM-settlement reconciliation runs outside the system of record, with month-end close stretching to 7-10 days of controller time and material recovery leakage on contested debit lines.
- **Logic:** Map Tally Prime's capabilities against the 10 auto-component reconciliation streams (OEM settlement, EDI / ASN with CUM, RMPV, quality debits, Section 143 job-work, free-issue steel, consignment, KLT bins, tooling, PLI / export), identify Tally-handled streams (GST returns, TDS deduction, bank reconciliation, accounting books) versus Tally-gap streams (everything OEM-side and scheduling-agreement-driven), maintain Tally as the books-of-account system of record, and add TransactIG as the reconciliation layer reading Tally exports on a daily cadence and surfacing OEM-side exceptions back to the finance team for action.
- **Config:** Tally Prime install with auto-component manufacturer chart-of-accounts, GST module configured for HSN 8708 / 8432 family rates (28% / 18% / 5% as applicable), TDS module configured for Income Tax Act 2025 payment codes 1001-1092 with parallel legacy 194C / 194Q / 206C(1) ledgers during cross-era migration, daily Tally export job (invoice register, receipt register, TDS register, GST output), TransactIG reconciliation layer consuming Tally exports plus OEM portal exports (e-Nagare, TML SRM, M&M Supplier Portal, SupplyOn), reconciliation streams configured per OEM customer, programme-level margin tracker.
- **Output:** A TransactIG-on-top architecture: Tally Prime retains books-of-account status with daily structured exports of invoice / receipt / TDS / GST data, TransactIG reads Tally exports plus OEM portal exports and runs the auto-component reconciliation streams as continuous exception management with CUM drift register, FOMP claim sheet, programme-level margin tracker, Section 34 GST credit-note calendar, Form 168 TDS reconciliation against books, and Section 143 deemed-supply countdown — all surfaced through dashboards with action queues feeding back to the Tally accounting team for posting.

### Tally Prime Workarounds for Auto-Component Tier-2 and Tier-3 Suppliers

Source: https://www.terra-insight.com/insights/tally-prime-auto-component-workarounds/

- **Problem:** Indian Tier-2 and Tier-3 auto-component suppliers at ₹15-50 crore revenue economically cannot run SAP S/4HANA or Oracle Fusion Cloud, so they run on Tally Prime. Tally Prime lacks native scheduling agreement, ASN, EDI 830 / 862, RMPV index linkage, ITC-04 multi-hop and free-issue Rule 55 tracking on the supplier side. The result is a Tally + Excel + macros stack where workarounds carry the supply chain reconciliation discipline that the OEM-Tier-1-Tier-2-Tier-3 ecosystem demands.
- **Logic:** Treat Tally Prime as the document and accounting system of record (sales orders, tax invoices, e-invoice, e-way bill, GST returns, TDS deductions, bank reconciliation), maintain the supply-chain dimensions externally in structured Excel side-cars (SA master, ASN register, RMPV calculator, ITC-04 multi-hop tracker, free-issue stock register), use Tally voucher classes plus cost-centre / cost-category tagging to carry the cross-references between Tally and the Excel side-cars, and run four disciplined monthly reconciliations between Tally exports and the Excel side-cars.
- **Config:** Tally Prime install with auto-component manufacturer chart-of-accounts, GST module configured for HSN family rates, TDS module configured for Income Tax Act 2025 codes 1001-1092 (Section 393(1) Sl. 6(i) codes 1023 / 1024 contractor, Section 393(1) Sl. 8(ii) code 1031 purchase, Section 394 code 1071 scrap), custom voucher classes for ASN delivery note and free-issue Rule 55 challan, cost-centre and cost-category dimensions for ASN number / OEM reference / programme / hop count / downstream GSTIN, daily ODBC export job, Excel side-cars for SA master, ASN ageing, RMPV calculator, ITC-04 multi-hop tracker, free-issue stock register, with macros or Python utilities for the ITC-04 JSON generation.
- **Output:** A disciplined Tally + Excel + macros operating model where Tally Prime carries documents and books, Excel side-cars carry the auto-component supply-chain dimensions (SA, ASN, RMPV, ITC-04, free-issue), four monthly reconciliations close the gaps between the two layers, month-end runs at 6-8 controller days, and the workaround stack supports up to 60-80 active SA-equivalents and three to four direct OEM-Tier-1 customers before economic pressure to migrate up to a heavier reconciliation platform kicks in.

### Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses

Source: https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india/

- **Problem:** Tally Prime is the deepest India-localised SME ERP with native GSTR-2B import, TDS challan tracking, and bank reconciliation screens, but its single-user data folders, manual voucher matching, and lack of a true multi-branch console make it impractical for organisations above 2,000 bank lines per month or 5+ branches — especially for CA firms running 80–200 Tally client instances in parallel.
- **Logic:** Automate Tally via one of three integration paths: XML API for structured voucher export and import, TallyODBC for read-only BI queries (deprecated from TallyPrime 4.0 onwards), or the Tally Connector HTTP endpoint on port 9000 with TDL-formatted XML payloads. External layer reads ledgers via XML, ingests bank MT940/CSV and GSTR-2B JSON externally, runs multi-pass matching, and posts cleared voucher numbers back to Tally via XML import.
- **Config:** Tally Connector HTTP enabled via F12 configuration, XML API payload templates per TDL schema, per-company data-folder registry for multi-company deployments, GSTR-2B JSON ingestion adapter, bank MT940 and CSV parser, and XML writeback jobs scheduled per CA firm client.
- **Output:** A reconciled Tally ledger across 5+ branches or 80+ CA firm client companies, GSTR-2B matched at invoice level, bank reconciliation statement clean, TDS challans reconciled to Form 26AS, and cleared voucher numbers written back to Tally so the native Tally screens show the true reconciled state.

### Tata Consumer Tetley Global Tea Reconciliation — Brand + Export

Source: https://www.terra-insight.com/insights/tata-consumer-tetley-global-tea-recon-brand-export/

- **Problem:** A listed Indian tea major running approximately Rs 5,500 crore of annual tea business across Tata Tea domestic brands and Tetley international brands across UK, Canada, US, and Australia must reconcile own-estate production in Assam and Nilgiris, auction lot procurement from Kolkata, Coonoor, and Guwahati primary centres, third-party garden supply purchase invoices, blend recipe consumption per SKU at the packing line, HSN 0902 domestic output at 5 percent GST against zero-rated export under LUT, Section 54(3) refund on export-side ITC accumulation via Rule 89(4), Ind AS 21 forex translation on Tetley UK inter-company invoicing in GBP, and RoDTEP scheme benefit per Appendix 4R on tea HSN 0902 export. Manual reconciliation across three procurement channels, one recipe pool, two output rate lines, six export destinations, and a monthly LUT-based refund cycle loses recipe compliance detail, mis-attributes packaging ITC to domestic versus export turnover, and delays the Section 54(3) refund filing by weeks against the tax period close.
- **Logic:** Build a procurement ledger keyed by channel (own estate, auction lot number, third-party garden supplier), grade, weight, moisture, and prompt or contract due date; carry auction lot broker note, warehouse tally, and rent debit as sub-ledger to the auction lot line; ingest the recipe master versioned by effective date and generate the bill-of-materials consumption at each blend run; feed the packing line SKU dispatch register against the blend output tally and expose recipe compliance variance and packing yield variance as reconciliation exceptions; split the finished-goods dispatch register into domestic HSN 0902 5 percent taxable output and export zero-rated under LUT, and further split the export register by destination country (UK, Canada, US, Australia) and by invoicing currency (GBP, CAD, USD, AUD). Compute Section 54(3) refund per Rule 89(4) formula Refund Amount = (Turnover of zero-rated supply of goods × Net ITC) / Adjusted Total Turnover monthly on Form GST RFD-01. Translate Tetley UK inter-company invoicing under Ind AS 21 at transaction, reporting, and settlement rates, and reconcile the parent INR-recorded sale against the subsidiary GBP-recorded purchase at consolidation. Extract shipping bill data from ICEGATE and reconcile RoDTEP scroll credit against the accrued scheme benefit per Appendix 4R rate.
- **Config:** Estate master with estate code, garden name, district (Dibrugarh, Jorhat, Golaghat, Coonoor, Ooty), grade output (CTC, orthodox, dust, fannings), monthly production plan; auction lot master with lot number, sale number, centre (Kolkata, Coonoor, Guwahati, Cochin, Coimbatore, Siliguri, Jorhat), broker (J.Thomas & Co, Contemporary Brokers, Carritt Moran, Paramount Tea Marketing, Forbes Ewart & Figgis), fall-of-hammer date, prompt date, warehouse tag; third-party garden supply master with supplier PAN, GSTIN, MSME flag under Section 43B(h), supply agreement grade and rejection specification, TDS payment code 1031 for Section 194Q if aggregate purchase crosses Rs 50 lakh; blend recipe master versioned by effective date with SKU-level input mix expressed as percentage draw from procurement pools; packing line master with SKU, pack size, packaging inputs (HSN 4811 laminate, HSN 4819 carton, HSN 3923 polymer film), and dispatch destination (domestic distribution, export country); LUT master on Form GST RFD-11 with validity window, export completion tracking against Rule 96A three-month rule; foreign subsidiary master with entity (Tetley UK, Tetley Canada, Good Earth US, Tetley Australia), functional currency, invoicing currency, Ind AS 21 translation reference; ICEGATE shipping bill and RoDTEP scroll feed keyed by port, invoice, HSN 0902, FOB value.
- **Output:** A monthly integrated tea reconciliation pack: procurement register by channel with auction lot broker note and prompt-settlement tally, recipe compliance and packing yield variance report by SKU and blend run, domestic dispatch and output GST at 5 percent under HSN 0902, export dispatch by destination and currency with LUT reference and Rule 96A tracker, Section 54(3) refund draft per Rule 89(4) formula with Net ITC computed net of ineligible services and capital goods, Ind AS 21 forex reconciliation between parent INR-recorded inter-company sale and subsidiary GBP or CAD or USD or AUD-recorded purchase with unrealised exchange gain or loss recognised in profit or loss (monetary items) or OCI (net investment in foreign operation), RoDTEP scroll credit reconciliation against Appendix 4R rate accrual on shipping bill dispatch, and a year-end e-BRC realisation tracker against export invoices for FEMA compliance. Traceability from any packet dispatch back to the source auction lot marker or estate godown supports the food-safety and grade-provenance discipline the Tea Board and international brand standards require.

### Tata Motors Tier-1 Supplier Reconciliation: JLR vs Domestic OEM Settlement Differences

Source: https://www.terra-insight.com/insights/tata-motors-tier1-supplier-reconciliation-india/

- **Problem:** Tier-1 suppliers to Tata Motors operate inside a three-business commercial regime — commercial vehicles at Jamshedpur / Lucknow / Pantnagar, passenger vehicles at Sanand / Pune, and JLR India at the premium tier with foreign-currency export invoicing — each with its own plant codes, FOMP running accounts, debit-note reason taxonomy and tax overlay. A ₹240 crore annual Tata book across two plants demands plant-coded settlement, programme-level decomposition, Form 168 TDS reconciliation under Section 393(1) Sl. 6(i) codes 1023/1024, and a foreign-currency overlay on the JLR leg with Section 393(2) Sl. 17 / code 1057 considerations on any associated non-resident pay-leg.
- **Logic:** Decompose each Tata settlement at the plant-code level (Jamshedpur / Lucknow / Pantnagar / Sanand / Pune / JLR India), tie each invoice and debit memo to the source vehicle programme (Prima / Signa / Ace / Intra / Nexon / Punch / Harrier / Safari / Tiago / Tigor / Altroz / Curvv / Nexon EV / programme-x JLR), classify debit reasons against the Tata-specific taxonomy, age each FOMP claim against the per-programme running account, calendar Section 34 GST credit notes per accepted debit, reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i) codes 1023/1024 against the supplier's books, and treat the JLR foreign-currency leg as a separate sub-stream with FX revaluation and Section 393(2) Sl. 17 / code 1057 overlay where applicable.
- **Config:** Tata Motors customer master with sub-records per plant code and per business (commercial vehicles / passenger vehicles / JLR India), TML SRM export mapping for daily call-off / ASN / GRN / settlement-statement / debit-memo parsing, debit-note reason taxonomy aligned to Tata Supplier Quality Excellence codes, FOMP running account per programme, programme-level cumulative shipped and margin tracker, Form 168 TDS register with Section 393(1) Sl. 6(i) codes 1023/1024 reconciliation, foreign-currency invoice sub-ledger for JLR export-bound parts, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-plant, per-business Tata settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with FOMP / tooling / quality penalty attribution, TML SRM-sourced delivery-schedule reconciliation, Form 168 TDS register reconciled to books under Section 393(1) Sl. 6(i) codes 1023/1024, foreign-currency JLR sub-ledger with FX revaluation, and Section 34 GST credit-note action queue keyed to approaching cutoff.

### Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB

Source: https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india/

- **Problem:** Section 44AB Form 3CD (migrating to Form 26 under the Income Tax Act 2025 from FY 2025-26) has 44 clauses, 25 requiring reconciliation — Clause 34 for TDS or TCS against Form 26AS, Clause 26 for Section 43B plus 43B(h) MSME 45-day tracking, Clauses 49-51 in Form 26 requiring exact counts of unreported TDS transactions. 271B penalty is 0.5% of turnover up to ₹1.5 lakh for non-filing.
- **Logic:** Clause-wise reconciliation packs are generated from books of account against statutory portals. Clause 34(c) three-way matches book TDS payable, Form 26AS, and challans on TAN plus section plus quarter. Clause 26 tracks Section 43B statutory dues aging and 43B(h) MSME invoice-to-payment within 45 days. Clause 52 in Form 26 adds AIS-referenced related-party loan reconciliation, Clause 55 attaches digital audit trail for ₹50 crore-plus turnover.
- **Config:** Form 3CD-to-Form 26 clause-mapping migration tool, TRACES plus Form 26AS integration, MSME 43B(h) 45-day tracker, AIS related-party matcher, and digital audit-trail attestation for ₹50 crore threshold.
- **Output:** Clause-wise reconciliation schedules ready for auditor upload, unreported TDS or TCS count for Clauses 49-51, MSME 43B(h) disallowance-prevention schedule, and digital audit trail evidence for Form 26 Clause 55 attestation.

### Tata Motors Supplier Portal (TML SRM): Delivery Data Extraction for Finance Teams

Source: https://www.terra-insight.com/insights/tata-supplier-portal-srm-delivery-reconciliation/

- **Problem:** Tier-1 suppliers to Tata Motors interact with TML SRM as the visible portal surface but face cross-plant complexity across Jamshedpur (CV), Pune (PV), Pantnagar and Sanand, with separate scheduling agreements, separate ASN streams, separate GRN flows, separate debit-note cycles and separate payment advices per plant. Treating the Tata customer master as a single account collapses plant-level signal and breaks debit-note reason decomposition, FOMP attribution and TDS reconciliation.
- **Logic:** Maintain a Tata customer master with sub-records per plant (Jamshedpur CV / Pune PV / Pantnagar / Sanand) and per scheduling agreement. Ingest TML SRM exports (PDF/CSV) and IDoc feeds (DELJIT / DESADV / MBGMCR) into a transport-neutral reconciliation stream. Run plant-level reconciliation per month: SA-release-ASN-GRN-debit-payment chain. Decompose debit notes by Tata's reason taxonomy (quality reject, line-stop FOMP, PPM penalty, tooling clawback, freight, premium freight). Calendar Section 34 GST credit notes against accepted quality-reject debits.
- **Config:** Tata customer master with plant-code sub-records (Jamshedpur, Pune-Pimpri, Pune-Chinchwad, Pantnagar, Sanand), scheduling-agreement and programme indexing per plant, TML SRM extract templates (call-off PDF/CSV, ASN log, GRN confirms, debit-note register, payment advice), IDoc DELJIT/DESADV/MBGMCR ingester for SAP-integrated suppliers, Tata debit-note reason taxonomy, Section 34 credit-note calendar (30 November of next FY), Section 393(1) Sl. 6(i) TDS receivable register.
- **Output:** A per-plant Tata reconciliation pack showing scheduling agreement to firm release to ASN to GRN to debit-decomposed payment per period. Cross-plant aggregation only after plant-level reconciliation is closed. Section 34 GST credit-note action queue keyed to 30 November next-FY cutoff. Section 393(1) Sl. 6(i) TDS deducted reconciled to Form 26AS. Year-end audit position defensible from IDoc archive plus TML SRM extract trail.

### Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025

Source: https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india/

- **Problem:** Assessment Year (AY 2026-27) is replaced by Tax Year (Tax Year 2025-26) from April 1, 2026. Historical comparisons, correction statements, and ITR forms need consistent labelling across both conventions without confusing which period is being compared.
- **Logic:** Maintain a mapping table converting every AY label to its Tax Year equivalent. Tag every reconciliation record with both labels during the cross-over period to support historical lookups. Validate trend reports to confirm the same period is compared across both labels.
- **Config:** Tax Year used for new filings from April 1, 2026 onwards across ITR, TDS returns, and certificates. Assessment Year retained for any correction statement or appeal that references a pre-2026 period.
- **Output:** Period-consistent trend reports, correctly labelled historical comparisons, and ITR-ready period references that prevent two different periods being treated as the same.

### TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B

Source: https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation/

- **Problem:** Section 52 of the CGST Act requires e-commerce operators to collect 1% TCS (0.5% CGST plus 0.5% SGST intra-state or 1% IGST inter-state) and file GSTR-8 by the 10th of the following month. Sellers on Amazon, Flipkart, Meesho, Swiggy, and Zomato cannot claim TCS credit in GSTR-3B until the operator's GSTR-8 auto-populates the GSTR-2B — any over-claim triggers scrutiny.
- **Logic:** Three-source reconciliation matches (1) TCS deducted in the operator settlement report, (2) TCS auto-populated in seller's GSTR-2B Part II from GSTR-8, and (3) TCS in Form 26AS Part F. Matching keys are operator GSTIN plus seller GSTIN plus tax period plus net taxable value. Unmatched TCS is parked as deferred credit until the operator files or corrects GSTR-8.
- **Config:** Per-operator settlement-report ingestion, GSTR-8 filing-status tracker (10th-of-month cut-off), and 14th-of-month GSTR-2B readiness check.
- **Output:** Claimable TCS schedule aligned to GSTR-2B for GSTR-3B offset, deferred TCS carry-forward register, seller-support ticket list for GSTR-8 corrections, and Form 26AS Part F cross-check for income tax.

### TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses

Source: https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india/

- **Problem:** Tour operators and forex dealers must collect TCS on LRS remittances at slab-based rates (0.5% to 20%) that change at the ₹7 lakh cumulative threshold per PAN per financial year, making per-transaction TCS calculation dependent on running totals.
- **Logic:** Track cumulative remittance per PAN per FY, apply slab-based TCS rate based on purpose and cumulative amount, reconcile TCS collected against challan deposits and Form 27EQ returns.
- **Config:** Section 206C(1G) rates — education loan 0.5% above ₹7L, medical/education 5% above ₹7L, overseas tour 5% up to ₹7L and 20% above, other 20% above ₹7L. RBI LRS limit $250,000/year. Quarterly Form 27EQ.
- **Output:** PAN-wise cumulative remittance tracker, slab-split TCS calculation register, Form 27EQ reconciliation, and buyer TCS credit report for income tax return.

### TCS on Luxury Goods Reconciliation in India: Section 206C Matching

Source: https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india/

- **Problem:** Sellers of motor vehicles above ₹10 lakh and goods exceeding ₹50 lakh cumulative per buyer must collect TCS under Section 206C, with threshold tracking per buyer PAN per financial year.
- **Logic:** Track cumulative sales per buyer PAN to detect ₹50L threshold crossing, apply TCS at specified rates per goods category, reconcile TCS collected against TCS deposited via challan and Form 27EQ filed.
- **Config:** Section 206C(1F) at 1% on motor vehicles above ₹10L, 206C(1H) at 0.1% above ₹50L cumulative (abolished April 2025), quarterly Form 27EQ filing, interest 1%/month on late deposit.
- **Output:** Buyer-wise cumulative sales tracker, TCS collection register, challan-to-Form 27EQ reconciliation, and buyer TCS credit confirmation for Form 26AS.

### Section 394 TCS on Scrap Sale by Auto Component Manufacturers: Payment Code 1071 (FY 2026-27)

Source: https://www.terra-insight.com/insights/tcs-scrap-sale-section-394-auto-component-india/

- **Problem:** Auto-component manufacturers generate scrap as a structural byproduct of every press, forge, machine and casting operation — stamping skeleton scrap from press lines, forging flash from drop hammers, machining swarf and chips from turning centres, casting scrap from rejection and melt loss. Sale of this scrap attracts Tax Collected at Source at 1% under Section 394 of the Income Tax Act 2025 (payment code 1071) from 1 April 2026 onwards, replacing legacy Section 206C(1). The compliance surface is small per-transaction but high in volume — a Tier-1 with ₹4 to ₹6 crore of annual scrap sale across 4 to 8 scrap dealers generates 100+ TCS transactions per year, each requiring monthly deposit, quarterly Form 27EQ filing, Form 27D buyer-side certificate, and a separate accounting lineage from the unrelated GST Section 52 TCS on e-commerce.
- **Logic:** Maintain a scrap-sale ledger keyed by buyer PAN, scrap category (stamping skeleton / forging flash / machining swarf / casting / sprue), sale date, sale value pre-GST, TCS collected at 1% under Section 394 code 1071. Run the monthly deposit engine: aggregate all TCS collected within the month, deposit by 7th of next month against the seller's TAN, generate challan with code 1071. Run the quarterly Form 27EQ filing engine. Issue Form 27D to each buyer within 15 days of Form 27EQ due date. Maintain a parallel cross-era lineage for any FY 2025-26 transactions still in adjustment cycle under legacy Section 206C(1) code 6CR.
- **Config:** Scrap-buyer master keyed by PAN with TCS-applicability flag, scrap-category taxonomy (stamping / forging / machining / casting / moulding scrap), sale ledger with date / value / category / buyer-PAN / TCS-collected, Section 394 monthly deposit calendar with 7th-of-next-month trigger and 30th-April special case for March collections, Form 27EQ quarterly filing calendar, Form 27D issuance queue with 15-day post-27EQ deadline, cross-era handling rule routing pre-2026-04-01 transactions to legacy code 6CR and post-2026-04-01 transactions to new code 1071.
- **Output:** A scrap-sale TCS ledger with per-transaction Section 394 code 1071 collection records, a monthly TCS deposit auto-prep file with challan code 1071 and TAN reference, the Form 27EQ quarterly export file for TRACES upload, a Form 27D issuance queue ranked by buyer, a cross-era reconciliation register showing legacy Section 206C(1) code 6CR vs new Section 394 code 1071 lineages, and an audit-defensible trail linking every scrap-sale invoice to its TCS deposit and Form 27D record.

### TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger

Source: https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation/

- **Problem:** Restaurant aggregators including Zomato and Swiggy collect 1% TCS under Section 52 of the CGST Act on net taxable supplies, but the credit reaches the restaurant only via the aggregator's monthly GSTR-8 filing, auto-populates into a non-ITC section of the GST electronic cash ledger, and must be claimed and cleared against output GST in GSTR-3B — a multi-step flow that is repeatedly confused with income-tax TCS or treated as ITC, leading to unclaimed credits and incorrect output-tax offset.
- **Logic:** Pull the aggregator settlement file with restaurant-wise net taxable supply per month, accrue Section 52 TCS receivable in the cash-ledger sub-account at 1% of net taxable supply with intra-state CGST/SGST split or inter-state IGST, match against the auto-populated GSTR-8A view on the GST portal, accept the entries to flow into the electronic cash ledger, and utilize the cash-ledger balance to offset output GST in the same period's GSTR-3B.
- **Config:** Aggregator settlement-file connector with monthly net-taxable-supply extraction; intra-state vs inter-state TCS classifier with CGST/SGST/IGST split; GSTR-8A reconciliation interface keyed to aggregator GSTIN and month; refund-period reversal logic to adjust net taxable supply across calendar-month boundaries; cash-ledger utilization mapper to offset GSTR-3B output liability.
- **Output:** A reconciled Section 52 TCS receivable that ties every aggregator GSTR-8 entry to a restaurant cash-ledger credit, every refund reversal to the correct calendar month, and every cash-ledger balance to a GSTR-3B utilization line — with no leakage of unclaimed credits and no confusion with income-tax TCS.

### Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies

Source: https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation/

- **Problem:** Every Section 195 foreign remittance requires Form 15CA online declaration before the AD bank processes the wire, and Form 15CB CA certificate for remittances above ₹5 lakh per purpose code or where a DTAA benefit is claimed. Across a year with dozens of remittances, mismatches between 15CA records, TDS challans, AD bank logs, and Form 27Q entries are common and expose the remitter to Section 276B prosecution and Section 201 interest.
- **Logic:** Link every outward remittance to a unique 15CA acknowledgment, a 15CB CA certificate (where above threshold), a TDS challan at the rate certified, and a Form 27Q entry. Enforce one 15CA per remittance, match the AD bank's processed amount and date to the 15CA record, and reconcile the challan rate and amount against the 15CB determination before quarter close.
- **Config:** Remittance register with 15CA acknowledgment, 15CB reference, challan ID, and 27Q quarter fields per payment. One-to-one remittance-to-15CA rule. Threshold logic routing above-₹5-lakh remittances to 15CB.
- **Output:** Every foreign remittance backed by matching 15CA, 15CB, challan, AD bank record, and Form 27Q entry, zero Section 276B exposure, and an auditor-ready reconciliation file for the full year.

### TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1

Source: https://www.terra-insight.com/insights/tds-2026-migration-checklist-india/

- **Problem:** The shift to Income Tax Act 2025 on April 1, 2026 requires pre-migration closure of legacy correction windows, vendor master updates, GL code loads, cut-over planning, and dual-mode testing. Without a structured checklist, finance teams risk missing correction deadlines and carrying incorrect configurations into production.
- **Logic:** Sequence the migration across four phases. Close time-barred correction windows for FY 2018-19 through FY 2022-23 before March 31, 2026. Update vendor master and chart of accounts with payment code placeholders. Decommission Section 206AB and 206CCA compliance filters. Run end-to-end cut-over and test cycles.
- **Config:** Cut-over window targeted end-March 2026. Dual-mode reporting enabled on go-live so the same source data produces both legacy and new-era outputs. Read-only history retained for 206AB and 206CCA filters.
- **Output:** Go-live readiness checklist, pre-migration correction completion report, vendor master gap report, and cut-over test results covering ERP master updates, GL code loads, reconciliation configuration, and end-to-end test runs.

### Section 393(1) Sl. 1(ii) and Payment Code 1006: Hotel TDS Reconciliation on Domestic OTA Commission

Source: https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation/

- **Problem:** Hotels paying commission to MakeMyTrip, Goibibo, Yatra, and OYO domestic must deduct 2% TDS on commission (rate reduced from the legacy 5% under 194H), but the deduction code changed on April 1, 2026 — Section 194H is replaced by Section 393(1) Sl. 1(ii) with payment code 1006. Cross-era cases mix old and new codes in the same matching run, e-commerce operator bookings under the OTA's own withholding must be excluded from 393(1) Sl. 1(ii), and the hotel's challan, Form 16A, Form 131, and the OTA's Form 168 all must reconcile at deductee level.
- **Logic:** For every commission invoice, classify whether the booking is in agency mode or e-commerce operator mode. Apply 393(1) Sl. 1(ii) and code 1006 only to agency-mode commission. Tag each deduction with its deduction date, route to the correct section based on date — pre-April 1 entries to legacy 194H, post-April 1 to 393(1) Sl. 1(ii). Match the hotel's Challan 281 to Form 26Q, then Form 131, then the OTA's Form 168 at deductee level. Keep INR commission and foreign-currency-equivalent legs on separate ledger lines so forex variance does not contaminate the TDS base.
- **Config:** OTA settlement file connector with mode flag (agency vs e-commerce operator); commission invoice ledger with deduction-date tag; section mapping master with both 194H and 393(1) Sl. 1(ii) entries; Challan 281 link to Form 26Q line item; Form 131 generator at deductee level; reconciliation rule that excludes e-commerce operator bookings from the 393(1) Sl. 1(ii) calculation.
- **Output:** A reconciled commission TDS ledger where every domestic OTA invoice is tagged with the correct section and code on its deduction date, the hotel's Challan 281 reconciles to Form 26Q, Form 131 issued to each OTA matches Form 168 entries at the OTA's end, and cross-era cases route correctly without manual intervention.

### Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1035

Source: https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation/

- **Problem:** Restaurant aggregators like Zomato and Swiggy now deduct 0.1% TDS under Section 393(1) Sl. 8(v) of the Income Tax Act 2025 with payment code 1035 (down from the legacy 1% under Section 194O), but settlement files cross the FY 2025-26 to FY 2026-27 era boundary with mixed old-code and new-code deductions that must reconcile to two separate annual statements — final Form 26AS for the legacy period and Form 168 for the new regime.
- **Logic:** Pull the aggregator settlement file with order-level gross sale value, classify each deduction by deduction date — pre-April 2026 to legacy 194O, post-April 2026 to Section 393 code 1035 — accrue TDS receivable on gross order value not net payout, post each deduction to the matching tax-period sub-ledger, and reconcile against Form 168 for FY 2026-27 with deductor TAN as the matching key.
- **Config:** Aggregator settlement file connector with order-level gross value extraction; cross-era TDS classifier keyed to deduction date; payment code 1035 mapper for Section 393 entries; Form 168 download integration with TAN-based matching; legacy Form 26AS connector for residual 194O credits; refund-period reversal logic to adjust original TDS base when orders are refunded across settlement cycles.
- **Output:** A reconciled TDS receivable ledger where every Section 393 deduction in the aggregator settlement file ties back to a Form 168 entry under payment code 1035, every legacy 194O deduction reconciles to final Form 26AS, and the cross-era split is auditable at the order-line level for the restaurant's quarterly advance tax computation.

### TDS Challan Mismatch: How to Identify and Resolve Errors

Source: https://www.terra-insight.com/insights/tds-challan-mismatch-resolution/

- **Problem:** TDS challan mismatches — wrong BSR code, wrong serial number, or amount difference between the TDS return and the OLTAS record — leave the challan marked unmatched on TRACES and block Form 26AS from updating for the deductee. The money has been paid, but the credit does not reach the recipient's tax account.
- **Logic:** Classify each unmatched challan into one of three types — BSR code error, serial number error, or amount discrepancy — by comparing the TDS return entry against the OLTAS record. Route each type to a C2 correction return filed by the deductor on TRACES. After processing, confirm the challan status on TRACES and verify the Form 26AS update within 3 to 7 business days.
- **Config:** Typed variance classifier linking return entry to OLTAS challan. C2 correction return routing queue. Post-correction Form 26AS verification tracker.
- **Output:** Unmatched challans cleared through typed C2 corrections, Form 26AS credits restored to deductees, and a full audit trail of deductor actions and TRACES processing timestamps.

### TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26

Source: https://www.terra-insight.com/insights/tds-compliance-calendar-india/

- **Problem:** TDS compliance in India runs on monthly deposit deadlines (7th of following month, 30 April for March), quarterly return dates (31 July, 31 October, 31 January, 31 May), and certificate issuance windows. Missing any deadline triggers 1.5 percent per month interest under Section 201(1A), ₹200 per day under Section 234E, or Section 271H penalties capped at the total TDS amount for the quarter.
- **Logic:** Build a month-by-month compliance calendar linking deduction, deposit, challan verification, quarterly return filing, certificate issuance, and reconciliation windows. At each milestone, run Form 26AS reconciliation against the TDS receivable ledger, flag unmatched entries within the deductor's correction window, and file correction statements before time-bars fall.
- **Config:** Calendar master with 12 monthly deposit dates, 4 quarterly return dates, and 2 certificate windows. Auto-triggered reconciliation runs keyed to post-return due dates. Interest and penalty accrual logic per Section 201(1A) and 234E.
- **Output:** Zero missed deposits or returns, Section 234E and 201(1A) accruals limited to unavoidable exceptions, and reconciled Form 26AS after every quarterly return with variances routed to deductors inside their correction windows.

### TDS Correction Return: How to Fix Errors After Filing

Source: https://www.terra-insight.com/insights/tds-correction-return-process/

- **Problem:** Errors in an accepted TDS return can only be fixed by filing the correct correction return type on TRACES — C1 for deductee PAN, C2 for challan details, C3 for deductee or salary data, C4 for salary details in 24Q, and C5 to cancel a statement. Using the wrong type leads to rejection and extends the Form 26AS mismatch for the deductee.
- **Logic:** Classify each error by the field that needs changing — PAN (C1), challan BSR/serial/amount (C2), deductee or salary record (C3/C4), or statement cancellation (C5) — and download the Conso file from TRACES as the source of truth. Apply changes in NSDL RPU, validate through FVU, and upload the .fvu file. Confirm processing on TRACES within 3 to 7 business days and verify the Form 26AS update.
- **Config:** Error-to-correction-type map with required field changes. Conso file retrieval workflow keyed by TAN and quarter. Post-correction Form 26AS verification check.
- **Output:** Correctly routed correction return accepted on first submission, 3 to 7 day Form 26AS refresh for the affected deductee, and a closed audit log linking original return, correction type, and TRACES processing timestamp.

### TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23

Source: https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline/

- **Problem:** TDS correction statements for FY 2018-19 through FY 2022-23 become permanently time-barred on March 31, 2026 under the Section 200 limitation. PAN errors, challan mismatches, amount discrepancies, and wrong section codes for these five years cannot be rectified after that date, exposing deductors to Section 201 demand notices, 1.5% per month interest, and Section 40(a)(ia) disallowance.
- **Logic:** Pull Form 26AS and AIS for every deductee-year in the FY 2018-19 to FY 2022-23 range, compare against the deductor's 26Q and 27Q returns, and classify each mismatch as PAN error, challan mismatch, amount discrepancy, section code error, or deductee-master error. Route each typed variance to its correction statement queue on TRACES before the March 31 cut-off.
- **Config:** Variance taxonomy with typed correction codes. Deadline tracker per financial year. TRACES correction statement routing queue with ageing indicators against March 31, 2026.
- **Output:** A closed punch list of filed correction statements, refreshed Form 26AS entries matching the deductor ledger, and a documented audit trail of every FY 2018-19 to FY 2022-23 mismatch that was rectified before the permanent time-bar.

### TDS on Cotton/Yarn Freight under Section 194C Code 1001 for Textile

Source: https://www.terra-insight.com/insights/tds-cotton-yarn-freight-section-194c-code-1001-textile/

- **Problem:** A Karur or Tiruppur textile principal running quarterly freight of ₹8 to ₹10 lakh across 40 to 50 truck loads from Coimbatore or Erode cotton spinners must deduct TDS under Section 393(1) Sl. 4 at either code 1001 (1 percent for Individual/HUF truck-owner-operator) or code 1002 (2 percent for transport partnership/LLP/company), apply the transport-contractor exemption where a 10-vehicle declaration is on file, track the ₹30,000-single and ₹1,00,000-aggregate PAN thresholds across all quarterly payments to the same transporter, resolve the CIF-versus-FOB freight-invoice-recipient question that decides whether the brand deducts at all, and reconcile Form 26Q filings against Form 26AS credit at each transporter's PAN. Manual freight-vendor classification and threshold tracking commonly produce Section 201(1) short-deduction defaults, blocked ITC on freight GST at the transporter, and CPC-TDS assessment notices at year-end.
- **Logic:** Build a transporter vendor master keyed to PAN with entity-type flag (Ind/HUF versus other resident), 10-vehicle-declaration flag with expiry date, and expected payment code (1001, 1002, or nil-deduction with exemption reason code). Ingest every freight invoice and match against the vendor master to derive the expected TDS deduction; running aggregate per PAN per FY tracks the ₹1,00,000 threshold and flips the deduction obligation at the payment that crosses it. Every payment carries a documentation walk-through to confirm CIF-versus-FOB (is the freight invoice raised to the brand or to the consignor); brand-invoiced freight enters the TDS workflow, consignor-invoiced freight is booked as an embedded goods cost and skips the workflow. Form 26Q quarterly return generation reconciles against the freight ledger and the deducted-TDS challan register before filing; post-filing reconciliation matches Form 26AS credit at each transporter PAN and surfaces classification defaults.
- **Config:** Transporter vendor master with PAN, GSTIN, entity type (Individual, HUF, Partnership, LLP, Private Limited, Cooperative, AOP), 10-vehicle declaration on-file flag and expiry date, expected 393(1) payment code (1001, 1002, or nil with reason code for transport exemption); freight invoice register with invoice reference, transporter PAN, gross freight, CIF/FOB flag (freight invoice raised to consignee or consignor), consignment reference to the underlying yarn dispatch challan; running aggregate table per PAN per FY tracking the ₹1,00,000 aggregate threshold; Section 393(1) Sl. 4 code lookup with legacy Section 194C mapping (1001 = Ind/HUF 1 percent, 1002 = other 2 percent, 1014 = specialised carrier); Form 26Q filing calendar (Q1 due 31 July, Q2 due 31 October, Q3 due 31 January, Q4 due 31 May); Form 26AS reconciliation feed at each transporter PAN post-filing.
- **Output:** A quarterly freight-TDS reconciliation pack: freight ledger by transporter PAN with gross freight, expected code, expected deduction, actual deduction, and variance; running aggregate per PAN with ₹1,00,000 threshold crossings flagged; 10-vehicle-declaration audit trail with expiry alerts for renewal; Form 26Q draft filing populated by transporter with correct payment code and threshold-honoured deductions; post-filing Form 26AS reconciliation showing credit posted at each transporter PAN with code-classification defaults surfaced for corrective 26Q revision; CIF/FOB documentation trail per freight invoice explaining why the brand did or did not deduct.

### TDS Credit Leakage in India: How Form 26AS / Form 168 Reveals Missing Deductions

Source: https://www.terra-insight.com/insights/tds-credit-leakage-form-26as-india/

- **Problem:** Indian services businesses with significant TDS-bearing revenue silently lose 8 to 14% of TDS credits because the deductor never filed, used the wrong PAN, used the wrong section code, used the wrong period, or filed past the deductee's rectification window. The cross-era complication of FY26 spanning legacy Section 194x and new Section 393 / 394 payment-code 1001-1092 makes the reconciliation harder. Books-side TDS receivable shows a number, but Form 26AS plus Form 168 together show less, and the gap is the leakage.
- **Logic:** Maintain a TDS receivable register keyed by customer PAN, deductor TAN, invoice number, gross taxable amount, contracted TDS rate, deduction date, and expected payment code 1001-1092 plus legacy 194x reference. Daily-pull Form 26AS and Form 168 for the deductee PAN across all relevant assessment periods. Match each books-receivable to the 26AS / 168 entry by PAN, period, payment code, and amount. Age every unmatched receivable in 30 / 60 / 90 / 180-day buckets. Map each bucket to a specific recovery action (deductor confirmation, escalation, rectification filing via Form 131 or Form 141).
- **Config:** TDS receivable ledger with deductor TAN, deductee PAN, invoice reference, deduction date, payment code 1001-1092, cross-era 194x reference, contracted rate. Daily 26AS / 168 pull pipeline against deductee PAN. Match-engine rules with PAN-period-amount-code primary keys and amount-fuzzy fallback. Ageing buckets 30 / 60 / 90 / 180 days. Action playbook by bucket. Rectification queue feeding Form 131 / Form 141. Audit trail capturing every match, every claim, every rectification request and outcome.
- **Output:** A daily TDS leakage dashboard by customer with rupee receivable, days outstanding, and recovery probability band. A weekly deductor-side escalation pack with PAN, period, and amount detail ready to email. A monthly 168 match-rate trend tracking books-to-statement reconciliation coverage. A quarterly recovery report showing rupees recovered, rupees rectification-filed, rupees structurally lost — feeding the Discovered Money register on the tax-deduction class.

### TDS Credit Recovery: Operating Process for Indian Receivers

Source: https://www.terra-insight.com/insights/tds-credit-recovery-26as-form-168-india/

- **Problem:** Indian receivers routinely carry a TDS receivable in their books that does not fully reconcile to Form 26AS or to the deductor's Form 168 statement. Some of the gap is deductor delay (tax withheld under Section 393 but not yet deposited under Section 394). Some is misquoted PAN or section code in the Form 168 filing. Some is structurally orphan — withheld and never deposited. Without a monthly operating process the gap ages out, Section 199 credit is under-claimed at ITR time, and the receivable line on the balance sheet accumulates a structural loss that nobody owns.
- **Logic:** Run a monthly three-way reconciliation between books TDS receivable, Form 26AS reflection, and Form 168 statement view. Classify every gap by cause — deductor delay, PAN mismatch, section mismatch, rate mismatch, structurally orphan. Apply a four-tier deductor-chase escalation matrix anchored to Section 393 and Section 394 of the Income Tax Act 2025 — T+15 polite, T+30 firm with regulatory citation, T+45 board-of-directors letter, T+60 legal notice. Operate a Discovered Money register with status field per row. Refile revised ITR where orphan TDS is later recovered. Provision structurally lost balances after four quarters of unsuccessful escalation.
- **Config:** Monthly reconciliation calendar with named owner (tax controller / TDS desk). Three-way match query template for books vs Form 26AS vs Form 168. Gap-classification library with five categories and standard action per category. Four-tier escalation template library with regulatory citations and legal-notice draft. Section 199 credit-claim worksheet for ITR computation. Revised return SOP for orphan-TDS recovery. Quarterly audit-committee report template with rupees orphan, rupees recovered, rupees provisioned.
- **Output:** A monthly Discovered Money register row for every orphan-TDS gap with classification, owner, SLA, and status. A quarterly audit-committee pack showing TDS receivable at start, additions, recoveries, structural losses, and net balance. An annual Section 199 credit claim worksheet feeding the ITR computation. A revised-return queue for in-cycle recoveries identified after ITR filing. A trend line showing recovery rate quarter-over-quarter as the program matures.

### TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match

Source: https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india/

- **Problem:** Enterprise pays tax twice when Form 26AS credits don't match TDS receivable ledger. 18% of Indian filers experience refund rejections from this mismatch.
- **Logic:** Sequential recovery stack: deductor C3/C5 correction → Section 154 rectification (4 years) → Section 119(2)(b) condonation (5 years) → ITR-U updated return (24 months with 25-50% additional tax).
- **Config:** CBDT Instruction 5/2013 for Section 205 claims. Circular 11/2024 for condonation. 2-year correction limit under new Act Section 397(3)(f).
- **Output:** Recovered TDS credits in Form 26AS, reduced Section 143(1) demand notices, and elimination of duplicate tax payments on reconciled receivables.

### TDS Demand Notice Under Section 200A: How to Reconcile and Respond

Source: https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india/

- **Problem:** A Section 200A intimation is auto-generated after TDS return processing and itemises short deduction, Section 201(1A) interest (1 percent per month pre-deduction plus 1.5 percent per month pre-deposit), Section 234E late fees (₹200 per day capped at quarterly TDS), and challan or PAN mismatches. Each line requires a different remediation path — correction statement versus Section 154 rectification versus challan deposit.
- **Logic:** Download the intimation and classify each demand line by type — interest, late fee, short deduction, or challan/PAN mismatch. Route challan mismatches and PAN errors to TRACES correction statements (C2 or C1), route genuine shortfalls to a new challan plus correction return, and route CPC computation errors to a Section 154 rectification filed within 4 years. Deposit accrued interest with the shortfall challan.
- **Config:** Demand-line classifier mapping to C1/C2/C3 correction route, new challan route, or Section 154 rectification. Interest calculator implementing 1 percent and 1.5 percent monthly logic. Ageing counter against the 4-year Section 154 window.
- **Output:** Each 200A line item closed through the correct remediation route, revised intimation within 3 to 7 working days of TRACES processing, and documented audit file showing demand-line-to-correction traceability.

### TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges

Source: https://www.terra-insight.com/insights/tds-esop-section-192-india/

- **Problem:** ESOP TDS under Section 192 is triggered at exercise (not grant and not sale) on the perquisite value — FMV on exercise date minus grant price — and must be added to salary in Form 24Q for that quarter. A 50-employee plan with three vesting tranches can produce up to 150 separate TDS events, each of which is missed when ESOP is treated as an annual exercise rather than a transaction-level process.
- **Logic:** Capture every exercise event with the required FMV reference — merchant banker certificate for unlisted Indian shares, NSE/BSE average for listed shares, foreign exchange price plus RBI reference rate for parent-company grants. Add the perquisite to the employee's salary for the exercise quarter, deduct TDS at slab rate, and post to Form 24Q. Reconcile the ESOP register against Form 24Q line-by-line at quarter close.
- **Config:** Exercise event register linked to employee master. FMV source rules by company type. IndAS 102 expense vs Section 192 TDS timing map for cross-period mismatch reporting.
- **Output:** Form 24Q entries that match the ESOP register one-for-one, Form 16 Part B showing the correct perquisite under Section 17(2), and a clean audit trail for every exercise including resignation-window and cross-border grant cases.

### TDS on Foreign Agent Commission for Auto-Component Exports: Section 393(2) + Payment Code 1057

Source: https://www.terra-insight.com/insights/tds-foreign-agent-commission-auto-component-export-india/

- **Problem:** An Indian Tier-1 auto-component exporter paying €100,000 to €500,000 of annual sales commission to overseas agents in Germany, the UK, Italy, Spain, the US, Japan, Singapore, the UAE and others on its export programme to European, North American and Asian OEMs must, from 1 April 2026, work each remittance through Section 393(2) of the Income Tax Act 2025 at payment code 1057 (replacing legacy Section 195) — applying the DTAA override on Article 7 business profits where supported by a no-PE certification, falling back to domestic Section 9 chargeability where no DTAA cover exists, executing Form 15CA / 15CB filing on every remittance regardless of withholding outcome, retaining the no-PE certification and the CA's Form 15CB on file, and reconciling the outbound TDS register (where applicable) in the supplier's own quarterly Form 168 with cross-era handling of any legacy Section 195 entries from FY 2025-26.
- **Logic:** Tag every foreign agent in the master with country of residence, DTAA cover status, no-PE certification on file (Y / N with date), Form 15CB issued by CA (Y / N per remittance), and Form 15CA Part filed (A / B / C / D); for each commission remittance, work the five-decision tree — (1) is the agent a non-resident under Section 6 of the Act, (2) is the income chargeable under Section 9, (3) does a DTAA override the chargeability under Article 7, (4) is a no-PE certification on file, (5) what Form 15CA Part applies; deduct TDS at the applicable rate under code 1057 where withholding bites; deposit on the prescribed challan; file Form 15CA before remittance; file Form 168 quarterly for the outbound deductions; issue the TDS certificate to the agent; maintain a cross-era 195 ↔ 413 cross-reference for FY 2025-26 entries.
- **Config:** Foreign-agent master with country, DTAA cover (Article 7 reference), legal form, no-PE certification register with annual renewal, CA panel for Form 15CB issuance, AD-bank remittance calendar, Form 15CA filing checklist by Part, outbound TDS register at code 1057, monthly TDS challan calendar, quarterly Form 168 outbound register, TDS certificate template for foreign agents, and cross-era 195 / 413 mapping for legacy entries.
- **Output:** A live foreign-agent dashboard per agent showing DTAA cover, no-PE certification status, Form 15CA / 15CB filing trail per remittance, withholding decision per remittance, outbound TDS deducted at code 1057, challan deposit confirmation, Form 168 outbound register, the cross-era 195 / 413 mapping, and an audit-defensible trail of the chargeability determination on every remittance.

### TDS Reconciliation Failure Modes Against Form 26AS and Form 168: Every Failure Mode That Turns Into a Section 200A Notice

Source: https://www.terra-insight.com/insights/tds-form-26as-reconciliation-failure-modes-india/

- **Problem:** A mid-sized Indian enterprise closing its FY 2026-27 books must reconcile every TDS receivable line in the general ledger against the deductor's credit in Form 26AS and — from FY 2026-27 — the consolidated Form 168 annual TDS statement, at the PAN-and-four-digit-code level under Section 393 of the Income-tax Act 2025, while simultaneously carrying open FY 2025-26 residual credits under the legacy Section 194x identifiers through the 31 March 2027 correction window. Fourteen distinct failure modes — cross-era code confusion, PAN mismatch triggering Section 206AA at 20 percent, TDS deducted on GST-inclusive amount, Q4-to-Q1 boundary misclassification, deductor short-deduction, TRACES pull cadence errors, unaged unresolved bucket, undocumented cutoff, self-review by preparer, intercompany mis-routing, Form 168 amendment drift, Section 195 mis-tagging, Section 194Q threshold miss, and post-facto reclassification — each maps to a Section 200A demand-notice or Section 143(1) intimation-adjustment exposure that the reconciliation must catch before the correction window closes.
- **Logic:** Anchor the reconciliation function definition as a quarterly PAN-and-code-level match between the general ledger TDS receivable subledger and the TRACES-pulled Form 26AS extract (transitioning to the consolidated Form 168 for FY 2026-27), with a residual FY 2025-26 window layered on the legacy Section 194x identifiers. Walk every open variance through the 6P cause taxonomy (People, Policy, Process, Portal, Period, Partner) to identify the class of failure. Rate each on the anchored Severity-Occurrence-Detection scale with the Section 200A demand-notice as the Severity-9 anchor and a permanent credit loss under Section 155 processing constraints as the Severity-10 anchor. Prioritise remediation on Severity-first Action Priority rather than a multiplicative Risk Priority Number, so the Class 5 (timing) cross-era failure and the Class 11 (evidence) Rule 31A documentation failure do not get downgraded by low occurrence estimates.
- **Config:** Deductee's TDS receivable subledger keyed to invoice number, deductor PAN, gross invoice value, GST component (CGST + SGST or IGST), pre-GST base, applicable Section 393 code (for FY 2026-27 payments) or legacy Section 194x identifier (for FY 2025-26 payments), code rate, expected TDS, and actual TDS deducted at source per the deductor's remittance advice; TRACES login and Form 26AS pull cadence documented at fortnightly or monthly intervals; Form 168 pull cadence documented at quarterly intervals from FY 2026-27; aging bucket schema on unresolved variances at 30 / 60 / 90 / 180 days with escalation trigger at 180 days; PAN validation utility integrated with the Income-tax Department's PAN validation API for real-time inoperative-PAN detection under Rule 114AAA; ratio-test workbook computing TDS receivable to pre-GST invoiced revenue by vendor and by code quarter over quarter; cross-era mapping table maintaining Section 194x-to-Section 393 code equivalents for every open FY 2025-26 residual line.
- **Output:** A quarterly TDS reconciliation pack: opening balance of TDS receivable by deductor PAN by code, additions during the quarter with expected TDS computed on pre-GST base times code rate, reductions on credits reflected in Form 26AS or Form 168 with variance flagged where actual TDS credited differs from expected, closing balance carried forward, aging queue on unresolved variances with 180-day escalation trigger fired to the group controller, ratio-test dashboard by vendor and by code with quarter-over-quarter drift highlighted, cross-era residual schedule for open FY 2025-26 lines with a 31 March 2027 correction-window countdown, and a documented Rule 31A / CARO 2020 audit trail for every reconciliation exception showing the resolution path and the deductor communication log. The reconciliation feeds directly into the deductee's own advance-tax computation under Sections 234B and 234C, closing the loop between deductor-side reconciliation discipline and deductee-side tax liability.

### TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation

Source: https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197/

- **Problem:** A Section 197 lower deduction certificate is valid only from the date the deductor receives and verifies it on TRACES. A consulting firm with 40 clients must distribute one certificate to every deductor, track each deductor's first payment at the lower rate, and reconcile Form 26AS entries where some clients deducted at the reduced rate and others remained on the standard rate.
- **Logic:** Record three dates per deductor — certificate issue date by TRACES, date furnished to the deductor, and first payment date at the lower rate — and flag any payment at the reduced rate before the verification date as a short-deduction exposure. Update the TDS receivable ledger to the certificate rate for future invoices to that deductor. Pull Form 26AS and classify each entry against the expected rate (standard, transition, or certificate-reduced) to surface deductors that missed the certificate.
- **Config:** Per-deductor certificate register with issue/furnish/first-payment dates. Expected-rate ledger field that shifts from standard to certificate rate on the furnish date. Exception rule flagging Form 26AS entries at the standard rate post furnishing.
- **Output:** Deductors correctly applying the reduced rate from verification date, identified deductors that need a revised Form 16A (or Form 131 post-April-2026), and a closed exposure log for any pre-furnishing over-deduction claim.

### Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India

Source: https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india/

- **Problem:** A consulting firm or professional with 20 or more clients receives TDS credits from many deductors under multiple sections (194J, 194C, 194I, 194H), each filing independently at different times and occasionally misclassifying sections. The recipient's Form 26AS aggregates everything, but late filings, section errors, and PAN slips prevent simple aggregate matching.
- **Logic:** Parse Form 26AS XML into rows by deductor TAN, section code, quarter, and amount, and match each row to invoices in the income ledger using TAN plus section plus amount as keys. Classify unmatched rows as section misclassification, late-filed-return timing, or PAN error and route each to a deductor correction statement. Aggregate at the client PAN level for multi-TAN clients.
- **Config:** TAN-to-client master linking multi-branch deductors to economic clients. Per-invoice expected section and TDS stored in the income ledger. Typed variance classifier for section misclassification, timing, and PAN errors.
- **Output:** Every Form 26AS entry traced to an invoice or a documented deductor error, no phantom credits claimed against unmatched 26AS rows, and complete TDS credit claimed in the ITR with an auditor-ready trace file.

### TDS on Freight and Transport for Auto-Component Suppliers: Section 393 + Payment Codes 1023/1024 (FY 2026-27)

Source: https://www.terra-insight.com/insights/tds-on-freight-transport-auto-component-section-194c-india/

- **Problem:** An Indian Tier-1 auto-component supplier paying ₹4 to ₹6 crore of annual inbound freight to Maruti, Hyundai or Tata Motors plants runs three to five distinct transporter classes — fleet operators (companies and LLPs), small owner-operators (individual with ten or fewer trucks under the declaration exemption), freight forwarders (commission and pure freight split), GTA-classified carriers with RCM GST overlay, and non-GTA carriers under forward GST — and from 1 April 2026 must deduct TDS under Section 393(1) Sl. 6(i) of the Income Tax Act 2025 at payment codes 1023/1024 (replacing legacy Section 194C), apply the small-truck exemption only on filed declarations, split freight-forwarder bills between codes 1023/1024 and code 1006 (Section 393(1) Sl. 1(ii) commission), keep the GST RCM leg independent of the TDS leg, and reconcile every deduction in Form 168 against each transporter's Form 26AS / AIS reflection.
- **Logic:** Tag every transporter in the master with PAN, legal form (individual / HUF / company / firm / LLP), GTA classification (Y / N), small-truck declaration on file (Y / N with declaration date and fleet count), freight-forwarder split rule (Y / N), and applicable rate per leg; capture every freight invoice, split forwarder bills into freight and commission legs, check the small-truck declaration override first, then the per-invoice threshold (₹30,000) and aggregate (₹1,00,000 per FY) per PAN; deduct TDS at the correct code (1023/1024 for freight, 1006 for forwarder commission) at the correct rate (1% individual / HUF, 2% company / firm / LLP, 20% no-PAN); deposit on the 7th of the following month; file Form 168 quarterly with code-segregated per-PAN totals; reconcile to each transporter's Form 26AS / AIS; maintain cross-era 194C ↔ 393(1) Sl. 6(i) cross-reference through the FY 2026-27 cycle.
- **Config:** Transporter master with PAN, legal form, GTA flag, small-truck declaration register with annual renewal calendar (1 April each year) and PAN-with-fewer-than-10-trucks attestation, freight-forwarder split rule with commission percentage, per-PAN per-FY cumulative threshold tracker, monthly TDS challan calendar (7th of following month), quarterly Form 168 calendar, deductee invoice register with cross-era 194C / 393(1) Sl. 6(i) code mapping, GST RCM register independent of TDS register, and reconciliation link to Form 26AS / AIS download per transporter.
- **Output:** A live transporter dashboard per PAN showing declaration-on-file status, cumulative gross paid for the year, threshold-breach status, TDS deducted at codes 1023/1024 (freight) and code 1006 (forwarder commission), challan deposit confirmation per month, Form 168 filed position per quarter, the cross-tie to Form 26AS / AIS, an independent GST RCM register tracking the reverse-charge ITC leg, and a cross-era reconciliation register preserving legacy 194C entries through the FY 2026-27 cycle.

### TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly

Source: https://www.terra-insight.com/insights/tds-on-gst-component-india/

- **Problem:** CBDT Circular No. 23/2017 requires TDS to be computed on the base invoice value only, excluding the GST component. Deductors that compute on the gross amount (base plus 18 percent GST) over-deduct and create Form 26AS credits the vendor cannot claim. For a ₹1,18,000 invoice at 10 percent under 194J, the excess is ₹1,800 per invoice.
- **Logic:** Split each vendor invoice into base value and GST component at entry, either from a separately stated invoice line or by dividing the gross by one plus the applicable GST rate. Compute TDS only on the base value using the section-appropriate rate. Flag invoices without a GST break-up for vendor follow-up before TDS computation.
- **Config:** Invoice parser that extracts base and GST lines. Vendor-master GST rate field to derive base when GST is not separately shown. Exception queue for invoices without a GST break-up.
- **Output:** Correctly computed TDS on base value only, clean Form 26AS credits that the vendor can claim, and reduced correction return volume for GST-inclusive over-deductions.

### TDS on Interest Income for NBFCs: Section 393(1) Sl. 12 Code 1002 Chain

Source: https://www.terra-insight.com/insights/tds-on-interest-income-nbfc-section-194a-code-1002-india/

- **Problem:** An NBFC earns interest from two flows: contractual interest on its loan portfolio and treasury interest on its own investments. Both are subject to TDS deduction by the payer under Section 393(1) Sl. 12 payment code 1002 (the Income Tax Act 2025 successor to legacy Section 194A) at 10% for residents. The NBFC must reconcile its interest income register against inward TDS on both flows, tie every deduction back to Form 26AS, and file Form 26Q claims that recover the full deducted tax. Any break in this chain leaves TDS unclaimed and inflates the effective tax rate on the interest book.
- **Logic:** Segregate interest income into two ledgers — loan book (borrower interest) and treasury (investment interest). For each ledger, capture the accrual entry, the deductor identity (borrower TAN or bank TAN), the deducted amount, the payment code (1002), the section reference (legacy 194A / Sl. 12), and the assessment year. Reconcile against Form 16A certificates from TRACES and against the consolidated Form 26AS. Investigate every mismatch: missing Form 26AS entries where the NBFC recognised interest income; Form 26AS entries against the NBFC's TAN for interest the Treasury does not recognise; and timing gaps between accrual year and deductor's remittance year.
- **Config:** Ledger structure — borrower interest income register keyed by loan account + deductor TAN; treasury interest income register keyed by investment ID + bank TAN. Deductor master — every corporate borrower's TAN, name, and audit-threshold flag; every treasury counterparty's TAN. Payment code map — 1002 for interest other than securities, 1003 for interest on securities. Form 16A intake channel — quarterly TRACES download by TAN. Assessment year mapping rule — deferred credit claim vs current-year claim policy.
- **Output:** A quarter-end interest-TDS reconciliation pack: interest income by ledger tied to Form 26AS credits; a break register listing every unmatched deduction with owner, root cause, and resolution status; a Form 26Q filing extract; and an audit trail from every claim in the ITR back to a specific deductor's remittance and the underlying interest income entry.

### TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates

Source: https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india/

- **Problem:** Under Section 206AA, an invalid, inoperative (Aadhaar-unlinked), or not-furnished PAN forces TDS at the highest of the section rate or 20 percent. A single unvalidated vendor PAN on a ₹10 lakh invoice creates a ₹2 lakh deduction where 194C at 2 percent would have been ₹20,000, and the deductor bears the shortfall liability if the lower rate was applied.
- **Logic:** Run bulk PAN verification on TRACES before each quarterly return, flagging vendors as valid, invalid, inoperative, or not-found. For invalid or inoperative PANs, apply 20 percent (or treaty rate plus surcharge for non-residents) and save the TRACES output as audit evidence. Correct vendor-master PAN errors, re-verify, and recompute TDS for affected invoices before filing the return.
- **Config:** Vendor-master PAN validation status field refreshed pre-quarterly. TRACES bulk verification workflow with CSV upload. Rate-override rule applying 20 percent Section 206AA when status is invalid or inoperative.
- **Output:** Zero short-deduction exposure under Section 206AA, a dated TRACES verification evidence file per quarter, and correctly filed quarterly returns with auditor-ready PAN status documentation.

### TDS Payment Code 1006 (Section 393(1) Sl. 1(ii)): Commission and Brokerage Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1006-section-393-sl-1-ii-commission-brokerage/

- **Problem:** Commission TDS under payment code 1006 (formerly Section 194H) is a high-volume low-value transaction stream — many small commission payments to many agents — with a 2% rate and a low ₹15,000 aggregate threshold per deductee. The combination of high volume and a low threshold means the threshold rollover is the most error-prone aspect; ERPs that miss the rollover under-deduct on entire cohorts of agents.
- **Logic:** Reconciliation joins the commission-payable ledger (agent commission accruals and payouts) with the TDS challan register and Form 168 lines on a composite key of deductor TAN, payment code 1006, quarter, and deductee PAN. The matching engine tracks year-to-date commission per agent against the ₹15,000 threshold, validates the 2% rate at invoice level, and flags any commission payout that crossed the threshold mid-quarter without retrospective deduction on the breaching payment.
- **Config:** Agent master annotated with PAN and year-to-date commission counter that resets on April 1 each FY. Reconciliation ruleset configured with payment code 1006 (Section 393(1) Sl. 1(ii)) mapped to legacy 194H for cross-era matching, 2% rate validation, and an explicit boundary check against code 1035 (e-commerce operator) and code 1027 (professional fees) for service-based agents.
- **Output:** Form 168 commission lines fully matched to the commission-payable ledger, threshold rollover dates documented per agent, rate variances flagged at invoice level, and a clean audit pack showing every commission payment with the agent's running year-to-date balance and the deduction trigger date.

### TDS on Rent by Individual/HUF under Section 393(1) Sl. 2(i) Payment Code 1007 (FY 2026-27)

Source: https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-sl-2-i-rent-ind-huf-india/

- **Problem:** An Indian individual or HUF tenant — salaried or non-tax-audit professional — paying rent above ₹50,000 per month on a residential lease must run a Section 393(1) Sl. 2(i) code 1007 TDS deduction stream once a year: identify the ₹50,000 monthly threshold breach, compute 2% on gross rent for the deductible period, deposit via Form 26QC within 30 days of deduction, and issue Form 131 to the landlord — without a structured control the threshold is missed, the deduction timing is wrong, the challan is late, and Form 26AS at the landlord side does not tie to the certificate issued.
- **Logic:** Identify any month in the financial year where rent paid to a single landlord crosses ₹50,000; if breached, compute TDS at 2% (code 1007, provisional) on the gross rent for the relevant portion of the year; deduct once in the last month of tenancy (or last month of the FY); deposit via Form 26QC within 30 days; issue Form 131 to the landlord within 15 days of the Form 26QC due date; tie back to landlord's Form 26AS credit for reconciliation.
- **Config:** Lease master per property with landlord PAN, monthly rent, security deposit, lease start/end, residential-vs-commercial flag; monthly threshold tracker per landlord PAN checking the ₹50,000 trigger; single-event TDS computation engine at code 1007 (provisional) / Section 393(1) Sl. 2(i) / 2% rate; Form 26QC filing tracker with challan reference; Form 131 issue tracker per landlord per year.
- **Output:** An annual rent close pack showing the landlord, the monthly rent, the threshold-breach month, the deductible base, TDS deducted at 2% under code 1007 (provisional), Form 26QC filing status, and the Form 131 certificate issued to the landlord — ready for reconciliation against the landlord's Form 26AS and for the tenant's own Section 80GG / HRA position in their annual return.

### TDS Payment Code 1009 (Section 393(1) Sl. 2(ii).D(b)): Rent on Land and Building Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-sl-2-ii-rent-land-building/

- **Problem:** Rent TDS under payment code 1009 (formerly Section 194-I(b)) is a recurring monthly deduction stream with a 10% rate and an annual ₹2,40,000 aggregate threshold. The threshold is annual but the deduction is monthly, so the first month of a new tenancy where the projected annual rent crosses ₹2,40,000 needs TDS from month one — a common ERP misconfiguration.
- **Logic:** Reconciliation joins the rent ledger (rental accruals and payouts) with the TDS challan register and Form 168 lines on a composite key of deductor TAN, payment code 1009, month-of-deduction, and deductee PAN. The matching engine projects annual rent from the monthly rate, applies the ₹2,40,000 threshold check at month one, validates the 10% rate, and tracks the joint-owner allocation against per-co-owner thresholds.
- **Config:** Landlord master annotated with PAN, GSTIN (where applicable), joint-owner shares, and the monthly base rent. Reconciliation ruleset configured with payment code 1009 (Section 393(1) Sl. 2(ii).D(b)) mapped to legacy 194-I(b) for cross-era matching, 10% rate validation, and explicit handling of the security-deposit-versus-rent classification at the invoice line level.
- **Output:** Form 168 rent lines fully matched to the rent ledger, joint-owner allocations documented, GST-versus-base allocation reconciled at invoice level, and a clean audit pack showing every monthly rent deduction with the landlord PAN, the annualised threshold check, and the gross-rent base.

### TDS Payment Codes 1023 & 1024 (Section 393(1) Sl. 6(i)): Contractor Payments Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1023-1024-section-393-sl-6-i-contractor/

- **Problem:** Contractor TDS under payment codes 1023 and 1024 (formerly Section 194C) carries two different rates (1% individual/HUF under code 1023, 2% others under code 1024) and a dual threshold (₹30,000 per payment, ₹1,00,000 aggregate per FY). Misclassifying contractor status, missing the aggregate threshold rollover, or confusing contractor payments with professional fees produces TRACES default notices and Form 168 mismatches that have to be resolved before the deductee can claim credit.
- **Logic:** Reconciliation joins the AP ledger (contractor invoices and payments) with the TDS challan register and Form 168 lines on a composite key of deductor TAN, payment code (1023 or 1024), quarter, and deductee PAN. The matching engine checks rate applied against contractor entity type, validates per-payment and aggregate thresholds against year-to-date payments, and flags any line where the gross-up implied by tax amount divided by gross amount does not equal 1% (code 1023) or 2% (code 1024).
- **Config:** Vendor master annotated with contractor entity type (individual / HUF / firm / company), PAN, and any transport-carrier declaration on file. Reconciliation ruleset configured with payment codes 1023 and 1024 (under Section 393(1) Sl. 6(i)) mapped to legacy 194C for cross-era matching, dual-rate tolerance (1% for code 1023 / individual or HUF, 2% for code 1024 / others), and threshold tracking on a per-vendor per-FY basis.
- **Output:** Form 168 contractor lines fully matched to AP ledger, rate variances flagged at invoice level, threshold breach dates documented, and a clean audit pack ready for statutory audit showing every contractor payment with the applicable rate and code (1023 or 1024) justification.

### TDS Payment Code 1027 (Section 393(1) Sl. 6(iii).D(b)): Professional and Technical Fees Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1027-section-393-sl-6-iii-professional-fees/

- **Problem:** Professional and technical fees under legacy Section 194J have been split into two distinct codes under the Income Tax Act 2025 — code 1027 (10%, professional / royalty / non-compete, under §393(1) Sl. 6(iii).D(b)) and code 1026 (2%, technical services, under §393(1) Sl. 6(iii).D(a)). The deduction has to be tagged at the invoice level by the correct sub-code. Misclassifying a payment as technical (1026 at 2%) when it should be professional (1027 at 10%) shorts the deduction by 8 percentage points, surfacing as a TRACES default notice on the quarterly return.
- **Logic:** Reconciliation joins the AP ledger (professional invoices) with the TDS challan register and Form 168 lines on a composite key of deductor TAN, payment code (1027 or 1026), quarter, and deductee PAN. The matching engine validates the rate applied against the invoice service description, checks per-code threshold against year-to-date payments to the same deductee, and flags lines where the deduction implied by tax divided by gross does not equal the expected 10% (for 1027) or 2% (for 1026).
- **Config:** Vendor master annotated with default service category (professional / technical / royalty / non-compete) and an invoice-level override field where a single vendor invoices for multiple sub-types. Reconciliation ruleset configured with payment codes 1027 (§393(1) Sl. 6(iii).D(b), 10%) and 1026 (§393(1) Sl. 6(iii).D(a), 2%) both mapped to legacy 194J for cross-era matching, with per-code threshold tracking on a per-vendor per-FY basis.
- **Output:** Form 168 professional fee lines (code 1027) and technical fee lines (code 1026) fully matched to AP ledger, sub-code variances flagged at invoice level, threshold breach dates documented per code, and a clean audit pack showing every professional and technical fee payment with the applicable rate and service-type justification.

### TDS Payment Code 1031 (Section 393(1) Sl. 8(ii)): Purchase of Goods Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1031-section-393-sl-8-ii-purchase-goods/

- **Problem:** Buyer-side TDS on goods purchase under payment code 1031 (formerly Section 194Q) sits at the intersection of three triggers — buyer's prior-year turnover ₹10 crore, current-year cumulative purchase from a supplier ₹50 lakh, and the historical 194Q-versus-206C(1H) priority rule. Misconfiguring any of these produces either under-deduction (default risk for the buyer) or, in legacy records, double-deduction (the supplier also ran TCS, creating credit duplication).
- **Logic:** Reconciliation joins the buyer's accounts-payable ledger (supplier invoices and payments) with the TDS challan register and Form 168 lines on a composite key of deductor TAN (buyer), payment code 1031, quarter, and deductee PAN (supplier). The matching engine maintains per-supplier cumulative-purchase counters resetting on April 1 each FY, validates the 0.1% rate on the above-threshold portion only, enforces the historical 194Q-priority rule when the supplier was also subject to 206C(1H), and tracks the buyer's prior-year turnover qualifier.
- **Config:** Buyer master annotated with prior-year turnover (₹10 crore qualifier). Supplier master annotated with PAN, GSTIN, year-to-date purchase counter, and a flag for legacy 206C(1H) applicability (cross-era records only). Reconciliation ruleset configured with payment code 1031 (§393(1) Sl. 8(ii)) mapped to legacy 194Q for cross-era matching, 0.1% rate validation, threshold trigger logic, and explicit priority handling against legacy TCS codes.
- **Output:** Form 168 goods-purchase lines fully matched to the AP ledger by supplier, threshold trigger dates documented per supplier, legacy priority rule applied to suppress duplicate TCS where applicable, and a clean audit pack showing every above-threshold purchase line with the running cumulative balance and the TDS computed on the incremental amount.

### TDS Payment Code 1035 (Section 393(1) Sl. 8(v)): E-Commerce Operator Payout Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1035-section-393-sl-8-v-ecommerce-operator/

- **Problem:** E-commerce participant payout TDS under payment code 1035 (formerly Section 194O) is high-velocity — every transaction settled by the marketplace generates a TDS line — with a 0.1% rate on the GST-inclusive gross transaction value. Sellers reconciling Form 168 against their own gross sales register face three structural mismatches: GST gross-up, returns timing lag, and per-marketplace TAN-keyed segmentation.
- **Logic:** Reconciliation joins the seller's transaction ledger (orders, refunds, settlement payouts) with the TDS challan register and Form 168 lines on a composite key of deductor TAN (marketplace), payment code 1035, settlement date, and deductee PAN. The matching engine grosses up taxable sales by the applicable GST rate, validates 0.1% of GST-inclusive total against the Form 168 tax amount, and tracks return-related TDS reversals across settlement cycles.
- **Config:** Marketplace master annotated with TAN per marketplace and the operator's GSTIN. Reconciliation ruleset configured with payment code 1035 (§393(1) Sl. 8(v)) mapped to legacy 194O for cross-era matching, 0.1% rate validation against GST-inclusive gross, and explicit handling of returns (no TDS reversal until settlement-level write-back), commissions (separately under code 1006), and individual-participant ₹5,00,000 exemption tracking.
- **Output:** Form 168 e-commerce participant lines fully matched per marketplace TAN, GST-inclusive base reconciled to taxable sales plus GST, return-related variances flagged at settlement-cycle level, and a clean audit pack showing every payout cycle with the gross transaction base, TDS deducted, and the seller's net payout received.

### TDS Payment Code 1057 (Section 393(2) Sl. 17): Non-Resident Payment Reconciliation Guide

Source: https://www.terra-insight.com/insights/tds-payment-code-1057-section-393-2-sl-17-non-resident/

- **Problem:** Cross-border TDS under payment code 1057 (formerly Section 195) is the most complex TDS deduction in the Indian regime — every payment requires per-transaction analysis of treaty applicability, income classification, TRC validity, and Form 15CA/15CB workflow. Misclassifying a payment as fees for technical services versus royalty, or missing the TRC requirement, materially changes the deduction rate and creates either default risk or excess deduction.
- **Logic:** Reconciliation joins the AP ledger (foreign vendor invoices and remittances) with the TDS challan register and Form 27Q return lines on a composite key of deductor TAN, payment code 1057, quarter, deductee name, and country of residence. The matching engine validates the rate applied against the applicable DTAA table, checks TRC and Form 10F validity dates, enforces the Form 15CA/15CB requirement on cumulative remittances above ₹5,00,000, and flags any income type that may have an equalisation levy overlap.
- **Config:** Foreign vendor master annotated with country of residence, treaty article applicability, TRC validity, Form 10F on file, beneficial-ownership declaration, and any Section 197 lower-deduction certificate. Reconciliation ruleset configured with payment code 1057 (Section 393(2) Sl. 17) mapped to legacy 195 for cross-era matching, DTAA rate lookup table, and explicit handling of treaty-shopping safeguards.
- **Output:** Form 27Q non-resident payment lines fully matched to the AP ledger, TRC and Form 10F validity documented per vendor, Form 15CA/15CB references attached at line level, and a clean audit pack showing every cross-border remittance with the treaty rate justification, the income classification, and the supporting CA certificate.

### TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025

Source: https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india/

- **Problem:** From April 1, 2026, TDS and TCS section codes (194C, 194J, 194H, and so on) are replaced by numeric payment codes 1001 to 1092 under parent sections 392 (salary), 393 (non-salary TDS), and 394 (TCS). Vendor masters, GL codes, and reconciliation configurations must map legacy codes to new payment codes before go-live.
- **Logic:** Extract every section code active in the ERP, vendor master, and return preparation tool. Map each legacy section to its Income Tax Act 2025 parent section and indicative payment code. Treat paired codes as equivalent for cross-era matching during the transition.
- **Config:** Dual-mode reconciliation supports legacy, payment_code, and dual runs. CBDT publishes the final payment code mapping before go-live, and the final list must be confirmed against the CBDT notification before locking production.
- **Output:** Vendor master annotated with payment code, migration-ready reconciliation configuration, and end-to-end April 2026 test results covering ledger entry, challan deposit, return preparation, and certificate download under the new code.

### TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework

Source: https://www.terra-insight.com/insights/tds-penalty-interest-regime-india/

- **Problem:** TDS penalties compound across five layers — interest, assessee-in-default, expenditure disallowance, late filing fees, and criminal prosecution — often silently until a demand notice arrives.
- **Logic:** Map each TDS transaction to its penalty exposure: Section 201(1A) interest at 1-1.5%/month, Section 40(a)(ia) 30% disallowance, Section 234E at ₹200/day, Section 271H up to ₹1 lakh, Section 276B prosecution up to 7 years.
- **Config:** Late deposit: 1.5%/month from deduction to deposit. Non-deduction: 1%/month plus 30% disallowance. Late filing: ₹200/day capped at TDS amount. US Technologies v CIT (2023): 271C not leviable for delayed deposit.
- **Output:** Penalty exposure dashboard per TDS transaction, compliance calendar with deposit/filing deadlines, and total financial risk quantification across all five penalty layers.

### TDS on Property Purchase: Section 194IA ₹50 Lakh Threshold Trap

Source: https://www.terra-insight.com/insights/tds-property-purchase-section-194ia-50-lakh-threshold-india/

- **Problem:** An Indian buyer purchasing an immovable property from a resident seller where the consideration or stamp-duty value (whichever higher) equals or exceeds ₹50 lakh must deduct 1% TDS under the Section 393 successor to legacy Section 194IA, file Form 26QB within 30 days of month-end, issue Form 16B to the seller, and ensure the seller's Form 26AS reflects the credit — while navigating the cliff threshold, the higher-of-two-figures deduction base, and per-buyer 26QB filings on joint purchases.
- **Logic:** Compare consideration in the sale deed against the state-notified stamp-duty value on the same property; take the higher figure as both the threshold test and the deduction base; if it equals or exceeds ₹50 lakh, deduct 1% at the time of payment or credit to the seller (whichever earlier); split the deduction and Form 26QB filing across co-owner buyers by ownership share; file the challan-cum-statement on TRACES within 30 days of month-end; issue Form 16B; reconcile the sale deed value, the escrow/bank credit to the seller, the 26QB payload and the seller-side Form 26AS credit into a single evidence pack per unit sold.
- **Config:** Property master keyed by sale deed reference number with consideration, stamp-duty value, higher-of-two figure, and threshold-cross flag; buyer master with PAN and ownership share; seller master with PAN and residency status (routes to 194IA vs 195); TDS challan register per Form 26QB with challan number, deduction date, filing date, Form 16B download reference; sale deed to bank-statement to 26QB reconciliation view per unit; seller-side Form 26AS tie-back.
- **Output:** A per-unit TDS pack containing sale deed value, stamp-duty value, higher-of-two, threshold-cross flag, per-buyer 26QB references, Form 16B PDFs, and the seller's Form 26AS credit line; an audit-ready evidence trail linking the buyer's bank statement debit, the challan payment, the 26QB acknowledgement, and the seller's tax credit; a monthly exception list of 26QBs unfiled beyond 30 days, of stamp-duty value below consideration (where the deed should have been re-stamped), and of Form 26AS credits missing on the seller side.

### TDS Quarterly Return Reconciliation: Process and Common Errors

Source: https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation/

- **Problem:** TDS quarterly return reconciliation must match three data sets — books, the return being filed, and Form 26AS credits that eventually appear for deductees — with the Q4 return due May 31 carrying the highest risk because errors affect every deductee's ITR-season credit claim. Late filing attracts a ₹200 per day Section 234E fee capped at total quarterly TDS.
- **Logic:** Reconcile in three sequential steps. First, match the TDS ledger to the draft return by section and amount. Second, verify every challan in the return against OLTAS by BSR code, serial number, and deposit date, and confirm deposit dates fall within the correct quarter. Third, after filing, sample-check counterparty Form 26AS entries to confirm credits flow to the correct PANs at the correct sections.
- **Config:** Section-wise TDS ledger export mapped to the return template. OLTAS challan verifier keyed by BSR and serial. Post-filing Form 26AS sampler across deductee PANs.
- **Output:** Error-free quarterly return filed 10 to 15 working days before the deadline, zero Section 234E late fee exposure, and confirmed Form 26AS credits for all deductees before ITR season opens.

### TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year

Source: https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india/

- **Problem:** Mid-year rate and threshold changes (194H cut 5% to 2% on October 1, 2024; 194O cut 1% to 0.1% on October 1, 2024; 194J threshold raised ₹30K to ₹50K April 2025; 194A senior-citizen threshold raised ₹50K to ₹1L April 2025) require date-aware rate application, or reconciliation incorrectly flags correct deductions as errors.
- **Logic:** Maintain a rate calendar that records every effective-date change by section (old rate, new rate, transition date). Tag each payment transaction with the payment date (earlier of credit or payment). Look up the applicable rate for that section on that date. Apply the correct rate to calculate expected TDS and compare against what was deducted.
- **Config:** Rate calendar master with old rate, new rate, transition date, and threshold metadata per section. Payment date derived as the earlier of credit or payment.
- **Output:** Expected-vs-actual TDS variance classified as rate-transition, threshold-transition, or genuine deduction error, with each variance type routed to its appropriate queue.

### TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS

Source: https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation/

- **Problem:** The TDS receivable ledger accrues tax credit at invoice time, but only Form 26AS credits are claimable in the ITR. At scale, matching requires TAN-level logic across multi-TAN deductors, tolerance handling for rate and rounding differences, and cross-era support for FY 2025-26 legacy codes alongside FY 2026-27 payment codes.
- **Logic:** Match each ledger entry to Form 26AS on four keys — deductor TAN, section code (or post-April-2026 payment code), quarter, and amount — and classify unmatched entries into typed outcomes: amount mismatch, PAN error, missing credit, or cross-quarter slip. Route each outcome to the deductor with Form 16A (or Form 131) and challan references. Reconcile multi-TAN deductors by aggregating at the client PAN level.
- **Config:** Ledger fields capturing deductor TAN and section at invoice level. TAN-to-client master aggregating branches under a single economic client. Tolerance band for rounding differences, strict match on rate differences.
- **Output:** Confirmed Form 26AS credits available to claim in the ITR, a live list of unmatched entries by deductor for structured follow-up, and no year-end scramble to discover missing credits after Q4 close.

### TDS Reconciliation for IT Services Companies: 194J at Scale

Source: https://www.terra-insight.com/insights/tds-reconciliation-it-services-india/

- **Problem:** IT services companies with 50 or more active clients sit almost exclusively on the deductee side of Section 194J, splitting 10 percent professional services from 2 percent technical services after the Finance Act 2020. Net-of-TDS bank receipts, client-side section misclassification (194C instead of 194J), and multi-TAN corporate clients produce recurring gaps between invoices, 26AS, and bank credits that spreadsheets cannot close at scale.
- **Logic:** Three-way match each invoice to its bank credit (net of TDS) and its Form 26AS entry using deductor TAN, section code, and amount as keys. Classify variances as section misclassification (194C vs 194J), rate error (10 percent vs 2 percent), late return filing, or PAN slip, and route each type to a deductor correction statement. Aggregate multi-TAN enterprise clients (HDFC, TCS, banks) at the economic-entity level.
- **Config:** Vendor-master with professional vs technical service default. TAN-to-client master for multi-branch enterprise clients. Net-of-TDS match rule linking invoice, bank credit, and Form 26AS row in one operation.
- **Output:** Quarterly 194J reconciliation cleared in hours rather than weeks, recovered credits via deductor section-change correction returns, and full TDS credit claimed in the ITR with an auditor-ready trace per invoice.

### TDS Reconciliation for NBFCs: Managing Section 194A at Scale

Source: https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india/

- **Problem:** NBFCs operate on both sides of the TDS ledger simultaneously — deducting 10 percent under Section 194A on depositor interest above ₹5,000 (20 percent when PAN is absent under 206AA) while receiving TDS-deducted interest from banking partners. At 10,000 depositors and multiple co-lending partnerships, PAN validation failures, Form 15G/15H timing, and multi-TAN mappings accumulate error at scale.
- **Logic:** Validate depositor PANs at account opening and each payout cycle, applying 10 percent where PAN is valid and 20 percent under 206AA otherwise. Track Form 15G and 15H submissions per quarter on TRACES and exclude eligible accounts from deduction. For co-lending, map each bank partner's TAN to the specific partnership and reconcile Form 26AS entries under that TAN against the NBFC's interest-received ledger.
- **Config:** Depositor-master PAN validation status refreshed per payout. Form 15G/15H register with quarterly TRACES submission workflow. Co-lending partner-to-TAN master for bank-partner Form 26AS matching.
- **Output:** Correct 10 percent or 20 percent deductions at each payout, Form 26AS entries under bank TANs reconciled to co-lending interest income, timely Form 16A to depositors, and RBI-aligned interest-income reporting.

### TDS Reconciliation Runbook: Monthly Deposit and Quarterly Form 168 Match for Indian Finance Teams

Source: https://www.terra-insight.com/insights/tds-reconciliation-runbook-monthly-quarterly-india/

- **Problem:** TDS reconciliation compresses four working days into three at month end, ships the challan on the 7th of the following month without an upstream cross-era classification check, and rolls the TDS receivable ledger forward from quarter to quarter without a Form 168 match. The result is a Section 200A demand notice on short deposit or wrong payment code, an assessee-in-default liability under Section 201(1) with 1 percent per month interest, and a year-end audit finding on an unreconciled TDS receivable balance that should have been cleared quarter by quarter. Every one of these is preventable through an operational sequence that runs the deposit against a closed ledger and the receivable against a quarterly Form 168 pull.
- **Logic:** Sequence the TDS window across Days 6 to 10 of the monthly close. Day 6 is extraction and Section 393 payment code classification for both the payable and receivable sides. Day 7 is challan preparation, deposit, and CIN capture against the closed payable ledger. Day 8 is the challan-to-ERP match and any correction file under the Section 154 workflow. Day 9 is the receivable match against the bank credits pre-populated on Day 3 of the upstream bank window, and Day 10 is the exception categorisation and tax manager sign-off. In the third month of every quarter, add a half day for the Form 168 pull, the five-way match against the receivable ledger, and a 180-day aging queue with escalation triggers. Run cross-era two-key matching — Section 393 payment code first, then legacy Section 194x code — for FY 2025-26 residuals still in flight.
- **Config:** Named roles per window: tax executive runs the reconciliation on Days 6 to 10; tax manager reviews and signs off. Payment code reference table maintained as a versioned master (code 1001 salary Section 392; codes 1002 to 1092 non-salary Section 393; code 1094 TCS Section 394) with the legacy Section 194 mapping carried alongside for cross-era work. PAN validation refresh cadence against the Income Tax Department database at deductor onboarding and quarterly thereafter, feeding the Section 206AA higher-rate exception queue. Circular 23/2017 flag on every ERP TDS calculation field, enforced as a formula against the GST-exclusive base rather than a manual override. Form 168 pull cadence on the last day of the first month of each quarter for the previous quarter, with reconciliation against the receivable ledger before the working paper is signed off.
- **Output:** A closed TDS window on Day 10 with four named exception categories aged against the escalation ladder — awaiting Form 168 posting, deductor short-deducted, Section 206AA PAN-mismatch higher rate, Circular 23/2017 GST-inclusive deduction. A quarterly Form 168 reconciliation working paper filed alongside every March, June, September, and December close, with a 180-day maximum-open rule on the receivable aging queue. A cross-era mapping table refreshed every month for the residual FY 2025-26 items in flight. A tax manager sign-off on Day 10 that is the gate opening the GST window on Day 11, and a controller-level defensible reconciliation base for the quarterly TDS return and the annual filing.

### Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS

Source: https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india/

- **Problem:** Section 192 salary TDS uses a slab-based computation rather than a fixed rate, and Q4 deductions spike as year-end bonuses, ESOP perquisites, HRA revisions, and Form 12BB declarations are finalised. Reconciliation spans three sources — payroll register, challan deposit record, and Form 26AS — and a gap at any checkpoint creates Form 16 mismatches that employees cannot resolve at ITR time.
- **Logic:** Reconcile monthly (payroll TDS matched to challan deposit by BSR code and serial number), quarterly (Form 24Q Annex II matched to payroll and deposit records), and year-end (Form 16 Part A from TRACES matched to payroll annual computation). Trigger retroactive recomputation when perquisites are added late or Form 12BB declarations are revised, and distribute the shortfall across remaining monthly deductions.
- **Config:** Payroll-to-challan match rule keyed on BSR code, challan serial, and deposit date. Perquisite trigger that recomputes annual tax and redistributes across remaining months. Form 12BB revision log with cutover date for recalculation.
- **Output:** Each month's deduction reconciled at source, Form 24Q filed with matched Annex II records, Form 16 Part A consistent with payroll annual computation, and no ITR-time employee-employer disputes over Section 192 TDS.

### TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India

Source: https://www.terra-insight.com/insights/tds-refund-reconciliation-india/

- **Problem:** TDS refunds arise when aggregate TDS deducted exceeds annual tax liability — common for loss-year companies, entities with exempt income, or holders of Section 197 certificates not submitted on time. Refund reconciliation runs across ITR filing, Section 143(1) intimation, Section 245 adjustments against prior-year demands, and bank credit, with failure points at each stage.
- **Logic:** Compute the expected refund from TDS receivable, match it to the 143(1) intimation figure, and route any shortfall to pending deductor returns for follow-up. Monitor Section 245 adjustment notices and respond within 30 days for disputed prior-year demands. Verify the pre-validated bank account on the portal and track the refund credit through bank reconciliation.
- **Config:** Refund register with expected, intimation, and bank-credited columns per assessment year. Section 245 notice tracker with 30-day response ageing. Bank account pre-validation status check on the income tax portal.
- **Output:** Reconciled refund from TDS receivable to Section 143(1) intimation to bank credit, resolved Section 245 adjustment notices, and a structured follow-up file for deductor credits not yet in Form 26AS at intimation time.

### Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies

Source: https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india/

- **Problem:** Since April 1, 2020, dividend-paying companies deduct 10 percent TDS under Section 194 on dividends above ₹5,000 per resident shareholder (20 percent under 206AA for missing PAN; 20 percent plus surcharge and cess for non-residents under Section 195, reduced by DTAA where TRC and Form 10F are on file). Listed companies with millions of retail shareholders encounter PAN data gaps, joint-holder attribution, and DTAA rate mismatches at scale.
- **Logic:** Validate every shareholder PAN in the register before each dividend payout and flag absent or invalid records for 206AA 20 percent. For non-residents claiming DTAA rates, require a current TRC and Form 10F on file before applying the treaty rate. Deduct on the first-named holder for joint accounts and maintain IEPF-transferred share records separately. Reconcile Form 26AS shareholder credits against the dividend register by PAN, quarter, and amount.
- **Config:** Shareholder-register PAN validation pre-payout. TRC and Form 10F attachment register for non-resident shareholders. First-holder attribution rule for joint holdings.
- **Output:** Correctly rated dividend TDS on every shareholder, Form 26Q and Form 27Q filings that match the dividend register, timely Form 16A certificates, and minimal investor disputes at ITR time.

### TDS Under Section 194A: Interest Income Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194a-interest-tds/

- **Problem:** Section 194A thresholds differ sharply by source — ₹5,000 per year for NBFC, cooperative society, and inter-company loan interest versus ₹40,000 per year for bank FD interest (₹1,00,000 for senior citizens from April 1, 2025). Uniform threshold configurations in ERP cause missed TDS on NBFC deposits and unexplained Form 26AS credits that do not map to receivables.
- **Logic:** Tag each interest source in the investment master with its correct threshold (₹5,000 or ₹40,000/₹1,00,000) and 10 percent rate. Apply TDS on accrual or payment, whichever is earlier, and match Form 26AS quarterly entries against the interest accrual schedule rather than the receipt date. Handle inter-company loans with the borrower as deductor and the parent or lender as the Form 26AS credit recipient.
- **Config:** Investment master with source-type threshold mapping. Accrual-based TDS recognition rule. Inter-company loan configuration identifying deductor entity in a conglomerate.
- **Output:** Correct 194A TDS on every interest source, no UNEXPLAINED Form 26AS credits from missed NBFC deductions, and reconciled quarter-by-quarter matching between interest accruals and TRACES credits.

### TDS Under Section 194C: Contractor Payment Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194c-contractor-payments/

- **Problem:** Section 194C rate-mix errors (1 percent for individual or HUF versus 2 percent for companies and firms), sub-contractor TDS chains, and multi-branch TAN multiplicity produce recurring Form 26AS variances on contractor and manpower supply payments. On a ₹10,00,000 invoice, a rate mismatch from 2 percent to 1 percent is a ₹10,000 shortfall in claimable credit.
- **Logic:** Tag each vendor in the master with the correct entity type (individual/HUF at 1 percent, company/firm at 2 percent) and section code 194C. Classify Form 26AS entries against the expected rate and flag mismatches as TAX_DEDUCTION variance, route wrong-section entries to the deductor for a section-change correction return, and aggregate multi-branch deductor TANs under a single economic client for holistic reconciliation.
- **Config:** Vendor master with entity-type and 194C default. TAN-to-client master aggregating branches. Typed rate-variance classifier with expected vs actual TDS per invoice.
- **Output:** Correctly deducted 194C TDS on every contractor payment, resolved rate shortfalls through deductor correction returns, and reconciled Form 26AS credits across multi-branch clients without manual lookup.

### TDS Under Section 194H: Commission and Brokerage Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage/

- **Problem:** Section 194H rate dropped from 5 percent to 2 percent on October 1, 2024, and advertising creative work was reclassified from 194H commission to 194J professional services. Variable commission amounts, quarterly consolidated deposits, and the 194H-vs-194J boundary dispute produce recurring Form 26AS reconciliation gaps that simple amount matching cannot clear.
- **Logic:** Apply the correct rate by date — 5 percent for payments up to September 30, 2024 and 2 percent from October 1, 2024 — and match quarterly consolidated Form 26AS entries against the sum of commission invoices in that quarter. Flag payments tagged 194H that are actually creative advertising for a 194J section-change correction. Use Form 16A certificate numbers as the authoritative match key where amounts are variable.
- **Config:** Rate calendar with October 1, 2024 transition. Certificate-number based match for variable commission. Vendor-master classification of commission-earners vs advertising agencies to route 194H vs 194J.
- **Output:** Quarterly 194H reconciliation that handles rate-by-date correctly, cleared advertising reclassifications via deductor correction returns, and commission-income Form 26AS entries reconciled at quarter-total level.

### TDS Under Section 194I: Rent Payment Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation/

- **Problem:** Section 194I splits into 10 percent for land, building, furniture, and fittings and 2 percent for plant, machinery, and equipment, with a ₹2,40,000 per-landlord annual threshold. Multi-city office portfolios, incorrect TDS on refundable security deposits, and co-working vs lease classification are the three recurring error modes.
- **Logic:** Tag each lease in the property master with asset type (building vs plant) and the corresponding rate, and record the landlord's PAN and TAN. Suppress TDS on security deposits — only rent is in scope. Classify co-working arrangements that grant shared access with services as 194J at 2 percent, not 194I. Map each monthly rent payment to the property-level TAN for reconciliation.
- **Config:** Property master with asset-type rate (10 percent or 2 percent). Deposit-vs-rent flag suppressing TDS on refundable deposits. Co-working engagement flag routing to 194J classification.
- **Output:** Correctly rated rent TDS across multi-city portfolios, zero erroneous deductions on security deposits, and Form 26AS reconciliation keyed to property-level TAN for each lease.

### TDS Under Section 194J: Professional Services Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194j-professional-services/

- **Problem:** Section 194J splits into 10 percent for professional services and 2 percent for technical services from Finance Act 2020, and the threshold rose from ₹30,000 to ₹50,000 on April 1, 2025. ERP configurations still applying a flat 10 percent over-deduct on IT and software invoices; on a ₹5,00,000 monthly engagement that is ₹40,000 per month of recoverable working capital.
- **Logic:** Classify each engagement as professional advisory (10 percent) or technical services (2 percent) at the invoice line level, using vendor-master defaults keyed to SAC code. Apply the ₹50,000 threshold to deductions from April 1, 2025 onward and ₹30,000 for earlier periods. Aggregate monthly invoices to quarterly Form 26AS entries when the deductor consolidates deposits, and reconcile at quarter total rather than line-by-line.
- **Config:** Vendor master with professional vs technical split by SAC code. Threshold calendar (₹30K pre-April-2025, ₹50K post). Quarter-sum rollup of invoice TDS for comparison against consolidated Form 26AS entries.
- **Output:** Correctly rated 194J deductions, recovered over-deduction via deductor correction returns, and reconciled quarter-total credits that align invoice aggregates with Form 26AS entries.

### TDS Under Section 194N: Cash Withdrawal Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal/

- **Problem:** Section 194N triggers automatic 2 percent TDS (5 percent for non-ITR filers) by the bank once aggregate cash withdrawals from that bank cross ₹1 crore in a financial year. Finance teams find unexpected debits in bank statements, often misclassified as bank charges, understating the TDS credit and overstating operating expense.
- **Logic:** Recognise 194N debits in the bank statement and post them to a TDS advance tax account rather than a bank fee account. Match each debit against Form 26AS Part A1 where the bank's TAN appears as deductor and the section code is 194N. Aggregate at the bank level, not the account level, since the ₹1 crore threshold pools all accounts at the same bank.
- **Config:** Bank statement rule library recognising 194N debit patterns per bank. Ledger mapping to TDS advance tax account, not bank charges. Per-bank cash-withdrawal counter for treasury visibility.
- **Output:** Accurate TDS advance tax credit claimed at ITR time, corrected operating-cost reporting, and a clean audit trail linking each bank-debited TDS to its Form 26AS Part A1 entry.

### Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers

Source: https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation/

- **Problem:** Section 194O rate was cut from 1 percent to 0.1 percent on October 1, 2024, and is deducted on the gross payment (including GST embedded in marketplace fees) while sellers book revenue net of GST. Sellers on multiple marketplaces (Amazon, Flipkart, Meesho) receive separate TDS streams per deductor TAN, and returns, refunds, and settlement timing create recurring reconciliation gaps.
- **Logic:** Split Form 26AS entries by operator TAN and reconcile each platform's deductions independently against its settlement statements at the quarter level. Apply rate-by-date logic across the October 1, 2024 transition. Decompose the gross-vs-net gap by computing the expected TDS base as net revenue plus GST on fees, and route timing mismatches from returns or refund reversals to the next settlement cycle.
- **Config:** Per-operator TAN reconciliation queue. Rate calendar with October 1, 2024 transition. Gross-base calculator adding GST on marketplace fees to net revenue for TDS comparison.
- **Output:** Operator-level reconciled TDS credits, decomposed gross-vs-net variance attributed to GST-on-fees rather than genuine error, and clean claim against Form 26AS for each marketplace across the rate-transition boundary.

### TDS Under Section 194Q: Purchase Reconciliation for Large Buyers

Source: https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation/

- **Problem:** Section 194Q requires buyers with prior-year turnover above ₹10 crore to deduct 0.1 percent TDS on purchases from any single seller above ₹50 lakh cumulative in the financial year. Missing the mid-year threshold crossing leaves months of subsequent payments under-deducted, and although the legacy 194Q vs 206C(1H) TCS overlap historically caused double-deduction disputes between buyer and seller, 206C(1H) is now inapplicable since 1 April 2025.
- **Logic:** Track cumulative purchases per seller PAN across the financial year and trigger 0.1 percent deduction on every payment after the ₹50 lakh mark, on the GST-exclusive base. Notify the seller at the first deduction so they can post the matching Form 26AS / Form 168 credit. For historical entries (pre-1 April 2025), flag counterparties where both 194Q (buyer deducts) and the now-abolished 206C(1H) (seller collected) were configured, and reconcile the legacy overlap accordingly.
- **Config:** Vendor-master eligibility flag based on prior-year turnover. Per-seller cumulative purchase counter resetting each April 1. Historical 194Q vs 206C(1H) precedence rule for legacy entries; 206C(1H) is abolished from 1 April 2025.
- **Output:** Timely threshold-crossing alerts, correct 0.1 percent deductions from the first payment after ₹50 lakh, reconciled Form 26AS Part A1 entries for sellers, and elimination of buyer-seller double-deduction disputes.

### TDS Under Section 194R: Benefit and Perquisite Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite/

- **Problem:** Section 194R requires 10 percent TDS on benefits or perquisites above ₹20,000 per recipient per year given to business associates — distributor gifts, dealer travel, sponsored conferences, and high-value product samples. For non-cash benefits the deductor must gross up and pay TDS from its own funds, creating a line-item marketing cost that is missed without a per-recipient benefit register.
- **Logic:** Maintain a per-recipient cumulative benefit register across all touchpoints — samples, gifts, sponsored travel, event sponsorships — and trigger 10 percent TDS on the first transaction after the running total crosses ₹20,000. For non-cash benefits, apply the grossing-up formula and post the TDS as a marketing expense in the books. Record each deduction to the correct Section 194R challan for quarterly return filing.
- **Config:** Per-recipient benefit register spanning marketing, sampling, and channel-management sub-ledgers. Grossing-up calculator for non-cash benefits. Challan mapping to Section 194R with non-recoverable TDS tagged as expense.
- **Output:** Correct 10 percent deductions from the first qualifying transaction, Form 26AS Part A1 credits posted to recipient accounts, and clean book treatment of grossed-up TDS as a marketing cost line.

### Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India

Source: https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india/

- **Problem:** Section 194S requires 1 percent TDS on VDA consideration at transfer — threshold ₹50,000 for specified persons and ₹10,000 for others. Volatile asset values, day-end vs trade-time price reporting, multi-exchange deduction streams, and in-kind consideration (crypto-for-crypto swaps) create systematic gaps between exchange-side TDS and the trader's ledger.
- **Logic:** Compute TDS at trade-time INR value using the exchange rate on the date of transfer, not day-end batch prices. For in-kind exchanges, value the VDA received at its INR fair market value on the transfer date. Split Form 26AS entries by exchange TAN, match against the exchange's quarterly TDS certificate, and claim the credit in ITR even on loss trades (Section 115BBH does not restrict TDS credit).
- **Config:** Trade-time price capture rule with INR conversion at the transfer date. In-kind consideration valuer for crypto-for-crypto swaps. Per-exchange TAN reconciliation keyed to Form 26QF quarterly filings.
- **Output:** Trade-by-trade TDS reconciliation across multiple exchanges, claimable TDS credit even on loss-year VDA positions, and a documented trade ledger supporting Form 26AS entries for the full financial year.

### Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates

Source: https://www.terra-insight.com/insights/tds-section-206ab-206cca-india/

- **Problem:** Section 206AB requires TDS at twice the section rate or 5 percent (whichever is higher) for specified persons — vendors with two preceding years of non-filing and ₹50,000-plus TDS/TCS in each. Specified person status can change mid-year, so annual master updates miss vendors who file late or newly become non-filers. Failure exposes the deductor to Section 201 short-deduction liability plus 271C penalty. 206AB and 206CCA are abolished from April 1, 2026.
- **Logic:** Run the TRACES Compliance Check before each payment cycle for vendors above the relevant section threshold, not annually. Apply the higher of twice the section rate or 5 percent when status is specified person, and retain the dated compliance output as audit evidence. Decommission the check and rate-override logic from April 1, 2026 under the Income Tax Act 2025.
- **Config:** Vendor-level specified-person flag refreshed pre-payment. Higher-rate calculator comparing 2x section rate vs 5 percent. Sunset switch retiring 206AB and 206CCA logic on April 1, 2026.
- **Output:** Correctly higher-rated TDS on specified persons, Section 201 defence file with dated compliance evidence, and a clean sunset on April 1, 2026 with no carry-over over-deduction risk.

### TDS Under Section 195: Non-Resident Payment Reconciliation

Source: https://www.terra-insight.com/insights/tds-section-195-non-resident-payments/

- **Problem:** Section 195 has no minimum threshold — every outward remittance to a non-resident is potentially taxable at source. The correct rate depends on income nature (royalty, business income, interest, dividend), recipient country, and whether a valid Tax Residency Certificate and Form 10F are on file. Wrong classification creates short-deduction demands or over-deduction cash-flow drag that the non-resident must claim back.
- **Logic:** Tag each outward payment with section code 195 (or new 2025 Act payment codes 1039–1057), DTAA country, income nature, and applicable rate. Verify that a TRC, Form 10F, and Form 15CA plus 15CB are on file before the bank releases the wire. Match each remittance against the challan, Form 15CA acknowledgment, and Form 26AS Part A entry using the non-resident's PAN or the deductor TAN as the key.
- **Config:** Rate determination rule table by income type and DTAA country. TRC and Form 10F attachment register. Form 15CA acknowledgment cross-reference against outward payment records.
- **Output:** Correctly rated non-resident remittances, complete Form 15CA/15CB audit file, reconciled Form 26AS Part A entries, and counterparty-ready payment logs that foreign vendors can match to their Indian tax credit position.

### Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers

Source: https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india/

- **Problem:** Section 206C creates a dual obligation — sellers must match TCS collected to challan deposited and Form 27EQ filed, while buyers must verify Form 26AS Part C credits against invoices. Scrap at 1 percent, 20 percent TCS on LRS above medical/education and on overseas tour packages from October 1, 2023, and the legacy 194Q vs 206C(1H) precedence rule for above-₹10-crore buyers (206C(1H) abolished from 1 April 2025) produce recurring errors on both sides.
- **Logic:** For sellers, reconcile TCS collected per buyer PAN and category against the monthly challan, file Form 27EQ quarterly, and issue Form 27D. For buyers, match each Form 26AS Part C entry to the collector TAN, section, and invoice. Flag transactions where the buyer's prior-year turnover exceeds ₹10 crore and suppress TCS collection in favour of 194Q TDS by the buyer.
- **Config:** Buyer-master with prior-year turnover flag controlling historical 194Q vs 206C(1H) precedence (206C(1H) abolished 1 April 2025). Category-rate master (scrap 1 percent, LRS 20 percent with medical/education exception at 5 percent, tour 20 percent). Seller-side TCS reconciliation workflow aligned to Form 27EQ quarters.
- **Output:** Matched TCS collected to deposited and filed figures for sellers, Form 26AS Part C credits that reconcile to invoices for buyers, zero legacy 194Q vs 206C(1H) double-deduction disputes for pre-1-April-2025 periods, and auditor-ready TCS evidence for scrap, LRS, and tour transactions.

### TDS Section 393(1) Codes 1023/1024 for Textile Job-Work

Source: https://www.terra-insight.com/insights/tds-section-393-textile-job-work-codes-1023-1024/

- **Problem:** A national branded apparel manufacturer running a network of 47 job-workers across Tiruppur, Bhilwara, Ludhiana, and Surat spends approximately ₹2.1 crore per quarter on job-work conversion charges spread across dyeing, printing, embroidery, cutting, and stitching. The taxonomy under Income-tax Act 2025 Section 393(1) Sl. 4 splits every one of those 47 job-worker relationships into either code 1023 (material supplied by principal) or code 1024 (material not supplied), with a rate slab of 1 percent (Ind/HUF) or 2 percent (other resident) and a threshold of single ₹30,000 or aggregate ₹1,00,000 per FY per PAN. Mis-classification between the two codes produces a Form 26Q filing that will not reconcile against Form 26AS at the job-worker PAN, exposes the deductor to Section 201/201(1A) short-deduction interest and penalty, and — on a code-1024-to-1023 boundary error — risks re-treatment of a purchase transaction as a service or vice versa with GST-side consequences on Section 143 CGST job-work provisions. Manual per-invoice classification across a 47-vendor network with 200+ invoices per quarter leaves a residue of mis-flagged transactions that only surface at year-end 26AS reconciliation, by which time correction filings become costly.
- **Logic:** Build a job-worker master keyed by PAN and GSTIN carrying the material-supplied flag (true for code 1023, false for code 1024), the residency type (Ind/HUF vs other resident vs non-resident), the applicable TDS rate (1 percent Ind/HUF, 2 percent other resident, Section 195 for non-resident), the aggregate-paid tracker for the current FY against the ₹1,00,000 threshold, and the Rule 55 CGST delivery challan cross-reference that documents the material-supplied fact. At every conversion invoice, look up the job-worker relationship, deduct TDS at the classified code and rate, and remit against the job-worker PAN with the correct payment code in the challan. At quarter-end, generate the Form 26Q Annexure I lines with the payment code, deductee PAN, gross amount, and challan reference. Issue Form 16A to every job worker with the payment code and TDS credit. Reconcile the deductor's 26Q filing against Form 26AS at every job-worker PAN — mis-matches flag for correction filing before year-end.
- **Config:** Job-worker master with PAN, GSTIN, name, address, residency type (Ind/HUF, other resident, non-resident), material-supplied flag (per relationship, not per invoice — engagements that switch classification across invoices should be modelled as two separate job-worker records), Section 393(1) payment code (1023 if material-supplied true; 1024 if false; 1014 if freight; 1021 if professional/technical service; 1031 if purchase of goods above 194Q threshold), TDS rate slab (1 percent for Ind/HUF resident, 2 percent for other resident, DTAA-driven for non-resident under Section 195), threshold tracker (single ₹30,000 and aggregate ₹1,00,000 per FY per PAN), Rule 55 CGST delivery challan reference for every code-1023 relationship, and Section 143 CGST clock configuration if the material-supplied flag is true (1-year deemed-supply provision runs against every code 1023 job-work chain). Freight vendors carry a separate master under code 1014 with Section 194-IA successor rate.
- **Output:** A quarterly Form 26Q draft with Annexure I populated per Section 393(1) Sl. 4 codes — code 1023 lines for material-supplied job-work relationships (majority of the textile network), code 1024 lines for material-not-supplied engagements, code 1014 lines for freight vendors engaged separately, code 1021 lines for external testing labs or design consultancies. Per-job-worker Form 16A issued after the quarter with the correct payment code and rate. A reconciliation pack against Form 26AS at every job-worker PAN — matched credits, unmatched credits (deductor's 26Q did not report but 26AS shows a credit; or 26Q reported but 26AS does not reflect), and mis-classifications (26Q line reports code 1023 but 26AS shows code 1024 or vice versa). Threshold ageing report for every job-worker relationship approaching the ₹1,00,000 aggregate mark, prompting deduction on the next invoice.

### Section 393(2) (non-resident catch-all) of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission

Source: https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation/

- **Problem:** Hotels paying Booking.com (Netherlands), Agoda (Singapore), and Expedia (US or UK) must withhold tax at source on commission, but from April 1, 2026 the section reference moves from 195 to 413 of the Income Tax Act 2025, the rate is the lower of the Act rate or DTAA treaty rate, royalty vs FTS vs business-income classification is contested, and Form 168 will not show these credits because the deductee is non-resident — leaving the hotel with a separate outbound TDS register and a 15CA/15CB evidence trail.
- **Logic:** For each foreign OTA, store treaty article, TRC validity, Form 10F date, and classification position in the vendor master. On every commission remittance, apply the lower of the Act rate or the DTAA rate, generate Form 15CA and Form 15CB where required, deposit Challan 281 under code 1057 under §393(2) Sl. 17 routing, file Form 27Q, and record the deduction in the outbound TDS register against the foreign OTA. Route deductions on date — pre-April 1, 2026 entries stay under Section 195; April 1, 2026 onwards under Section 393(2) (non-resident catch-all).
- **Config:** Foreign OTA vendor master with treaty article, TRC, Form 10F, classification position; DTAA rate table with Netherlands, Singapore, US, UK entries; Form 15CA Part C generator; Form 15CB capture; outbound TDS register that reconciles to bank remittance and Form 27Q line items; cross-era routing rule on deduction date.
- **Output:** An outbound TDS register where every foreign OTA commission remittance is tagged with the correct section (Section 195 for legacy entries, Section 393(2) (non-resident catch-all) from April 1, 2026), the applicable DTAA treaty rate is documented with TRC and Form 10F, Form 15CA and 15CB acknowledgements are linked, Challan 281 reconciles to Form 27Q, and the bank-confirmed remitted amount matches the gross commission less withheld tax.

### TDS on Tooling Payments: Capital vs Revenue Classification for Auto-Component Suppliers

Source: https://www.terra-insight.com/insights/tds-tooling-payment-capital-vs-revenue-auto-india/

- **Problem:** An Indian Tier-1 auto-component supplier handling 200 to 500 OEM tooling transactions a year — stamping dies, injection-mould tools, gauges, fixtures, check-pins — across Maruti, Hyundai, Tata Motors, Mahindra, M&M and others must classify each tooling payment correctly between capital reimbursement (no TDS) and revenue conversion charge (TDS under Section 393(1) Sl. 6(i) codes 1023/1024 at 1% or 2%). Three live patterns operate — OEM-capitalised lump-sum reimbursement, supplier-capitalised piece-rate recovery, and OEM-capitalised amortised piece-rate — each with different income-tax, GST and balance-sheet treatments. Misclassification carries Section 201(1A) interest, Section 40(a)(ia) disallowance and OEM-supplier reconciliation disputes that surface only at year-end.
- **Logic:** Anchor every tooling transaction in a contract-class register tagged by pattern (lump-sum / piece-rate / amortised) with title-transfer clause, capitalisation-side (OEM / supplier), depreciation-side, GST classification (HSN goods / SAC services), and TDS treatment (capital exempt / revenue at codes 1023/1024 / mixed). For each pattern, drive the three legs — income-tax (deduct or not), GST (rate and HSN / SAC), balance-sheet (whose books) — consistently. Reconcile against the OEM's Form 168 entries to confirm no TDS was deducted on lump-sum reimbursements and TDS was deducted at codes 1023/1024 on piece-rate components. Maintain a contract-class master with title, capitalisation, depreciation and TDS treatment per tool to defend audit queries.
- **Config:** Tool register per OEM with contract pattern (lump-sum / piece-rate / amortised), title-transfer clause reference, OEM / supplier capitalisation flag, depreciation calendar, HSN / SAC code per leg, TDS treatment per leg (no TDS / codes 1023/1024 / mixed), purchase-order cross-reference, GL mapping (capital reimbursement account, conversion-charge revenue account, tool amortisation account), Form 168 cross-tie register per OEM TAN, and contract-class library with audit-defensible precedents.
- **Output:** A tool-by-tool dashboard showing pattern classification, title transfer status, capitalisation side, depreciation accumulated to date, TDS treatment applied, OEM Form 168 deductions reconciled, the substance memo on file for each pattern, and an audit-defensible classification trail for each tooling transaction in the FY.

### TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams

Source: https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india/

- **Problem:** TRACES is the Income Tax Department's central portal for Form 26AS, AIS, challan status, Form 16A, correction returns, and Section 206AB checks. Using TRACES only at year-end misses three quarterly reconciliation windows — Q1, Q2, Q3 — during which deductors can still file corrections before their windows close.
- **Logic:** Run TRACES workflows at four structured points each year aligned to return due dates. Download Form 26AS XML post each quarter (31 July, 31 October, 31 January, 31 May) and match against the TDS receivable ledger. Cross-check AIS for entries pending 26AS reflection. Verify challan status pre-filing to avoid C2 corrections. Run the 206AB compliance check pre-payment for above-threshold vendors.
- **Config:** Quarterly reconciliation calendar keyed to return due dates. XML parser for Form 26AS structured extraction. Pre-filing challan status verifier and pre-payment 206AB compliance check workflows.
- **Output:** Quarterly-cleared Form 26AS mismatches caught within the deductor correction window, zero Section 200A challan-mismatch demands at filing, and dated 206AB evidence files protecting against Section 201 short-deduction exposure.

### TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams

Source: https://www.terra-insight.com/insights/tds-year-end-march-close-india/

- **Problem:** March 31 closes the financial year, but the Q4 TDS return is due May 31 and Form 16 by June 15. The balance sheet must state TDS payable and receivable correctly at March 31 using incomplete TRACES data, while Section 40(a)(ia) creates a 30 percent disallowance risk on any expense where TDS was required but not deducted or deposited.
- **Logic:** Freeze the TDS payable ledger at March 31 and cross-reference challans against OLTAS to identify Q4 deductions awaiting the April 30 deposit. Reconcile TDS receivable against Form 26AS and AIS, provision for Q4 credits that will only appear after May 31 when deductors file, and classify open items into pending-return, pending-correction, or follow-up categories. Verify every above-threshold expense has TDS deducted to avoid Section 40(a)(ia) disallowance.
- **Config:** March 31 freeze rule on TDS ledgers. Provision register for pending-to-TRACES credits with supporting evidence attached. Section 40(a)(ia) exposure scan on expense ledger above TDS thresholds.
- **Output:** Accurate TDS payable and receivable balance at March 31, provisioned Q4 timing credits with supporting contracts and advice, zero Section 40(a)(ia) disallowance surprises, and a clean audit trail from March 31 close through May 31 Q4 filing.

### ILD International Long Distance Reconciliation: Carrier Settlement for Indian Telecom

Source: https://www.terra-insight.com/insights/telecom-ild-international-long-distance-reconciliation-india/

- **Problem:** Indian ILDOs settle international voice traffic with hundreds of foreign carriers under bilateral USD-denominated commercial agreements with destination-by-destination rate sheets and mixed direct vs hub routing. The reconciliation must tie originating-side CDRs against the foreign carrier's monthly settlement statement, decompose hub-vs-direct, manage FX risk between agreement booking and remittance spot, withhold Section 393(2) Sl. 17 payment code 1057 (non-resident catch-all, rates in force) TDS with DTAA documentation, and discharge GST under reverse charge on ILD inbound under Section 5(3) IGST.
- **Logic:** Aggregate originated international minutes by destination country and routing class (direct vs hub); apply the bilateral agreement rate per minute in USD; reconcile against the foreign carrier's monthly settlement statement; book the INR cost at the period-end RBI reference rate; settle at spot through the AD bank; book the realised FX variance under Ind AS 21; document the no-PE / DTAA / TRC position per remittance with Form 15CA/15CB and withhold Section 393(2) Sl. 17 code 1057 TDS where chargeable; discharge reverse-charge GST under Section 5(3) IGST on ILD inbound and claim ITC.
- **Config:** Foreign-carrier master with bilateral agreement and route policy; USD rate sheet by destination and route; CDR aggregation by destination and route class; FX rate table (RBI reference + spot at remittance); AD-bank remittance ledger; Section 393(2) Sl. 17 code 1057 chargeability matrix with DTAA / TRC / Form 15CA-CB inputs; reverse-charge GST classification for ILD inbound.
- **Output:** A reconciled ILD settlement dashboard showing originated-vs-settled minutes per foreign carrier per destination and route, applied USD rate validation against the bilateral agreement, INR cost at booking and at remittance with the realised FX variance, Section 393(2) Sl. 17 code 1057 TDS position per remittance with DTAA documentation, and reverse-charge GST discharged and ITC claimed under Section 5(3) IGST.

### Telecom IUC (Interconnect Usage Charges) Reconciliation for Indian Operators

Source: https://www.terra-insight.com/insights/telecom-iuc-interconnect-reconciliation-india/

- **Problem:** Indian telecom operators settle billions of inter-carrier minutes every month under TRAI's IUC tariff framework, with mobile-to-mobile termination at Rs 0.06 per minute post-BAK and asymmetric rates for fixed-line and international traffic. The reconciliation must tie Call Detail Records (CDRs) carrier by carrier, net bilateral positions, apply 18% GST on the supply, run reverse charge for international inbound IUC, and withhold Section 393(1) Sl. 6(i) contractor code 1024 (2% for company deductees) TDS on Indian carrier settlements — across CDR-count, rate-applied, traffic-classification and dispute-ageing variance streams.
- **Logic:** Aggregate originated and terminated CDRs by peer carrier and traffic type (M2M, F2M, M2F, intra-LSA, STD, ILD-inbound); apply the TRAI-mandated termination rate per traffic class; net the bilateral position; raise/receive the inter-operator invoice with 18% GST; tie to GSTR-2B for the receiving side and discharge reverse-charge GST for international inbound IUC; withhold Section 393(1) Sl. 6(i) contractor code 1024 (2% for company deductees) TDS on Indian carrier payouts and Section 393(2) Sl. 17 code 1057 on foreign carrier remittances with DTAA documentation; age disputed minutes within the bilateral SLA window.
- **Config:** Peer-carrier master with bilateral SLA windows; TRAI tariff-rate table by traffic class and effective date; CDR ingestion from MSC/switch with traffic-classification tags; bilateral netting ledger; GST classification with reverse-charge flag for ILD inbound; Section 393(1) Sl. 6(i).D(b) code 1024 and Section 393(2) Sl. 17 code 1057 TDS withholding rules; dispute register with ageing and write-back trigger.
- **Output:** A reconciled IUC settlement dashboard showing originated-vs-terminated CDR ties per peer carrier per traffic class, applied-rate validation against TRAI tariff, netted bilateral position, GST charged and ITC claimed, reverse-charge discharge on ILD inbound, Section 393(1) Sl. 6(i).D(b) code 1024 / Section 393(2) Sl. 17 code 1057 TDS withholding, and a dispute-ageing view that feeds the suspense write-back decision.

### Tea Auction Settlement Reconciliation — Kolkata + Coonoor + Guwahati Cornerstone

Source: https://www.terra-insight.com/insights/tea-auction-settlement-reconciliation-kolkata-coonoor-guwahati/

- **Problem:** A tea garden in Assam or the Dooars or the Nilgiris routing production through the Tea (Marketing) Control Order 2003 auction system must reconcile a six-hop consignment cycle across Kolkata, Guwahati, Coonoor, and other licensed auction centres — garden dispatch note against bonded warehouse receipt against broker catalogue against auction prompt (fall of hammer) against 15-day settlement remittance to garden bank net of 1 percent broker commission and warehouse rent debit — while simultaneously computing Section 194H code 1015 TDS at 5 percent on the broker commission, tracking Section 194Q buyer-side purchase code TDS on aggregate above Rs 50 lakh from any single buyer, and filing Rule 89(5) inverted-duty refund claims on 5 percent tea output against 18 percent packaging and power inputs. Manual reconciliation across six hops loses per-lot commission accruals, mis-attributes warehouse rent to the wrong sale-week, under-deducts TDS on broker commission where the garden operates with multiple brokers across centres, and mis-computes Net ITC in the Rule 89(5) formula by including input services or capital goods — exposing the garden and blender to Section 73 or 74 GST notices, Section 201 short-deduction demands, and buyer-side Form 26AS mismatches.
- **Logic:** Ingest the garden's daily manufacturing register and dispatch note by chest count and grade, match against the auction warehouse's inward receipt at Kolkata, Guwahati, Coonoor, Cochin, Coimbatore, Siliguri, or Jorhat by garden mark and invoice number, and carry the lot-level attributes (chest count, net weight, grade, invoice date) as immutable dimensions through to the broker's catalogue entry. Match the broker's catalogue against the auction prompt and settlement statement (sale number, lot number, weighted average realisation, gross auction value, 1 percent broker commission, net remittance). Feed the settlement statement into the garden's bank inflow reconciliation with a 15-day expected-settlement window. Accrue broker commission by broker PAN across sale-weeks, key to Section 18 Sl. 15 payment code 1015 at 5 percent, and generate the monthly Form 26Q TDS remittance and Form 16A issue schedule. Track buyer-wise aggregate purchase value across the financial year for each garden-buyer pair, flag threshold crossings at Rs 50 lakh, and expose the Section 8 Sl. 8 code 1031 TDS credit expected on the garden's PAN for reconciliation with Form 26AS. Extract packaging input GST at 18 percent and tea output GST at 5 percent from the blender's GSTR-1 and GSTR-3B into the Rule 89(5) refund workbook, apply the Notification 14/2022-amended formula (Net ITC excludes input services and capital goods), and generate the GST RFD-01 filing base every month or quarter. Reconcile the warehouse rent invoice line-by-lot against the garden's catalogue-and-prompt register with free-days credit tracking.
- **Config:** Garden master with garden code, plantation area, small tea grower flag, PAN, GSTIN, TAN, and bank account; blending unit master with unit code, GSTIN, e-invoicing threshold flag, and mixed-output position (HSN 0902 packet tea versus HSN 2101 instant tea); auction-centre master with centre code (Kolkata, Guwahati, Coonoor, Cochin, Coimbatore, Siliguri, Jorhat), bonded warehouse network, and sale-week calendar; broker master with broker code, PAN, GSTIN, TDS payment code 1015, and commission rate (standard 1 percent, variations negotiated); buyer master with buyer PAN, TAN, aggregate-purchase running total for the current financial year, and Section 194Q applicability flag; warehouse master with warehouse code, per-chest-per-day rent schedule versioned by effective date, and free-days band per sale-week; grade master (CTC BOPF, PF, D, F, PD; orthodox FTGFOP1, TGFOP, GFOP, FOP); GSTR-1 and GSTR-3B feed for the Rule 89(5) refund workbook; sale-week calendar for auction centres; Section 43B(h) MSME flag on packaging suppliers (many corrugated carton and pouch converters are MSME-registered).
- **Output:** A sale-week and month-end multi-hop tea auction reconciliation pack: garden dispatch register by chest count and grade; bonded warehouse receipt register by lot at each auction centre; broker catalogue and sample-draw register by sale number; auction prompt and settlement register with gross realisation, 1 percent broker commission, net remittance, and 15-day settlement window compliance; broker commission run with code 1015 TDS reconciled against the garden's Form 26Q filing and Form 16A issue log; buyer-wise aggregate purchase register with Section 194Q threshold-crossing flags for each garden-buyer pair; Rule 89(5) inverted-duty refund draft with amended Net ITC formula and packaging plus power input register mapped by tax period; warehouse rent register by lot with free-days credit and per-chest-per-day accrual reconciled against the warehouse rent invoice; year-end summary of Section 43B(h) MSME payment discipline for packaging vendors.

### Test Transaction Ghost: The ₹1 Transaction That Leaves 98 Paise in Production

Source: https://www.terra-insight.com/insights/test-transaction-ghost-98-paise-production-file-streaming-india/

- **Problem:** Engineering teams occasionally run ₹1 or ₹2 test transactions against production payment gateway credentials — most commonly during environment misconfiguration when test/prod switches fail. The refund initiated afterwards refunds the gross amount but the MDR, GST on MDR, and any convenience fee remain retained. A residual 98-paise-per-transaction ghost accumulates in the settlement file with no corresponding invoice, no customer record, and no subscription in the master. Over six months, hundreds of such ghosts create an unexplained rupee-scale variance that finance teams typically absorb into month-end noise, breaking the settlement-to-invoice audit trail required under RBI's Payment Aggregator framework and GSTR-1 outward-supply reconciliation.
- **Logic:** A three-signal detector isolates ghost transactions: an amount-range filter (net below ₹5 or gross below ₹10), a no-corresponding-invoice check against the ERP order table using payment_id and order_id, and a no-customer-record check against the subscription master and CRM. Transactions clearing all three signals are quarantined to a dedicated ledger — not absorbed into revenue or variance. The quarantine ledger is periodically reviewed with engineering to trace the credential-misuse root cause, and the amounts are either reversed at source (where the gateway supports gross-fee refund) or written to a specific 'test-transaction ghost' P&L line with documented origin.
- **Config:** Amount-range thresholds (net residue < ₹5; gross < ₹10), no-invoice lookup against the order and subscription masters, no-customer lookup against CRM email/phone/subscription ID, and a ghost-quarantine ledger with root-cause tags (env-misconfig, load-test, credential-leak, gateway-side test). Optional fourth signal: same-amount burst detection within a short window from the same IP or device fingerprint.
- **Output:** A ghost-quarantine ledger with every 98-paise-class residue captured, tagged with its likely root cause, and either reversed at source or written off with documentation. Settlement file reconciles cleanly to invoice records because ghosts are removed from the main reconciliation flow. GSTR-1 outward-supply totals stop drifting from settlement totals. Month-end variance surfaces genuine reconciliation breaks instead of hiding paise-level noise.

### Three-Way ITC Reconciliation in Excel: Purchase Register, GSTR-2B, and IMS Actions in One Workbook

Source: https://www.terra-insight.com/insights/three-way-itc-reconciliation-excel-india/

- **Problem:** A mid-market Indian enterprise runs GSTR-2B input tax credit reconciliation by pulling a purchase register from the ERP, pulling a GSTR-2B extract from the GST portal, and running a two-way match in Excel. Since the Invoice Management System went live on 14 October 2024, the recipient action log has become a third input — every inbound document requires an Accept, Reject, or Keep Pending action before the monthly cycle closes, and the default action if no action is taken is Accept. A two-way workbook misses two classes of failure the IMS regime introduced: valid invoices wrongly rejected on IMS that then never reach the ITC ledger, and documents defaulted to Accept because no action was taken. Add the Section 16(4) November 30 permanent-loss deadline running on every unfiled supplier row, the Rule 37 180-day payment clock running on every paid supplier row, and the Rule 37A September 30 supplier-filing clock running behind them, and the Excel discipline that used to work needs a re-engineered workbook that operationalises the three-way match, the five-bucket categorisation, and the at-risk queue as first-class outputs.
- **Logic:** Build the workbook around three input sheets keyed on a normalised composite key of supplier GSTIN, invoice number stripped of prefix and suffix noise, invoice date, and taxable-value amount within a tolerance band. Sheet 1 is the ERP purchase register with those four keys plus the IGST/CGST/SGST split, the HSN or SAC code, the payment status and payment date (for Rule 37 ageing), and a Section 17(5) blocked-flag column. Sheet 2 is the GSTR-2B extract copy-pasted from the JSON-to-Excel converter the GST portal ships, with the supplier's GSTIN, invoice number, date, taxable value, and tax split. Sheet 3 is the IMS action log with GSTIN, invoice number, and the recorded IMS action (Accept, Reject, Pending, or Default-Accept). A driver sheet runs XLOOKUP with the composite key against the other two sheets and assigns one of five categorisation buckets to every row — Matched, Supplier not filed, Ghost invoice, IMS reject, IMS pending. Two computed sheets fall out — the at-risk queue keyed to the Section 16(4) deadline with a days-to-deadline countdown, and a supplier follow-up list keyed to unique supplier GSTIN with aggregated exposure. Formulas use XLOOKUP with an exact match, TEXTBEFORE and TEXTAFTER to strip GST invoice-number prefixes and suffixes for normalisation, ROUND to a paise tolerance for amount matching, and TODAY() with an EOMONTH-derived November 30 anchor for the countdown.
- **Config:** Purchase register sheet with columns for invoice number, invoice date, supplier GSTIN, supplier PAN, recipient GSTIN, taxable value, IGST, CGST, SGST, Cess, HSN or SAC code, Section 17(5) blocked flag, payment status, payment date, and remarks. GSTR-2B extract sheet with the same key columns pulled from the portal-generated Excel. IMS action log sheet with invoice number, GSTIN, and action code (A, R, P, or DA for Default-Accept). Supplier master sheet with GSTIN, supplier name, contact email, contact phone, and Rule 37A supplier-filing status. Configuration cell for the applicable financial year (used to derive the Section 16(4) target date). Configuration cell for the amount tolerance in rupees (typically 1 rupee absorbable, 10 rupees flagged). Named ranges on every input sheet so the driver formulas reference stable names rather than volatile cell ranges.
- **Output:** A driver sheet with one row per purchase register invoice, categorised into one of five buckets and colour-banded. An at-risk queue that filters the Supplier-not-filed bucket and shows days-to-deadline against 30 November, banded into over-90-days-informational, 61-to-90-days-Tier-1, 31-to-60-days-Tier-2, and under-30-days-Tier-3. A supplier follow-up list with unique supplier GSTIN, count of unfiled invoices, total exposure in rupees, and a contact placeholder ready for mail-merge. An IMS action queue that surfaces the Pending and Default-Accept rows for the current cycle. A Section 17(5) exclusion list. A reconciled ITC total that populates GSTR-3B Table 4 for the tax period. Every sheet refreshes on open, so a Monday morning refresh reflects the exposure state the finance team is walking into that week.

### Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)

Source: https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india/

- **Problem:** Tier-1 auto suppliers send semi-finished parts to deep sub-vendor tiers — plating, heat-treatment, machining, painting, anodising, phosphating — sometimes multi-hop across two or three job-workers before return, under Section 143 of the CGST Act with a one-year input return clock (three years for capital goods) beyond which the dispatch is deemed a supply with 18% interest; reconciling the challan-out register, the inter-job-worker movement challans, the physical-return GRN, the conversion-charge invoice with Section 393(1) Sl. 6(i) codes 1023/1024 TDS, and the quarterly ITC-04 is a multi-way control that breaks once monthly challan volume runs into the thousands.
- **Logic:** Tag every Section 143 dispatch challan at origin with job-worker GSTIN, process type, input/capital-goods flag, quantity and a one-year (or three-year) statutory clock from the original dispatch date; track multi-hop parts across each inter-job-worker challan against the single original clock; match return GRN to dispatch on quantity within process-loss tolerance; price the conversion invoice against returned quantity and deduct Section 393(1) Sl. 6(i) TDS at 1% or 2%; roll open positions into the quarterly ITC-04; alert on challans approaching the statutory window.
- **Config:** Job-worker master with GSTIN, PAN, process type and Section 393 TDS rate; challan series per principal GSTIN; statutory clock per challan (1 year inputs, 3 years capital goods, none for jigs/fixtures/moulds/dies); multi-hop routing map per part; process-loss tolerance per process; conversion-charge rate card; ITC-04 quarterly due-date calendar; alert thresholds 60 and 30 days before the window.
- **Output:** A daily job-work dashboard showing open dispatches by job-worker and by hop, days remaining to the one-year window, return-versus-dispatch reconciliation within process-loss tolerance, conversion invoices matched to returned quantity with Section 393(1) Sl. 6(i) codes 1023/1024 TDS, and the quarterly ITC-04 position reconciled to the challan registers across the full multi-hop chain.

### Time-and-Material Billing Reconciliation for Indian IT Companies

Source: https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india/

- **Problem:** T&M billing for 200+ consultants across 15 clients generates 3,000+ timesheet line items per month, and rate card variations, forex conversions, and TDS deductions create systematic reconciliation gaps.
- **Logic:** Match approved timesheet hours to invoice line items by consultant and rate, reconcile bank receipt against invoice after TDS and forex adjustments, validate rate card against contract terms.
- **Config:** Section 194J at 10%, FIRC for USD clients, FEMA 9-month realization rule, rate card master per client-consultant pair, tolerance for forex conversion variance.
- **Output:** Timesheet-to-invoice-to-cash reconciliation, rate card compliance report, forex gain/loss register, and TDS receivable tracker by client.

### Tiruppur Knitwear Cluster Reconciliation — MSME and Section 43B(h)

Source: https://www.terra-insight.com/insights/tiruppur-knitwear-cluster-reconciliation-msme-msme43bh/

- **Problem:** A mid-size Tiruppur knitwear exporter running a 6-hop MSME job-work chain — Tier-1 garment factory (may itself be MSME), dyeing MSME, embroidery MSME, cutting MSME, stitching MSME, packing MSME — faces an independent Section 43B(h) 45-day payment clock on every bill from every micro or small vendor at every hop. A delayed brand payment upstream typically cascades into delayed payments downstream, and each hop that misses its own 45-day window suffers its own income-tax deduction disallowance in the year of accrual plus a compound-interest liability to the supplier at three times the RBI bank rate under MSMED Act Section 16. Manual payables tracking across 25 to 40 unique Udyam-registered job-workers loses vendor classification, misses the appointed-day trigger, and typically over-claims deductions that surface as year-end audit adjustments or Section 43B(h) tax notices.
- **Logic:** Maintain a Udyam register per job-worker with URN, classification (micro/small/medium), certificate PDF, and effective-from date; auto-flag every posted payable to a micro or small vendor with a 43B(h) marker. Start a 45-day clock on the acceptance date of every bill (goods received note or service acceptance) and track it against the payment date. Surface bills at 30, 40, and 44 days as pre-breach warnings; at Day 46 flag the bill for automatic year-end 43B(h) disallowance schedule. Compute MSMED Section 16 compound interest on every breached bill from the appointed day to date-of-payment at three times the RBI bank rate with monthly rests. Cascade-monitor: when a brand-side receivable ages past its expected pay date, project the cascade impact on downstream MSME payables in the same 30 to 45-day window and pre-emptively flag hops likely to breach.
- **Config:** Vendor master with PAN, GSTIN, Udyam Registration Number, classification (micro/small/medium/non-MSME/unknown), classification-effective-from date, certificate PDF reference, NIC primary code, and 43B(h) coverage flag (True for micro/small, False for medium/non-MSME); AP system field for goods-received-note date and separately for invoice-receipt date (the earlier of the two is the acceptance trigger for the 45-day clock, subject to Section 2(b) MSMED Act deemed acceptance of 15 days from delivery if buyer raises no objection); appointed-day computation as the day after the 45-day window from acceptance; RBI bank-rate feed (verify against the latest RBI notification) with monthly-rest compounding formula; year-end 43B(h) disallowance schedule that lists every unpaid MSME bill past 45 days as of 31 March and moves the deduction to the year of actual payment.
- **Output:** A pre-close 43B(h) audit pack listing every MSME job-worker bill posted in the year with acceptance date, 45-day appointed day, payment date (if paid) or as-of-31-March status (if unpaid), Section 43B(h) disallowance amount (deduction shifted to next year), Section 16 interest accrual from appointed day to close, and cumulative cascade projection where downstream MSME bills are still open pending upstream receivable collection. Real-time dashboard shows open MSME bills bucketed at 0-30 days, 31-40 days, 41-44 days, and past-45-days with the count and value at each bucket by job-worker and by hop-tier. Year-end tax pack ties the 43B(h) disallowance directly to the ITR schedule and surfaces the Section 16 interest liability disclosure required under the CARO 2020 reporting framework in the audit report.

### Tiruppur Knitwear Export Reconciliation

Source: https://www.terra-insight.com/insights/tiruppur-knitwear-export-reconciliation/

- **Problem:** A mid-size Tiruppur knitwear exporter at ₹80 crore FOB annual turnover ships 340 shipping bills of Chapter 61 knitted garments in a financial year, and the finance controller must reconcile four parallel export-incentive schemes — RoSCTL (approximately ₹2.88 crore at 3.6 percent), RoDTEP under Appendix 4R (approximately ₹3.36 crore at 4.2 percent), Rule 89(5) inverted-duty refund (approximately ₹95 lakh monthly cumulative), and e-BRC realisation (average lag 5.2 months against FEMA 9-month window) — plus the underlying job-work TDS chain under codes 1023, 1001, and 1031, plus e-invoicing IRN generation for every export invoice above the ₹5 crore threshold. A single shipping bill mis-declared, a single IRN gap, or a single e-BRC realisation past the 9-month FEMA window disrupts approximately ₹21,000 to ₹35,000 of incentive recovery per bill, and cumulative gaps at year-end can strip ₹40 to ₹60 lakh from the recoverable stack of ₹7.2 crore.
- **Logic:** Build a shipping-bill master keyed by SB number and date, carrying HS code, FOB value, incentive-scheme flags (RoSCTL applicable Yes/No, RoDTEP Appendix 4R vs 4RE, Rule 89(5) applicable), and the IRN reference for the linked export invoice. Ingest the RoSCTL claim register, the RoDTEP claim register, the GST RFD-01 monthly filing, and the e-BRC feed from the AD bank; reconcile each incentive against the shipping-bill master. Track e-BRC ageing against the FEMA 9-month window with alerts at 6, 7, and 8 months from shipping-bill date. Feed the TDS payment-code register (1023 for job-work, 1001/1002 for transporter contracts, 1031 for Section 194Q buyer TDS) and reconcile against Form 26AS at each vendor's PAN quarterly. Cross-check GSTR-1 Table 6A (zero-rated exports) against the shipping-bill master monthly for auto-population accuracy.
- **Config:** Shipping-bill master with SB number, SB date, HS code, FOB in foreign currency and INR, invoice reference, IRN, buyer country, incentive-scheme flags; RoSCTL rate table by HS code; RoDTEP Appendix 4R and 4RE rate tables by HS code with scheme-eligibility flag per exporter status (DTA vs AA/EOU/SEZ); Rule 89(5) formula parameters — turnover of inverted-rated supply, Net ITC exclusion set (input services, capital goods), adjusted total turnover, output tax payable on inverted-rated supply; e-BRC bank-feed integration with AD bank; TDS payment-code master (1023, 1024, 1001, 1002, 1014, 1031) with rate slabs; e-invoicing IRP credentials for IRN generation; FEMA ageing thresholds at 180, 210, 240, and 270 days from SB date.
- **Output:** A month-end export-incentive reconciliation pack: RoSCTL claim register with SB-wise entitlement and scrip-issuance status; RoDTEP claim register (Appendix 4R for DTA shipments) with SB-wise entitlement and encashment status; Rule 89(5) monthly refund claim draft with the GST RFD-01 numerator, denominator, and computed max refund; e-BRC reconciliation with ageing bucket by SB (0-3, 3-6, 6-9 months); TDS payment-code tally by vendor PAN with Form 26AS reconciliation status; e-invoicing IRN gap report (invoices booked but IRN not generated, IRNs generated but not booked). Combined stack recovery on the ₹80 crore FOB base surfaces at approximately 9 percent (₹7.2 crore), and any deviation from the expected recovery is bill-level traceable.

### Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them

Source: https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements/

- **Problem:** Tobacco spending and related controlled substance transactions represent a discretionary expense allocation and potential health risk proxy that, when material relative to income, reduces effective repayment capacity in ways that FOIR from EMI obligations alone does not capture.
- **Logic:** Match transaction descriptions against cigarette and tobacco brand names, retail outlet names associated with tobacco products, hookah lounge names, and terms associated with controlled substance procurement through non-pharmaceutical channels. Explicitly exclude licensed pharmacy names to prevent false-positive flagging of legitimate healthcare spending.
- **Config:** Enable for NBFC and HFC underwriting. Maintain pharmacy whitelist to prevent healthcare misclassification. Review alongside alcohol and gambling signals for complete vice spending aggregate. Set income-share threshold based on lender policy.
- **Output:** Tobacco and controlled substance risk section in the credit report with transaction count, total debit, top five matched terms, and aggregate discretionary allocation across vice spending categories.

### Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams

Source: https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india/

- **Problem:** 9% of GSTR-2B matches, most TDS rounding variances, and many bank-charge differences are sub-₹5 predictable variances. Reviewing each manually consumes analyst time with zero control value; setting tolerance too loosely masks genuine discrepancies.
- **Logic:** Define per-type tolerance bands: ₹5 for TDS rounding, ₹2 per GSTR-2B invoice line, amount-specific for bank charges. Never apply tolerance to GSTIN or invoice-number mismatches, unidentified credits or debits, or any single variance above ₹100. Log every tolerance-resolved match with rule, variance, and auto-resolution timestamp for audit.
- **Config:** Tolerance library per reconciliation type, hard exclusions (GSTIN, invoice number, unidentified items), monthly audit log of tolerance-resolved volume and value.
- **Output:** 15–30% smaller exception queue, analyst time redirected to genuine discrepancies, and a documented tolerance audit trail accepted by statutory auditors.

### Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers

Source: https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india/

- **Problem:** One-time tooling cost of ₹5-50 crore is recovered over OEM-committed volume through per-part amortisation, but commercial complexity overlays four ledgers — Section 32 depreciation on capitalised tooling, per-part recovery against contractual volume cap, GST 18% on tooling supply or 28% on bundled part price, and Rule 43 capital-goods ITC amortised over 60 months — plus shortfall risk when actual lifting falls below commitment and end-of-programme buyback or Section 394 scrap TCS at 1%.
- **Logic:** Reconcile tooling asset register per programme against per-part amortisation recovery and contractual volume cap, maintain Section 32 depreciation schedule for capitalised tools, decide GST 18% upfront supply vs bundled-in-part-price structure at programme award, run Rule 43 60-month capital-goods ITC amortisation with proportionate reversal for any exempt output, age shortfall exposure when cumulative lifting trails commitment, and close out at programme exit with buyback consideration, residual book value, and Section 394 code 1071 scrap TCS at 1% on disposal.
- **Config:** Tooling asset master per programme with ownership flag (OEM vs supplier), commercial structure flag (upfront vs bundled), capitalised cost, per-part amortisation rate, contractual cumulative volume cap, Section 32 depreciation method, GST treatment flag, Rule 43 60-month ITC schedule, shortfall trigger at 80% of programme life, scrap-disposal workflow with Section 394 code 1071 TCS calculation.
- **Output:** A monthly tooling reconciliation dashboard per programme showing capitalised cost, cumulative parts shipped vs contractual cap, recovery percentage, Section 32 depreciation booked, Rule 43 ITC amortisation booked with any exempt-output reversal, shortfall exposure at programme life remaining, and end-of-programme disposal queue with buyback or scrap action and Section 394 TCS deposit.

### Tooling Cost Recovery and Amortisation for Auto-Component Programmes: Models Explained

Source: https://www.terra-insight.com/insights/tooling-cost-recovery-amortisation-auto-component-india/

- **Problem:** Tooling investment in Indian auto-component programmes runs into hundreds of crores per Tier 1 across multiple OEM programmes, recovered through per-part amortisation or upfront tooling invoice, with downstream consequences under the Income Tax Act 2025 depreciation framework, GST capital-goods Rule 43 (60-month ITC amortisation), tooling buyback at programme end, and shortfall negotiation when OEM under-lifts committed volume — each layer running on a different ledger and reconciling differently.
- **Logic:** Classify each tool by ownership model (supplier-owned / OEM-owned / hybrid) at programme start; in supplier-owned mode capitalise the tool, run depreciation under Income Tax Act 2025 framework, and track per-part amortisation realised against tool cost; in OEM-owned mode raise tooling tax invoice at HSN 8480/8466 at 18 percent, configure OEM Rule 43 capital-goods ITC schedule (60-month) and reverse exempt-supply attributable portion monthly; track cumulative lifted volume against committed volume and surface shortfall when under-lift opens; at programme end execute tooling buyback or scrap in line with the agreement; reconcile tooling-revenue recognition (amortisation accrual) separately from depreciation (timing deduction).
- **Config:** Tool master with cost, ownership model, HSN, committed volume, per-part amortisation, fixed-asset register link; programme-volume tracker per OEM with cumulative lifted volume; per-part amortisation accrual workflow; Rule 43 60-month capital-goods ITC schedule; shortfall computation engine triggering debit note at programme end or contract milestone; depreciation books (Income Tax Act 2025 and Companies Act 2013) maintained separately; buyback / scrap workflow at programme close.
- **Output:** A per-programme tooling dashboard showing tool cost, ownership model, committed volume, lifted volume, cumulative amortisation realised, balance to recover, projected shortfall, Rule 43 ITC reversal status (where applicable), depreciation booked under both frameworks, and a programme-end queue for buyback or scrap with shortfall debit note generation.

### Tower Infrastructure Revenue Reconciliation: Indus Towers, ATC, Brookfield Telco

Source: https://www.terra-insight.com/insights/tower-infrastructure-revenue-reconciliation-india/

- **Problem:** Indian tower infrastructure providers own and operate over 750,000 towers under Master Service Agreements with telecom operators that price each slot, apply tenancy-ratio discounts for additional tenants, pass through energy-and-fuel costs, and run monthly invoicing at the tower-slot level. Revenue reconciliation must tie slot inventory and Tenancy Orders against the invoice, validate the slot rate at the operator's tenancy position, decompose energy pass-through against meter readings and DG fuel allocation, withhold Section 393(1) Sl. 6(i) contractor code 1024 (2% for company deductees) TDS on the rental side, evaluate Ind AS 116 lease classification for the operator-lessee, and tie 18 percent GST output across all of it.
- **Logic:** Maintain a tower-slot master with location, MSA reference, tenancy position, slot rate and energy methodology; tie active Tenancy Orders against the slot master; bill monthly per the MSA rate matrix; ingest tower energy meter readings and DG fuel and allocate by tenancy-ratio weight; raise energy pass-through with monthly bill or year-end true-up per the MSA; raise tax invoice at 18 percent GST; ensure operator-side Section 393(1) Sl. 6(i).D(b) code 1024 TDS at 2 percent is correctly withheld on the rental net of GST and tied to 26AS by operator TAN; track Ind AS 116 lessee classification per slot; reconcile disputed slot rates and energy allocations within the MSA SLA window.
- **Config:** Tower-slot master with location, MSA reference, tenancy mix; MSA rate matrix per operator with single/double/triple/additional-tenant pricing; Tenancy Order register; tower energy meter ingestion and DG fuel ledger with tenancy-ratio allocation; Section 393(1) Sl. 6(i).D(b) code 1024 TDS rule on rental net of GST with 26AS reconciliation by operator TAN; Ind AS 116 lease assessment per slot for operator-side accounting; 18 percent GST telecom-passive-infrastructure classification.
- **Output:** A reconciled tower-revenue position showing slot-by-slot tenancy and applied rate against the MSA matrix, monthly energy pass-through allocated by tenancy ratio with meter and DG fuel evidence, Section 393(1) Sl. 6(i).D(b) code 1024 TDS receivable per operator TAN reconciled to Form 26AS, Ind AS 116 lessee classification per slot for operator-side accounting, and 18 percent GST output liability tied through GSTR-1 to GSTR-3B.

### Toyota Kirloskar Motor Supplier Reconciliation: TPS, Heijunka and Indian Tax Overlay

Source: https://www.terra-insight.com/insights/toyota-kirloskar-supplier-reconciliation-india/

- **Problem:** Tier-1 suppliers to Toyota Kirloskar Motor (TKM) operate inside a TPS-derived commercial regime — Bidadi as the operating plant, kanban-pull as the primary release mechanism rather than MRP-push, heijunka production levelling dampening demand variance, milk-run logistics consolidating Tier-2 into Tier-1 hubs, consumption-based weekly billing rather than dispatch-based billing, annual cost-down negotiation in lieu of monthly RMPV pass-through, the typical 45-day post-GRN payment cycle, and Section 393(1) Sl. 6(i) codes 1023/1024 TDS overlay on the conversion charge. A ₹85 crore annual TKM book demands programme-level decomposition, kanban-pull-to-GRN-to-invoice reconciliation, and a cost-down tracker per scheduling agreement.
- **Logic:** Decompose each TKM settlement at the programme level (Innova Crysta / Innova Hycross / Fortuner / Hilux / Camry / Glanza / Urban Cruiser Hyryder / Vellfire), tie each kanban-pull consumption event to the supplier's dispatch and the resulting invoice line, classify debit reasons against the TKM taxonomy, validate JIT shortage debits against milk-run pickup timing rather than dock arrival timing, maintain a cost-down tracker per scheduling agreement showing achieved vs annual target, calendar Section 34 GST credit notes per accepted debit, and reconcile Form 168 TDS deductions under Section 393(1) Sl. 6(i) codes 1023/1024 against books.
- **Config:** TKM customer master with sub-records per vehicle programme, kanban-pull-to-invoice mapping from the supplier's consumption-billing module, milk-run pickup log linked to ASN and dispatch events, debit-note reason taxonomy aligned to TKM Supplier Quality Manual codes, cost-down tracker per scheduling agreement with annual / semi-annual target and achieved-to-date, FOMP / warranty back-charge register per programme, Form 168 TDS register with Section 393(1) Sl. 6(i) codes 1023/1024 reconciliation, Section 34 GST credit-note calendar at 30 November of next FY.
- **Output:** A per-programme TKM settlement view showing billed vs paid vs reason-coded debit per period, programme-level cumulative margin tracker with cost-down attainment attribution, kanban-pull-to-GRN-to-invoice reconciliation, milk-run pickup-time-to-dock-arrival logistics variance register, Form 168 TDS register reconciled to books under Section 393(1) Sl. 6(i) codes 1023/1024, and a Section 34 GST credit-note action queue keyed to approaching cutoff.

### TPA Settlement Reconciliation for Indian Hospitals

Source: https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india/

- **Problem:** TPA batch settlements aggregate 50-500 claims into a single bank credit with deductions for co-pay shortfalls, disallowances, and TDS under Section 194J at 10%.
- **Logic:** Ingest TPA sidecar file, disaggregate batch credit by patient ID and claim reference, match to hospital billing system, classify variances as co-pay shortfall, disallowance, or TDS deduction.
- **Config:** 19+ TPA-specific file formats, TDS 10% under 194J, settlement window 15-90 days, co-pay tolerance per scheme.
- **Output:** Per-claim settlement status, TDS receivable register for 26AS matching, disallowance analysis by TPA, revenue leakage report.

### Trade Promotion Accrual vs Payout Reconciliation for Indian FMCG

Source: https://www.terra-insight.com/insights/tpm-accrual-vs-payout-reconciliation-fmcg-india/

- **Problem:** Indian FMCG brands accrue trade-spend in the general ledger every period as a percentage of secondary sales — typically 8 to 15 percent depending on category and geography — but distributor claim payouts arrive in lump sums 45 to 120 days later, frequently netted against next-cycle dispatch invoices rather than paid separately. The accrual register and the claim register live in different systems (SAP CO-PA versus a TPM tool or distributor portal), Section 15(2) CGST determines per scheme whether the amount reduces taxable value or sits inside it, and stale claims past 90 days accumulate without provision unless an ageing discipline is enforced — leaving the year-end accrual liability over- or under-stated by 12 to 30 percent of gross trade spend.
- **Logic:** Build a monthly accrual register keyed by scheme code, distributor GSTIN, geography, and category; book accrual on Day 0 of the secondary sale at the scheme percentage in force. In parallel, parse the distributor claim register from the portal — claim submission date, scheme reference, gross claim, supporting evidence flag. Match each claim to its accrual line by scheme code and distributor; classify the net of each cycle into payout via credit note (Section 15(2) qualifying), payout via cash, claim rejected, or claim pending. Run ageing buckets — 0-30, 31-60, 61-90, 90+ days from claim submission — and provision against the 90+ bucket per Ind AS 37. Cross-foot the accrual GL liability to the open claim universe plus the stale-claim provision before each month-end close.
- **Config:** Scheme master with code, percentage, geography, category, validity dates, and Section 15(2) treatment flag (invoice-recorded, post-supply with agreement, or non-qualifying); distributor master with GSTIN, PAN, claim-portal ID, and Section 393(1) Sl. 18 (194H) TDS rate; secondary-sales feed from DMS by distributor by SKU by period; claim-register feed from the brand's TPM portal with submission date and evidence flag; ageing bucket configuration (0-30 / 31-60 / 61-90 / 90+); stale-claim provision rule per category; GST credit-note linkage to GSTR-1 cycle; pre-22-September 2025 versus post-22-September 2025 rate switch on the affected HSNs.
- **Output:** A month-end TPM reconciliation pack: opening accrual liability, period accrual booked, period payouts (split by credit note / cash / netted), claims rejected, claims pending, stale-claim provision movement, and closing liability — reconciled to the GL trade-spend account. Per-distributor ageing buckets surface stuck claims with submission dates and evidence gaps. A Section 15(2) per-scheme treatment register feeds the GST credit-note cycle and the GSTR-1 amendment, and the 90+ day bucket feeds CARO 2020 disclosure and the year-end audit pack.

### TPM Debit Note Reversal for Rejected Distributor Claims in FMCG

Source: https://www.terra-insight.com/insights/tpm-debit-note-reversal-fmcg-rejected-claims/

- **Problem:** When a distributor scheme claim fails validation on the brand's TPM portal — missing POS photographic evidence, retailer code mismatch against the DMS master, claim submission outside the scheme validity window, scheme-rule failure on slab thresholds, or duplicate submission — the brand must reverse the trade-spend accrual booked at scheme launch. Where the claim was already paid in a prior cycle via a Section 15(2) qualifying credit note, the brand must additionally issue a Section 34 CGST debit note to the distributor to neutralise the prior value reduction, recover the GST liability that was reduced earlier, and amend GSTR-1 in the rejection month. Without a structured debit-note reversal discipline, the trade-spend GL liability stays inflated, the GST liability stays under-stated, and the distributor relationship sours when the next-cycle invoice gets unexpectedly netted.
- **Logic:** Build a rejected-claim register keyed by claim ID, scheme code, distributor GSTIN, rejection reason code, and prior-settlement status (never settled / credit note issued / cash-paid with TDS). For never-settled rejections, reverse the accrual line by scheme code and distributor — no GST instrument required. For credit-noted-and-now-reversed claims, issue a Section 34 debit note referencing the original credit-note number and the underlying invoices; raise an accrual reversal in the same period; queue the debit note for GSTR-1 Table 9B of the issue month at the rate of the original underlying invoice; flag dispute and notify the distributor with the reason-code report. For cash-paid claims with TDS, reverse the trade-spend P&L, recover the gross from the distributor via the next dispatch invoice, and file a TDS return correction for the affected quarter under Section 393(1) Sl. 18. Maintain a per-claim dispute log so distributor escalations carry the full evidence trail.
- **Config:** Rejection reason master with codes for missing evidence, code mismatch, late submission, scheme-rule failure, and duplicate submission; settlement-state flag on each claim (never settled / credit note / net-off / cash with TDS); scheme master with Section 15(2) treatment flag and validity dates; original credit-note linkage on every TPM credit note for later debit-note reference; Section 34 debit-note number series separate from regular sales invoices; GSTR-1 Table 9B feed for the rejection month at the original invoice rate; TDS return correction trigger when reversal touches a cash commission line; dispute-log workflow with evidence attachments and distributor acknowledgement; pre-22-September 2025 versus post-22-September 2025 rate flag on the affected HSNs so the debit note carries the correct historical rate.
- **Output:** A rejected-claim reversal pack per month: total rejections by reason code, accrual reversal amount by scheme and distributor, debit notes issued (count, value, GST amount), debit notes pending for GSTR-1, TDS return corrections raised, dispute log status (open / acknowledged / escalated / settled), and the closing impact on the trade-spend GL liability. Distributor-level statements show the rejection reasons with evidence references so the field sales team can resubmit cases where evidence is recoverable. The pack feeds the GSTR-1 Table 9B export for the rejection month, the rate-aligned GSTR-3B liability uptick, and the CARO 2020 disclosure on disputed scheme claims.

### Transfer Pricing for IT Services Captive: Section 92CA Compliance and APA

Source: https://www.terra-insight.com/insights/transfer-pricing-it-services-section-92ca-india/

- **Problem:** Indian IT services captives operating as cost-plus subsidiaries of overseas parents face mandatory TPO references under Section 92CA, must file Form 3CEB annually, and must choose between safe harbour, an APA, or full TP litigation to determine the arm's length price.
- **Logic:** Benchmark the captive's operating margin against comparables using TNMM or other prescribed methods, document the ALP analysis in the Section 92D file, file Form 3CEB by 31 October, and evaluate safe harbour (Rule 10TD) versus APA (Sections 92CC and 92CD) for long-term certainty.
- **Config:** Section 92CA mandatory TPO reference, Rule 10TD safe harbour 17-18% margin band up to ₹200 crore, Section 92D documentation rules, Form 3CEB Section 92E annual filing, Sections 92CC and 92CD APA framework (unilateral, bilateral, multilateral).
- **Output:** ALP benchmarking file with TNMM analysis, Form 3CEB report, safe harbour or APA decision memo, and an inter-company billing reconciliation against the agreed margin.

### Transmission Charges Reconciliation: CTU/STU/PGCIL Billing for Open-Access Customers

Source: https://www.terra-insight.com/insights/transmission-charges-cstu-cwc-pgcil-india/

- **Problem:** Indian open-access industrial consumers face a structural transmission reconciliation gap — PGCIL bills inter-state PoC charges quarterly with node-wise rates under the CERC Sharing Regulations 2020, the State Transco bills intra-state transmission monthly under a separate SERC tariff order, the DISCOM bills wheeling and cross-subsidy surcharge and additional surcharge on a third cycle, banking charges accrue in kind on injection-drawal mismatches, and transmission losses are settled in energy via the POSOCO Regional Energy Account. A 10 MW consumer routinely sees 4-7% variance between expected and billed transmission stack with no single ledger that ties the rails together.
- **Logic:** Build a withdrawal-node and injection-node master with the applicable PoC rate per quarter, schedule drawal against trader confirmation and IEX/PXIL trade ID, apply the regional loss factor to derive required injection, reconcile PGCIL inter-state bill (PoC + loss + reactive) against schedule, reconcile STU bill (transmission charge per ₹/kW/month or ₹/kVAh) against connected load and energy drawn, reconcile DISCOM bill (wheeling + CSS + AS) under the current SERC tariff order with effective-date control, track banked injection against drawal claims with banking charge in kind, and tie the Regional Energy Account back to the trader's settlement confirmation.
- **Config:** Connection-point master with withdrawal node code, sanctioned load, voltage level, host DISCOM and host state, PoC rate table by quarter and node (long-term ₹/MW/month, short-term ₹/MWh), regional loss factor table per POSOCO region, STU transmission tariff order with effective date and ₹/kW/month rate by voltage, DISCOM wheeling tariff with CSS and AS components by consumer category, banking regulation with charge percentage and time-window restrictions per state, trader/IEX/PXIL trade register with schedule ID, REA ingest per settlement period, and SERC tariff order register with effective-from and effective-to dates.
- **Output:** A monthly reconciled view per connection point showing scheduled drawal vs REA actual vs trader confirmation, PGCIL bill ties under PoC rate × schedule + loss component, STU bill tie against tariff order × connected load and drawal, DISCOM bill tie showing wheeling + CSS + AS split with each rate validated against the current SERC order, banking ledger showing injected-banked-withdrawn-expired energy in kWh and the in-kind banking charge retained by DISCOM, and a transmission-stack variance bridge from expected to billed with each delta coded by reason — node reclassification, tariff revision, schedule deviation, loss-factor change, or banking expiry.

### Trent Westside Apparel VMI Reconciliation

Source: https://www.terra-insight.com/insights/trent-westside-fashion-vmi-reconciliation/

- **Problem:** A Tier-2 garment supplier VMI-places 65,000 units at a Trent Westside distribution centre in October under a Rule 55 delivery challan and retains legal title until consumption. Monthly consumption call-offs across November, December, and January draw down the stock at different unit counts and unit rates, and each call-off must convert to a Section 31 tax invoice at the correct time of supply under Section 12 CGST — with GST charged at the call-off date rate, invoice flowing into GSTR-1 for the call-off month, and Trent's ITC becoming available in GSTR-2B/3B in the same period. Residual stock at season-end must be closed either by return delivery challan (pre-invoicing units) or by Section 34 credit note (post-invoicing sales return). A supplier that manages this in a spreadsheet loses call-off timing, invoices in the wrong tax period, mis-classifies residual returns as credit notes instead of challan returns, and drifts on Section 194Q (payment code 1031) TDS reconciliation once the ₹50 lakh annual threshold is crossed.
- **Logic:** Build a VMI dispatch register keyed by the parent Rule 55 outbound challan reference at DC placement; expand each parent challan into an expected drawdown profile aligned with the season sell-through calendar. Ingest every consumption call-off notification from the brand, match by SKU, quantity, and running balance against the parent challan, and generate the Section 31 tax invoice within the day of the call-off. Flag every invoice with the Section 12 time-of-supply date and validate that the GSTR-1 filing period aligns. Track running balance at the DC by SKU; at season-end, reconcile the closing balance to the physical stock take shared by the DC and issue either a Rule 55 return-inward challan (for pre-invoicing units) or trigger a Section 34 credit note (for post-invoicing sales returns). Cross-check the invoice cumulative value against the ₹50 lakh Section 194Q threshold to identify the tipping invoice from which the buyer's TDS deduction under payment code 1031 becomes applicable, and reconcile the deducted TDS against Form 26AS at the supplier's PAN monthly.
- **Config:** Brand and DC master with GSTIN, PAN, PIN code, and delivery address; SKU master with HSN, unit-of-measure, standard unit rate for the season, and VMI parent challan reference; VMI dispatch register with outbound Rule 55 challan (challan number, date, HSN, quantity, declared taxable value, e-way bill reference); consumption call-off ingest schedule (weekly or monthly per the arrangement); Section 12 time-of-supply rule engine configured to earlier-of invoice-date or call-off date; Section 31 invoice issue window (same-day of call-off preferred, no later than the removal or making-available date); Section 34 credit note issue window (30 November following FY of original supply); Section 194Q payment code 1031 threshold tracker (₹50 lakh per PAN per FY) with 0.1 percent deduction rate; TDS credit reconciliation against Form 26AS at PAN level monthly.
- **Output:** A month-end VMI reconciliation pack: opening balance at DC by SKU by parent challan, monthly consumption call-off (with invoice numbers and time-of-supply dates), invoice value and GST charged, running balance at DC by SKU, cumulative FY purchase value against the Section 194Q threshold, buyer TDS deducted under payment code 1031 with 26AS reconciliation status. At season-end, closing balance at DC is reconciled to physical stock take; residual units returned pre-invoicing close on a return-inward Rule 55 challan; post-invoicing sales returns close on a Section 34 credit note within the 30 November following-FY deadline. The pack feeds the supplier's GSTR-1 for the invoicing month, the customer's GSTR-2B mirror check, and the statutory audit workpapers for revenue recognition timing under Ind AS 115.

### University Fee Collection Bank Reconciliation: Multi-Bank Account Pooling for Indian Institutions

Source: https://www.terra-insight.com/insights/university-fee-collection-bank-reconciliation-india/

- **Problem:** Indian universities must reconcile fee inflow across 4-8 fee-collection bank accounts (SBI, HDFC, ICICI typically), virtual-account credits keyed by student roll number, daily sweeps to the main operating account, fee-management-system receipts against bank credits, and an orphan-credit register for cases where credit cannot be matched to a student — at scale across 20,000-50,000 students with auditor and C&AG visibility.
- **Logic:** Per fee-collection account: ingest daily statement and VA-MIS, match credits to student records by VA prefix or narration, post receipts in fee-management system, identify unmatched credits to the orphan-credit register; reconcile daily sweep amount to receiving operating account inward credit; produce orphan-credit ageing report and resolution workflow; reconcile cash-counter receipts to bank deposit slips.
- **Config:** University fee bank reconciliation configuration with multi-bank statement ingestion (SBI, HDFC, ICICI native formats including MT940, CAMT.053, Excel and CSV), virtual-account MIS file ingestion with prefix-based student mapping, daily sweep schedule, main operating account inward reconciliation, orphan-credit register with ageing buckets, cash-counter to bank-deposit-slip reconciliation, audit evidence file generator.
- **Output:** A daily and monthly close where every fee-collection account ties credit roll-up to fee-management receipts and sweep evidence, every virtual-account credit is mapped to a student or parked in the orphan-credit register with ageing, the main operating account inward sweeps reconcile to fee-collection outward sweeps, and the audit evidence file produces per-account drill-down for statutory and C&AG audits.

### UPI AutoPay vs eNACH for ₹149-₹2,499 Subscription Tickets: Cost and Reliability Comparison

Source: https://www.terra-insight.com/insights/upi-autopay-vs-enach-149-2499-subscription-tickets-india/

- **Problem:** Indian subscription merchants in the ₹149 to ₹2,499 ticket band — OTT, B2B SaaS, edtech, hospitality membership, consumer NBFC EMI — pick a recurring-debit rail at contract stage without a quantified per-rail unit-economics model, then absorb a structurally avoidable fee burden when they default to eNACH at scale. The ratio between UPI AutoPay total cost and eNACH total cost at this ticket band is typically of the order of ten to fifteen times in AutoPay's favour for a book with eighteen thousand active subscribers, and the reliability gap on first-attempt success reinforces the cost gap because every eNACH rejection is a fresh fee event.
- **Logic:** Build a per-rail unit economics model with three line items per rail — successful-debit cost, failed-debit cost, and platform fee — using contracted rates for UPI AutoPay and the published per-debit sponsor-bank charge for eNACH. Multiply by expected success and rejection rates for the relevant customer segment. Apply the monthly active mandate base. Compute the rail-mix-weighted total against the contracted blended rate and surface the gap. Reconcile the actual fee column on the settlement file against the modelled expectation per debit, by rail. Flag any non-zero network MDR on UPI AutoPay lines and any per-debit rejection charge not classifiable against an NPCI return reason code.
- **Config:** Per-mandate registry by rail with creation date, status, customer segment, ticket size, and contract reference. Per-rail rate sheet — UPI AutoPay gateway platform fee schedule and eNACH per-debit and per-rejection schedule. NPCI return reason code dictionary for eNACH failure classification. Rail-mix model with expected success rate and rejection rate by segment. Settlement file pipeline split by rail. GST 18 percent overlay on fee components. Variance register feeding the subscription unit economics dashboard.
- **Output:** A monthly subscription rail dashboard showing per-rail debit count, success rate, failed-debit fee burden, platform-fee burden, and GST on each, totalled against the modelled unit economics. A per-rail leakage report flagging non-zero network MDR on UPI AutoPay lines and unclassified rejection charges on eNACH lines. A quarterly rail-mix recommendation brief setting target migration from eNACH to UPI AutoPay for ticket bands under ₹15,000 with quantified annual savings, supported by the reconciliation evidence base.

### UPI Bank-Account MDR by Ticket Size: Below ₹2,000 vs Above ₹2,000 Economics

Source: https://www.terra-insight.com/insights/upi-bank-account-mdr-by-ticket-size-india/

- **Problem:** Indian finance teams treat the gateway's parent UPI line as a single zero-MDR rail and so do not bucket UPI volume by ticket size or by instrument sub-type. The result is that PPI-on-UPI interchange (0.5%-1.1% above ₹2,000) and RuPay-credit-on-UPI interchange (~2% above ₹2,000) accumulate inside the same UPI line as legitimately-free bank-account UPI, and any erroneous positive MDR on bank-account UPI itself goes undetected because nobody has separated the three children of the parent rail.
- **Logic:** Reconciliation splits the UPI parent line into three children — bank-account UPI, PPI / wallet-on-UPI, and RuPay credit-on-UPI — using the payment-instrument sub-type field exposed in the gateway settlement payload, then buckets each child by ticket band (at or below ₹2,000 versus above ₹2,000). The expected-rate table is keyed on child rail and ticket band: zero for bank-account UPI in every band, NIL for PPI and RuPay credit at or below ₹2,000, 0.5%-1.1% PPI and ~2% RuPay credit above ₹2,000. Each transaction's actual deduction is compared to the expected and variances flagged.
- **Config:** Rail-split rule on the UPI parent method using the instrument sub-type field; ticket-band bucket rule with the ₹2,000 boundary; expected-rate table keyed on rail + merchant category code + ticket band; UPI_BANK_ACCOUNT_POSITIVE_MDR variance class with zero tolerance (any positive MDR is a flag); UPI_SUBRAIL_BELOW_THRESHOLD variance class for PPI or RuPay-credit charges at or below ₹2,000; refund-interchange-retention flag; monthly GST-invoice matcher to GSTR-2B for the 18% ITC line.
- **Output:** A per-transaction UPI rail-mix and ticket-band variance report with recoverable over-charges, a CFO-facing dashboard showing UPI parent volume split into three children by month, a refund-interchange-retention exception list for gateway support tickets, and an Input Tax Credit claim schedule for the 18% GST on legitimate sub-rail interchange.

### UPI MDR (Bank Account): What You Actually Pay vs What Gateways Charge

Source: https://www.terra-insight.com/insights/upi-mdr-bank-account-vs-gateway-platform-fee-india/

- **Problem:** Finance controllers conflate two distinct charges on UPI bank-account transactions: the network MDR (zero by statute under Section 10A of the Payment & Settlement Systems Act and Section 269SU of the Income-tax Act) and the gateway platform fee (a legitimate, contractually positive charge for aggregator services). When settlement files label both as 'MDR' or when the platform fee is billed at a card-grade flat percentage rather than the contracted enterprise UPI rate, the result is structural fee leakage on the largest method-mix cell.
- **Logic:** Decompose every settlement transaction into four reconciliation lines — gross sale, network MDR (zero on bank-account UPI), platform fee at the contracted enterprise rate per network, and 18% GST on the fee only. Flag any non-zero network-MDR component on bank-account UPI cells as Pattern #1. Reconcile the platform-fee effective rate (fee divided by network volume) to the contracted rate per network rather than to the headline blended rate. Keep TDS under Section 393(1) code 1035 at 0.1% as a separate line where applicable.
- **Config:** Per-gateway, per-network rate table with zero-MDR enforcement on bank-account UPI and RuPay debit cells; contracted enterprise rate per network captured separately from published-rate reference; instrument classifier that splits UPI into bank-account, RuPay-credit-on-UPI, and PPI-on-UPI; GST isolator at 18% on the fee line only; TDS reconciliation hook to Form 26AS for code 1035 deductions by third-party e-commerce operators.
- **Output:** Per-network effective-rate report (deducted fee divided by network volume) reconciled to contracted rate; transaction-level exception list flagging any non-zero network-MDR component on bank-account UPI; quantified monthly and annualised leakage by network; gateway dispute pack with the regulatory citations and the line-by-line classification that the gateway account manager can sign off without escalation.

### UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books

Source: https://www.terra-insight.com/insights/upi-settlement-reconciliation/

- **Problem:** UPI P2M settles at T+0 with a 12-digit NPCI Reference ID (not a bank UTR), producing thousands of individual bank credit lines per month. Direct UPI flows require per-credit matching at gross equals net (0% MDR under ₹2,000), while aggregator UPI flows require two-step matching of batch credit then order-level split.
- **Logic:** Primary match key is the 12-digit UPI Reference ID parsed from bank narration (pattern UPI/P2M/[12 digits]/[VPA]). Direct UPI matches each bank line to an order via UPI Ref ID plus amount plus date. Aggregator UPI first matches the batched settlement credit to the aggregator report, then resolves inner orders by UPI Reference ID while deducting MDR above ₹2,000 where applicable.
- **Config:** Narration parser for UPI/P2M pattern, dual-mode router (direct versus aggregator), MDR threshold rule at ₹2,000, and high-volume batch processing for thousands of daily credits.
- **Output:** Order-level reconciled revenue per UPI transaction, aggregator-settlement to order-level breakdown, MDR ITC claim where applicable, and exception ledger for mismatched UPI Reference IDs.

### UPI Zero-MDR Regime in India: Section 269SU, PSS Act §10A, and What It Means for Merchant Fee Reconciliation

Source: https://www.terra-insight.com/insights/upi-zero-mdr-regime-section-269su-pss-act-india/

- **Problem:** UPI bank-account P2M and RuPay debit P2M are zero network MDR by statute, but the gateway platform fee is not — and many settlement files merge bank-account UPI, RuPay-credit-on-UPI and PPI-on-UPI into a single 'UPI' line, masking the cells that genuinely carry merchant cost. Without separation, a finance team cannot distinguish the regulated component (which must be zero) from the contracted platform fee (which has its own rate-card error mode) from RuPay-credit-on-UPI interchange (around 2% above ₹2,000) from PPI-on-UPI interchange (0.5% to 1.1% above ₹2,000).
- **Logic:** Reconciliation splits the 'UPI' aggregate into instrument sub-types using rail flags from the settlement file (bank account vs. RuPay credit vs. PPI), then applies the rule: network MDR must equal zero for bank-account UPI and RuPay debit P2M; platform fee must equal the contracted rate (not the published rate); GST line must equal 18% of platform fee only. Any non-zero network MDR on a zero-MDR instrument, or any platform-fee variance outside tolerance against the contracted rate card, is raised as an exception.
- **Config:** Rate-card engine keyed on instrument plus rail sub-type, zero-MDR rule flag for bank-account UPI and RuPay debit, platform-fee tolerance threshold against contracted rate, GST cross-check at 18 percent of fee only, and refund-platform-fee retention flag.
- **Output:** Per-transaction split of UPI settlement into bank-account UPI, RuPay-credit-on-UPI and PPI-on-UPI; exception list of any non-zero network MDR on zero-MDR instruments; platform-fee variance recoverable against gateway; GST reconciled against GSTR-2B for ITC; refund-platform-fee leakage schedule.

### USFDA Form 483: Remediation Cost Accounting Under Section 37

Source: https://www.terra-insight.com/insights/usfda-form-483-remediation-cost-accounting-treatment-guide/

- **Problem:** An Indian listed pharma group receiving a USFDA Form 483 with a dozen observations across data integrity, sterility assurance, and CAPA closure faces a multi-year remediation programme that hits three simultaneous reconciliation surfaces. Section 37 revex deductibility per invoice must survive the wholly-and-exclusively test and the Explanation 1 offence-and-prohibited-by-law bar. Ind AS 16 capex vs revex classification per invoice must satisfy the future-economic-benefit and directly-attributable-cost criteria for capitalised equipment. Ind AS 37 provision recognition must move from a contingent liability at 483 issue to a recognised provision at response letter or warning letter, with a costed schedule over the programme window. Section 195 foreign remittance TDS on US-based CGMP consulting firms must apply the India-US DTAA rate after the make-available test, with a Tax Residency Certificate, Form 10F, and Form 15CA/15CB filed before every remittance. Section 194J code 1005 TDS on Indian sub-contractors must apply at 10 percent above the Rs 30,000 threshold. A typical 3-year Rs 200 crore programme generates 800 to 1,200 line items across 40 to 60 vendors, and manual reconciliation loses track of the capex/revex split, over-provisions or under-provisions the Ind AS 37 movement, and drops Section 195 challan matches against the Form 15CB certificate chain.
- **Logic:** Build a 483-observation register keyed to each of the 12 observations, split into sub-remediation-work-orders with a costed plan per work order. Map every vendor invoice to a work order and to a GL account that carries the capex or revex tag at source; apply the Ind AS 16 recognition criteria (probable economic benefit + reliable measurement + directly attributable cost) as the automated classification rule, with a manual override register for edge-case items. Compute the Section 37 wholly-and-exclusively test evidence per invoice — narrative link to observation, work-order reference, business-restoration argument — and store as an evidence pack for the tax audit. Recognise the Ind AS 37 provision at the earlier of (a) the internal costed remediation plan approval or (b) the FDA warning letter, and run a monthly provision movement schedule (opening balance + additions from new scope + utilisation from actual spend + remeasurement gain or loss = closing balance). Feed the Section 195 remittance register with each offshore consultant invoice, the DTAA rate applied (India-US Article 12 for US consultants, India-Germany for EU consultants, India-Singapore for SG consultants), the TRC/Form 10F held on file, and the Form 15CA/15CB pair filed before the remittance date. Feed the Section 194J code 1005 register with each Indian sub-contractor invoice above the Rs 30,000 annual threshold and remit TDS to TRACES against the payee PAN. Cross-check the aggregate Section 37 claim in the tax return against the Ind AS 16 asset addition and the Ind AS 37 provision utilisation to close the three-way reconciliation.
- **Config:** Consultant master with vendor code, PAN or overseas tax identifier, residency, DTAA-eligible tax residency certificate expiry date, Form 10F expiry date, service category (CGMP consulting, validation, calibration, training), and payment terms; 483-observation register with observation code, USFDA classification (data integrity/sterility/CAPA/stability/laboratory controls), assigned remediation work-order, budgeted cost, and target closure date; work-order register with work-order code, linked observation, remediation activity (consulting/equipment/method revalidation/training), capex or revex tag, budgeted cost, and actual cost; Ind AS 16 asset register with asset class (analytical equipment, HVAC, isolator, environmental monitoring), useful life, depreciation schedule, and directly-attributable capitalised cost; Ind AS 37 provision register with recognition date trigger (response letter approval, warning letter, consent decree), best-estimate cost schedule by year, and remeasurement history; Section 195 remittance workbook with invoice, DTAA rate, TRC/Form 10F on file, Form 15CA/15CB filing reference, and challan; Section 194J code 1005 workbook with invoice, payee PAN, threshold check, and TRACES challan; Section 43B(h) MSME flag on Indian sub-contractors under the 45-day payment rule.
- **Output:** A month-end USFDA remediation reconciliation pack that closes the three surfaces in one view. Observation-wise remediation progress with budgeted vs actual spend by work order and target closure date on track or slipped. Ind AS 16 capex ledger with per-asset addition, IQ/OQ/PQ status, and depreciation schedule. Ind AS 37 provision movement with opening balance, additions from new scope, utilisation from actual spend, remeasurement, and closing balance. Section 37 revex claim with per-invoice wholly-and-exclusively test evidence pack. Section 195 remittance register with DTAA rate applied per invoice, Form 15CA/15CB filing reference, and challan match. Section 194J code 1005 register with payee-wise TDS and TRACES challan match. Year-end tax audit pack cross-linking the three-way reconciliation of Section 37 revex claim + Ind AS 16 capex addition + Ind AS 37 provision utilisation against the ledger control total.

### Building a USFDA Inspection Observation Remediation Tracker

Source: https://www.terra-insight.com/insights/usfda-inspection-observation-remediation-tracker-pharma/

- **Problem:** A Tier 1 Indian pharma sponsor with a USFDA-inspected plant sits with 14 open Form 483 observations from a recent inspection cycle and needs a single observation-level tracker that closes the loop across the corporate quality head (technical closure of each CAPA), the finance controller (per-observation cost tracking and Ind AS 37 provision release), and the statutory auditor (Section 143(3)(i) ICFR testable control on remediation cost approval and provision movement). Each observation carries its own root-cause, corrective action, preventive action, evidence log, target closure date, and cost estimate; the aggregate best-estimate provision at year-end (illustratively Rs 145 crore for a mid-scale formulation plant) is released to P&L proportionally as observations close per the FDA response cycle. Missing any hop breaks the quarterly audit committee review, opens a book-to-tax reconciliation exposure on the Section 37 IT Act 2025 deduction versus the Ind AS 37 provision balance, and risks a Warning Letter escalation if the FDA determines the response is inadequate.
- **Logic:** Ingest the Form 483 observation set at inspection close-out and open one tracker row per observation with the CFR sub-part cited, the root-cause draft, the corrective action plan, the preventive action plan, the evidence-collection log, the target closure date, and a first-pass cost estimate across labor, equipment, validation, and training. Route each cost estimate through a two-signature approval workflow (plant quality head + corporate finance controller) before it enters the Ind AS 37 provision aggregate. Book the aggregate provision at year-end at best-estimate using the observation-level cost register, with a low-estimate and high-estimate range documented in the accounting policy note. As each observation closes per FDA response cycle sign-off, release the corresponding portion of the provision against actual CAPA spend, re-estimate the remaining open observations at each quarter-end, and true-up the provision. Feed the Section 37 IT Act 2025 deduction on actual payment through the tax provisioning ledger with a deferred tax asset on the un-paid provision balance. Ind AS 16 equipment capex is separately routed to property, plant and equipment and depreciated over useful life — only the non-capitalisable installation, validation, and training labor lands in the provision.
- **Config:** Observation-level master with the FDA inspection reference number, observation sequence (Observation 1 through Observation N), CFR sub-part citation (21 CFR 211.22, 21 CFR 211.42, 21 CFR 211.100, 21 CFR 211.160, 21 CFR 211.192, etc.), root-cause classification (documentation gap, equipment failure, procedural non-compliance, data integrity, cross-contamination risk, environmental control breach), corrective action plan, preventive action plan, evidence-collection log, target closure date, revised closure date on any FDA cycle response, actual closure date, per-observation cost estimate broken across labor (internal quality hours, consulting hours, engineering hours), equipment (non-capitalisable installation and validation labor, with a cross-reference to the Ind AS 16 capex line for the equipment purchase itself), validation (IQ / OQ / PQ hours plus method validation runs), and training (SOP rollout, retraining hours, external course fees); two-signature approval workflow (plant quality head + corporate finance controller); Ind AS 37 provision aggregate calculation with low / best / high estimate range; provision movement schedule with opening balance, additions in the year (new observations), utilisation (releases against actual spend on closed observations), re-estimation (change in best estimate on open observations at quarter-end), and closing balance; Section 37 IT Act 2025 deduction schedule with book-to-tax timing bridge and deferred tax asset roll-forward; Section 195 TDS withholding schedule for consulting fees paid to US or foreign firms; Section 143(3)(i) ICFR control matrix with the observation-intake / cost-estimation / closure-evidence / provision-release control tests documented for statutory auditor review; audit committee quarterly review pack template.
- **Output:** A quarterly observation-level closure register showing every open Form 483 observation with its CAPA status (open / in-progress / evidence-review / closed), the FDA response cycle position (initial response filed, FDA acknowledgement pending, FDA acknowledgement received, further evidence requested, closed), the per-observation actual spend to date versus the approved cost estimate, and the target versus revised closure date variance. The Ind AS 37 provision movement schedule with opening balance, additions, utilisation, re-estimation, and closing balance reconciled to the trial-balance provision GL. The Section 37 IT Act 2025 deduction schedule showing actual payment in the year (deductible), provision movement (book expense not yet deductible), and the deferred tax asset roll-forward. The Ind AS 16 property, plant and equipment addition schedule for equipment purchased as part of remediation, with the depreciation charge for the year. The Section 195 TDS withholding certificate schedule for US consulting firm fees. The Section 143(3)(i) ICFR control-test evidence pack for the statutory auditor including the two-signature cost approvals, closure sign-off records, and provision-release entries. The audit committee quarterly review pack: technical closure dashboard (corporate quality head narrative), financial closure dashboard (CFO narrative), provision movement waterfall, upcoming FDA response deadlines calendar, and any escalation exposure to Warning Letter or Import Alert.

### USFDA Warning Letters: Ind AS 37 Provisions and Contingent Liabilities

Source: https://www.terra-insight.com/insights/usfda-warning-letter-remediation-provision-ind-as-37/

- **Problem:** An Indian Tier-1 pharma formulator with a US-market export footprint of the order of USD 200 million annually per major USFDA-inspected plant receives a USFDA warning letter at one of its plants with eight observations spanning data-integrity, aseptic-processing, cleaning-validation and cross-contamination-control. The finance team must recognise, measure, disclose and reconcile the Ind AS 37 provision for USFDA warning letter remediation at the reporting date — applying the three-limb recognition test at paragraph 14, establishing the constructive obligation under paragraph 20, measuring the best estimate under paragraph 36, discounting under paragraph 45 if the effect is material, disclosing the movement schedule under paragraph 84, splitting the total-remediation-cost scope between the revex leg (which feeds the provision) and the capex leg (which is capitalised under Ind AS 16), and reconciling the book-tax gap against the Section 37 IT Act payment-basis deduction through the Ind AS 12 deferred-tax working. The illustrative provision quantum at initial recognition sits in the Rs 180 to 240 crore range depending on scope complexity and benchmarking anchor, with the movement schedule tracking drawdown over the 18 to 30 month remediation cycle.
- **Logic:** At each reporting date the finance team runs a five-step recognition-and-measurement sequence per Ind AS 37. Step one, apply paragraph 14 — check that a present obligation exists as a result of a past event (the warning-letter issuance is the past event; the constructive obligation under paragraph 20 is established by the formulator's pattern of past remediation practice, published CGMP commitments and management's specific remediation statement post-receipt). Step two, check probable outflow (management's commitment to protect US-market revenue at risk makes the outflow probable). Step three, build the reliable-estimate scope through initial engineering-and-consulting scoping plus benchmarking against the entity's own prior remediation history at other plants or against defensible peer benchmarks; produce the best-estimate figure under paragraph 36. Step four, split the total scope between the revex leg (feeds the provision) and the capex leg (capitalised under Ind AS 16 and depreciated). Step five, discount the revex leg to present value under paragraph 45 if the effect is material; recognise the discounted provision on the balance sheet; disclose the class-level movement schedule under paragraph 84 in Note X. Compute the Section 37 deduction on payment basis for each period's actual remediation drawdown, and reconcile the book-tax gap through the Ind AS 12 deferred-tax asset working.
- **Config:** Plant master with USFDA-inspection status and stage (Form 483, Warning Letter, Consent Decree, Import Alert) per plant per date; observation register keyed to plant, inspection date, observation number, systemic-versus-isolated classification, and management remediation status; scoping-and-benchmarking workbook holding the initial engineering-scope estimate, external-consultant scoping quotations, peer-benchmark reference cases from prior remediation cycles (Halol, Baddi, Ahmedabad, Bachupally in earlier windows), and the derived best-estimate range under paragraph 36; revex-versus-capex split rules with a taxonomy of remediation cost categories (consultants, external laboratory audits, batch-record reconstruction, deferred-batch write-off on the revex side; HVAC upgrades, sterile-fill line replacements, laboratory equipment additions on the capex side); Ind AS 45 discount-rate register per reporting-date (typically the risk-free rate for the remediation cycle horizon); Ind AS 37 movement-schedule template per class of provision; remediation cost drawdown register mapping actual invoices to provision-class buckets; Section 37 payment-basis deduction schedule; Ind AS 12 deferred-tax working; and disclosure Note X drafting template.
- **Output:** A reporting-date USFDA remediation provision pack per affected plant: the three-limb recognition test working with the constructive-obligation memo under paragraph 20, the best-estimate scoping-and-benchmarking file supporting the paragraph 36 measurement, the revex-versus-capex split working, the paragraph 45 discount-rate application, the recognised provision balance for the balance sheet, the movement-schedule table under paragraph 84 for Note X to accounts, the remediation cost drawdown register cross-cast against the movement schedule (opening plus additions minus used minus reversed plus unwind equals closing), the Section 37 payment-basis deduction schedule for the tax computation, the Ind AS 12 deferred-tax asset working, and the audit-trail file mapping every input document (warning letter, observation register, scoping quotations, peer-benchmark references, external-consultant deliverables) to the movement-schedule line item it supports. At year-end the pack rolls into the group audit file and into the Note X disclosure in the annual report.

### VMI (Vendor Managed Inventory) at Tier-2 Garment Supplier Reconciliation

Source: https://www.terra-insight.com/insights/vendor-managed-inventory-vmi-tier2-garment-supplier-reconciliation/

- **Problem:** Indian apparel brands running VMI arrangements with Tier-2 garment suppliers hold four parallel registers that must reconcile at every month-end: the supplier's warehouse stock register, the brand's SKU-level consumption calls, the monthly VMI settlement invoice, and the GSTR-2B credit visible on the brand's GST portal. Placement value under the master agreement is typically several crore; consumption runs 60 to 80 percent of placement across a season; the residual closing stock sits at the supplier warehouse under bailment. Any drift between the four registers — misread consumption calls, timing lags in the settlement invoice, GST rate reclassifications post 22 September 2025, or ambiguous ownership-transfer clauses — surfaces as either an over-declared ITC claim, an under-declared output GST liability, or a stuck payable that the auditor flags at year-end.
- **Logic:** Build a monthly VMI reconciliation pack keyed to the placement lot (Rule 55 delivery-challan number). Match the supplier's warehouse stock register to the brand's consumption call schedule at SKU level. For each consumption call, verify the monthly settlement invoice value against the rate contract in the master agreement and the applicable GST rate at the time of supply (i.e., the invoice-issue date, not the placement date). Cross-foot the settlement invoice to the GSTR-2B credit at the supplier's GSTIN. Age the residual closing stock against the master agreement's return window and Section 143 job-work protection clock if the arrangement is job-work-flavoured. For every consumption invoice cycle, deduct Section 393(1) Sl. 8 TDS at 0.1% on the invoice value net of GST once the seller-level threshold is crossed.
- **Config:** Master VMI agreement with rate contract per SKU, ownership-transfer clause, and return-window definition; supplier warehouse master keyed to the supplier's principal-place-of-business GSTIN or a registered additional-place-of-business GSTIN; SKU master with HSN and applicable GST rate (pre and post 22-September 2025 rate reclassifications); placement delivery challan register with Form GST INS-01 numbers and dispatch dates; monthly consumption call schedule from the brand's retail replenishment engine; monthly settlement invoice register with invoice date, taxable value, GST rate, and IRN; GSTR-2B extract at supplier GSTIN level; Section 393(1) Sl. 8 deductee register with cumulative FY value tracking; Section 143 return-clock timer where the VMI is job-work-structured.
- **Output:** A month-end VMI reconciliation pack: opening supplier-warehouse stock balance, period placement, period consumption invoiced, period consumption cash-settled, closing supplier-warehouse stock — reconciled to the supplier's stock register. A per-invoice GSTR-2B match with variance flags on rate, HSN, or IRN mismatch. A Section 393(1) Sl. 8 TDS deduction log with cumulative FY threshold status per supplier PAN. A return-window ageing report on residual closing stock feeding the master agreement's return-leg trigger. A Section 143 clock report for job-work-structured arrangements, flagging placement lots approaching the 1-year deemed-supply threshold with 60 days of runway.

### Venky's Hatchery Broiler Breeding Reconciliation India

Source: https://www.terra-insight.com/insights/venkys-hatchery-broiler-breeding-reconciliation-india/

- **Problem:** A pan-India broiler hatchery group at Venky's operating scale — twelve hatcheries producing an aggregate 2.5 to 3 million day-old-chicks per week across grades (Cobb, Ross, Vencobb) at illustrative Rs 26 to 32 per DOC — must simultaneously reconcile the three-tier GP to PS to DOC breeder chain, the dispatch invoice register split between contract-integrators (B2B bulk contract) and independent farmers (B2C spot), the Section 194Q code 1031 TDS deduction by integrator-buyers above the Rs 50 lakh single-supplier threshold, the Rule 89(5) inverted-duty refund cycle driven by 5 percent DOC output against 12 percent vaccine and medicine and 18 percent packaging input, and the tier-wise feed cost allocation from GP through PS to DOC. Manual reconciliation across twelve state-level GSTINs, per-integrator running-turnover triggers, per-tier production logs, and per-site RFD-01 filings loses the Section 194Q threshold crossings, over-includes input services in Net ITC, and misses inter-branch supply invoices — exposing the group to Section 73/74 GST notices at year-end, Form 26AS Form 26Q mismatches at every integrator, and 43B(h) MSME disallowance on delayed vendor payment.
- **Logic:** Build a hatchery production log ingest keyed on site code, date, hatch batch number, eggs set, eggs candled, chicks hatched, culls, saleable DOC by grade (Cobb, Ross, Vencobb) and export the batch-to-invoice traceability spine. Ingest the DOC dispatch invoice register by GSTIN by buyer type (B2B integrator with supply-contract reference / B2C independent farmer with PAN or GSTIN), reconcile invoice line grade and quantity against the source hatch batch, and expose grade-wise price variance against the buyer-type contract or the daily spot-price index. Maintain a per-integrator running-turnover ledger, trigger the Section 194Q code 1031 tag on the first invoice that crosses the Rs 50 lakh single-supplier threshold in a financial year, and reconcile the integrator-side TDS credit against Form 26AS at the hatchery PAN. Extract packaging input GST at 18 percent, medicine and vaccine input GST at 12 percent, and feed input GST at 5 percent from GSTR-1 and GSTR-3B into the Rule 89(5) refund workbook per state GSTIN, apply the amended Notification 14/2022 formula with input services and capital goods excluded from Net ITC, and generate a per-GSTIN GST RFD-01 monthly or quarterly. Allocate GP breeder-tier feed cost to PS chick output and PS breeder-tier feed cost to DOC output using standard-cost allocation with year-end true-up against actuals. Watch inter-hatchery DOC transfers between state GSTINs and raise the intra-group tax invoice at 5 percent under Schedule I to close the multi-GSTIN cross-charge exposure.
- **Config:** Hatchery site master with site code, GSTIN, state, incubator and hatcher installed capacity, breed authorisation (Cobb, Ross, Vencobb), and cold-chain vaccine store capacity; DOC grade master with grade code, breed line, weight band, and quality-guarantee flag; buyer master split into contract-integrator (agreement reference, monthly indicative volume, grade-wise price, credit-period days) and independent-farmer (GSTIN if registered, PAN, composition-scheme flag, payment mode); integrator running-turnover ledger with Rs 50 lakh Section 194Q threshold flag and 194Q code 1031 tag; feed supplier and vaccine supplier master with Section 43B(h) MSME flag on Micro and Small Enterprise vendors; corrugated packaging converter master with HSN 4819 mapping; polymer chick tray converter master with HSN 3923 mapping; three-tier breeder-flock production log (GP hens per site, PS hens per site, hatchability percentage, chick quality index); Rule 89(5) refund workbook per GSTIN with Notification 14/2022 amended Net ITC formula; inter-state DOC transfer register with intra-group tax invoice at 5 percent under Schedule I; DGFT breeding-stock import licence log for GP tier imports (Cobb-Vantress, Aviagen, Vencobb primary-breeder shipments).
- **Output:** A month-end pan-India hatchery reconciliation pack: three-tier breeder production log with GP-to-PS-to-DOC yield percentage by site, DOC dispatch invoice register reconciled against hatch batch source with grade-wise price variance flagged, per-integrator running-turnover ledger with Section 194Q code 1031 trigger dates and Form 26AS reconciliation status per hatchery PAN, per-GSTIN Rule 89(5) refund draft with the Notification 14/2022 amended formula and packaging and medicine and vaccine input invoice register mapped by tax period, PS-to-DOC and GP-to-PS feed cost allocation with year-end true-up variance, inter-hatchery transfer register with 5 percent intra-group tax invoices raised under Schedule I, and MSME 43B(h) status report on feed and vaccine and packaging vendor payables. Per-site yield trend supports the operating dashboard for the hatchery COO; the RFD-01 pack and 194Q reconciliation drives the group CFO's monthly working-capital cycle.

### Virtual Account Reconciliation in India: How Auto-Matching Works

Source: https://www.terra-insight.com/insights/virtual-account-reconciliation-india/

- **Problem:** NEFT and RTGS credits without a structured reference (generic narrations like 'EMI' or payer name) force manual narration parsing and cause 40% or more unmatched credits at scale. NBFCs processing 10,000+ collections per month cannot sustain manual narration matching.
- **Logic:** Issue each customer a unique Virtual Account Number so incoming credits self-identify via the bank's webhook. Match on VAN plus amount; when amount does not match an open invoice, classify as overpayment, underpayment, or TDS-net payment and route accordingly.
- **Config:** Bank-issued or gateway-issued VAN per customer, webhook ingestion with retry, AR master linkage by VAN, and TDS-net detection using each deductor's known section and rate.
- **Output:** Near-100% auto-match on incoming customer payments, LMS or AR updated same-day, and a dramatically smaller exception queue limited to genuine amount or payer anomalies.

### Visa/Mastercard Debit MDR: Small vs Large Merchant Caps (RBI 2017 Circular)

Source: https://www.terra-insight.com/insights/visa-mastercard-debit-small-vs-large-merchants-mdr-india/

- **Problem:** RBI/2017-18/105 sets two Visa/Mastercard debit MDR slabs — 0.40%/0.30%/₹200-cap for merchants up to ₹20 lakh turnover, 0.90%/0.80%/₹1,000-cap for everyone above — but acquirer settlements often mis-apply the slab at outlet level, ignore the per-transaction cap on big-ticket transactions, or carry a rate above the regulatory ceiling. The merchant cannot pass the cost to the customer, so every basis point of error is a permanent margin leak.
- **Logic:** For every non-RuPay debit settlement row, classify the channel (POS-and-online vs QR), look up the contracted slab rate for the merchant turnover tier, compute expected MDR as minimum of (rate times transaction value) and the slab cap (₹200 small / ₹1,000 large), then compare to the actual MDR deducted on the settlement file. Any positive variance is a recoverable overcharge. Roll up monthly per MID to produce an effective-rate-by-outlet view that exposes slab-classification drift across outlets.
- **Config:** Merchant turnover tier (small ≤ ₹20 lakh / large above), channel classifier (POS-and-online vs QR-code), contracted rate per slab, per-transaction cap clamp (₹200 / ₹1,000), MID-to-entity map so consolidated turnover drives slab assignment across all outlets, refund-MDR retention tracker since debit MDR is non-refundable industry-wide.
- **Output:** Per-transaction variance report flagging cap breaches and slab misclassifications, per-MID effective debit rate vs contracted rate, recoverable overcharge schedule with settlement IDs for acquirer dispute, and a monthly trend line that catches slab drift before it compounds into a multi-quarter leak.

### Visa/Mastercard Credit Card Consumer MDR: Negotiated 1.4-1.6% vs Published 2%

Source: https://www.terra-insight.com/insights/visa-mastercard-credit-consumer-negotiated-vs-published-mdr-india/

- **Problem:** Indian merchants processing material Visa and Mastercard consumer credit-card volume routinely accept the published gateway rate of around 2 percent as if it were a market rate. It is not. The published rate is the small-merchant rate. Enterprise merchants processing ₹1 crore or more per month on the network in question routinely negotiate 1.4-1.6 percent, but the negotiation requires four concurrent levers and a quantified justification. Without that discipline the merchant overpays roughly 35-60 basis points on every credit-card transaction. At ₹3 crore monthly Visa/Mastercard consumer-credit volume that is ₹1.05-1.80 lakh of margin leakage every month, compounding to ₹12-22 lakh per year, with the leakage invisible because the reconciliation baseline used internally is the published rate, not what a real negotiation would have delivered.
- **Logic:** Pull settlement files at the lowest available BIN-and-network granularity from every payment aggregator. Isolate Visa and Mastercard consumer-credit volume from Amex, Diners, corporate, international and premium-rewards volume, because those sit in the 3 percent slab and do not belong in the same negotiating denominator. Compute the effective rate on the consumer-credit slice as fee divided by gross over a rolling three-month window. Compare to the negotiated-rate band the merchant's monthly volume qualifies for (1.55-1.75 percent at ₹1-5 crore monthly; 1.40-1.55 percent above ₹5 crore monthly). Quantify the gap in monthly rupees and in annualised rupees. Carry GST 18 percent on the MDR and TDS 0.1 percent on gross under Section 393(1) Sl. 8(v) code 1035 as separate columns, never folded into the MDR percentage.
- **Config:** Per-gateway and per-network rate card with explicit separation of Visa/Mastercard consumer-credit from Amex, Diners, corporate, international, premium-rewards, EMI and prepaid. Negotiated-rate band table parametrised by monthly volume tier (below ₹1 crore, ₹1-5 crore, above ₹5 crore). Method-mix floor enforcement on the consumer-credit slice. Effective-rate variance threshold at 10 basis points above the contracted rate triggering an investigation. GST-on-MDR retention flag enforcing 18 percent on fee only, never on transaction value. TDS-by-operator flag enforcing 0.1 percent under Section 393(1) Sl. 8(v) code 1035 reconciling to Form 26AS.
- **Output:** A monthly per-network effective-rate report on the Visa/Mastercard consumer-credit slice, comparing actual to contracted to negotiated-band expectations, with monthly and annualised variance in rupees. A drill-down register of every transaction billed above the contracted slab for case management. A renegotiation dossier showing rolling-twelve-month consumer-credit volume, method-mix composition, chargeback ratio and dispute turnaround, ready for the next round of acquirer negotiation. A GST-on-MDR and TDS-by-operator audit trail keeping the input-tax-credit chain intact and the Form 26AS reconciliation clean.

### Wagh Bakri Tea Packet Modern Trade Reconciliation

Source: https://www.terra-insight.com/insights/wagh-bakri-tea-packet-modern-trade-reconciliation/

- **Problem:** A blended packet tea group with 25,000 MT of annual dispatch across modern trade (roughly 15 percent through DMart, Reliance Smart, More Retail, Big Bazaar), a national kirana distributor pyramid (roughly 70 percent), and HORECA institutional buyers (roughly 15 percent) must reconcile four cascading surfaces: garden procurement lot to blender batch, blender batch to packet SKU dispatch, packet dispatch to modern trade GRN or distributor primary sale, and channel-level Section 194H distributor TDS at code 1015, Section 15(2) scheme discount treatment through Section 34 credit notes, and Section 43B(h) MSME 45-day payment aging on small tea garden and packaging vendors. Manual reconciliation across four hops loses batch genealogy, mis-classifies scheme discounts as trade marketing expense when they qualify for Section 15(2) GST value adjustment, under-deducts distributor commission TDS by mis-coding under a non-194H head, and misses the 45-day MSME cut-off on small tea garden suppliers — exposing the group to a Section 74 GST short-payment demand, a Section 201 short-deduction TDS penalty, and a Section 43B(h) disallowance at year-end.
- **Logic:** Build a batch-genealogy ledger that carries garden lot codes into blender batch identifiers and forward into every packet SKU dispatch, so that any downstream retail dispute traces back to the garden lots that fed the batch. Ingest modern trade GRN feeds by chain by warehouse by SKU, three-way match against the dispatch challan and the payment advice, and expose the variance lines by category — short-supply, damage-in-transit, scheme adjustment. Key every distributor commission accrual to Section 18 Sl. 18 code 1015 at 5 percent and generate the monthly Form 26Q filing base per distributor PAN. Ingest the scheme-agreement register with the Section 15(2) eligibility flag per agreement, and split scheme spend between GSTR-1 credit-note adjustments (Section 15(2) eligible) and trade marketing expense (Section 15(2) ineligible or ad-hoc concessions). Flag every MSME-registered vendor on the accounts-payable master, run the 45-day (or 15-day) aging clock from invoice date, and generate the March-quarter payment sweep report for the finance team to close out before year-end.
- **Config:** Garden supplier master with supplier code, GSTIN, PAN, MSME status flag (Micro or Small under MSMED Act 2006), credit period agreed under Section 15 of the MSMED Act, HSN 0902 declaration, and Tea Board estate registration where applicable; blender batch master with batch identifier, blend recipe (Assam CTC percent, Dooars CTC percent, Nilgiris CTC percent, Darjeeling orthodox percent, other), moisture target, colour-cup grade, and expected packet SKU output; packet SKU master with SKU code, MRP tier, pack size, HSN 0902 declaration, Legal Metrology declarations, FSSAI licence trace, and channel eligibility (modern trade, kirana, HORECA); modern trade chain master with chain identifier, warehouse locations, listing agreement version, scheme agreement register with Section 15(2) eligibility flags, and payment cycle; distributor master with distributor code, super-stockist or C&F designation, state or region, PAN, TDS code 1015, and commission percentage schedule; scheme-agreement register versioned by effective date with the Section 15(2) three-condition eligibility check per scheme; accounts-payable ageing configuration keyed on MSME status with 45-day (or 15-day) threshold and March-quarter sweep alerts.
- **Output:** A month-end four-surface packet tea reconciliation pack: batch-genealogy trace from garden lot through blender batch to packet SKU dispatch; modern trade GRN three-way match by chain by warehouse by SKU with variance category breakdown (short-supply, damage-in-transit, scheme adjustment); distributor commission run with Section 18 Sl. 18 code 1015 TDS at 5 percent reconciled against Form 26Q filing per distributor PAN; scheme-agreement register split between Section 15(2)-eligible GSTR-1 credit-note adjustments and trade marketing expense; accounts-payable ageing report keyed on MSME status with 45-day (or 15-day) exposure highlighted for the March-quarter payment sweep; and a channel P&L view splitting the modern trade, kirana distributor pyramid, and HORECA net realisation per SKU per period.

### Walmart Best Price (Cash & Carry) FMCG Settlement

Source: https://www.terra-insight.com/insights/walmart-best-price-fmcg-cash-carry-settlement/

- **Problem:** Walmart Best Price is wholesale cash-and-carry serving registered kirana and HoReCa buyers, not modern trade — but every supply lands as B2B on Walmart India Pvt Ltd's GSTIN at the destination store. FMCG brands therefore reconcile a faster T+3 to T+7 settlement cycle than DMart or Reliance Smart while still carrying the line-by-line GSTR-1 tax-invoice discipline, a Walmart-side ITC chain that breaks on any GSTIN or taxable value mismatch, a hybrid direct-route vs distributor-route invoicing split that drives whether Section 393(1) Sl. 18 TDS applies, and a leaner channel-fee pack than modern trade. The reconciliation surface cannot be collapsed into the modern trade pack or the general trade pyramid pack — it needs its own channel master with route flags, GSTR-1 lock-step validation, and scheme-cost classification under Section 15(2) CGST.
- **Logic:** Build a Walmart Best Price channel master keyed by Walmart India Pvt Ltd parent GSTIN, destination store GSTIN, dispatch route flag (direct vs distributor), agreed scheme-net price per SKU, listing fee schedule, and Section 15(2) scheme treatment per category. Run three feeds in lock-step: brand dispatch invoice register, brand GSTR-1 filing summary, and the Walmart daily settlement file. Match each dispatch invoice to its settlement line by invoice number and destination GSTIN; classify each deduction into listing fee, scheme buy-in, quality return, transit damage, or settlement variance. For distributor-route lines, split scheme cost between brand and distributor and TDS the distributor commission under Section 393(1) Sl. 18 where the threshold is crossed. Reconcile the settlement net to expected net derived from agreed scheme-net price minus contractual deduction codes; route any gap above tolerance to channel-finance follow-up within the T+3 to T+7 cycle.
- **Config:** Channel master with Walmart parent GSTIN, store GSTIN list per state, dispatch route flag, agreed scheme-net price per SKU, listing fee schedule, Section 15(2) treatment per scheme; distributor master with GSTIN, PAN, Section 393(1) Sl. 18 TDS rate and per-deductee threshold tracker; dispatch invoice feed with HSN, taxable value, GST rate, and rate-effective date for the September 2025 straddle; GSTR-1 summary feed; Walmart settlement file feed with deduction code dictionary; credit-note linkage to GSTR-1 cycle; ageing buckets on unsettled invoices (0-7, 8-14, 15-30, 30+ days from invoice raise).
- **Output:** A rolling Walmart Best Price reconciliation pack: dispatched invoices, settled invoices (split by direct route and distributor route), pending settlements within the T+3 to T+7 window, settlement variances (listing fee, scheme buy-in, quality return, transit damage, other), GSTR-1 lock-step status (filed, matched, blocked), distributor commission TDS pool with Section 393(1) Sl. 18 threshold tracker, and Section 15(2) credit-note status per scheme. Variances above tolerance surface for channel-finance follow-up before the next settlement cycle. ITC blockers surface as Walmart-side debit-note risk and feed the credit-note window under Section 34 CGST.

### Warehouse COD and 3PL Settlement Reconciliation for Indian D2C and E-commerce

Source: https://www.terra-insight.com/insights/warehouse-cod-reconciliation-3pl-india/

- **Problem:** Indian D2C brands shipping 5,000 to 100,000 orders a month via 3PL fulfilment face a structurally complex COD reconciliation — T+5 to T+14 remittance cycles per 3PL with RTO hold-back, 15-35% RTO shrinkage by category, pickup-vs-billing weight disputes on volumetric vs actual weight, reverse-logistics GST credit-note matching under Section 34, Section 393(1) Sl. 6(i).D(b) code 1024 TDS on 3PL invoices, and a tariff-slab settlement (weight x zone x service tier) that requires re-validation against the 3PL's MIS.
- **Logic:** Tie each shipment to a unique AWB across the order-to-delivery-to-COD-remittance lifecycle, age remittance per 3PL per delivery date against the expected T+X window, reconcile RTO shipments to inbound warehouse receipts and reverse-leg GST credit notes, dispute pickup-vs-billing weight using volumetric formula re-validation with hub re-weigh evidence, recover ITC on 3PL 18% GST charge under SAC 996819, and tie Section 393(1) Sl. 6(i).D(b) code 1024 TDS deduction on each invoice to Form 26AS at quarter-end.
- **Config:** Shipment master keyed by AWB with order ID, SKU, declared weight, volumetric L*B*H, declared value, COD flag, 3PL code, zone, and forward/RTO tariff at booking, COD remittance expected table per 3PL per delivery date offset, RTO master with reason code, warehouse receipt flag and credit-note status, weight-dispute register with hub re-weigh evidence and 14-day contest window, and Section 393(1) Sl. 6(i).D(b) code 1024 vendor master for each 3PL with rate 2% default.
- **Output:** A daily reconciled view per AWB showing delivery date to COD-collection-status to remittance-expected to remittance-received with ageing exceptions, RTO ageing decomposed by reason code with warehouse-receipt confirmation and reverse-GST credit-note status, weight-dispute ageing by 3PL with hub re-weigh evidence file and 14-day window flag, monthly tariff reconciliation showing booked vs invoiced slab with delta classification, and a monthly Section 393(1) Sl. 6(i).D(b) code 1024 TDS challan tied to each 3PL invoice with 26AS quarterly tie.

### Gold Wastage and Melting Loss Inventory Reconciliation for Jewellers

Source: https://www.terra-insight.com/insights/wastage-loss-gold-jewellery-manufacturing-inventory-reconciliation/

- **Problem:** A jeweller sending gold to a karigar for finished-piece manufacture must reconcile four physical numbers per challan — input weight at 24-carat equivalent, refined weight after melting loss, finished output weight after making wastage, and karigar retention where the labour arrangement includes gold retention. The unexplained gap between input and (output + declared wastage + retention) is either genuine additional loss to be substantiated on a metallurgical or design-category basis, or it is a Section 17(5)(g) or 17(5)(h) exposure where the department will disallow the proportionate ITC on the input gold and levy interest at 24% under Section 50 plus Section 74 penalty. The reconciliation must run per challan, aggregate to the quarterly ITC-04 return, tie to the BIS HUID data for the finished pieces, and cross-reference the karigar TDS working under Section 393(1) Sl. 4 (payment codes 1001 / 1023, legacy 194C).
- **Logic:** Build a per-challan weight reconciliation with four numbers — input, refined, output, retention — captured at each stage on karigar-signed weighing certificates and refining assay certificates. Segment the design catalogue into wastage-tolerance bands (1-2% machine-made, 2-4% standard cast, 4-6% hand-crafted, 6-8% intricate filigree / kundan / meenakari) and attach a band to every challan based on the design of the pieces being manufactured. Flag challans where the observed wastage falls outside the design-band tolerance as exceptions for finance-team sign-off. Aggregate challan-level data to the quarterly ITC-04 filing with a supporting register that segments the loss-or-waste column by design category. Cross-reference finished-piece output with the BIS HUID master to tie each output piece to a manufacturing lot. Where the karigar arrangement includes gold retention as part of labour, value the retention at the daily gold rate and gross it up into the Section 393(1) Sl. 4 TDS deduction base.
- **Config:** Design master with wastage-tolerance band per design SKU (machine-made / standard cast / hand-crafted / intricate); karigar master with PAN, GSTIN, Section 393(1) Sl. 4 rate flag (1001 or 1023), and default labour arrangement (cash-only versus cash-plus-retention); job-work challan register with input weight, target output weight, permitted wastage weight, retention weight, and 24-carat equivalent conversion factor; refining assay master with karigar reference, input weight, output weight, and melting-loss percentage; BIS HUID lot master tying finished piece HUID to job-work challan reference; ITC-04 support register per quarter with design-category segmentation of the loss-or-waste column; karigar TDS working per financial year with cash-labour and retention-valued components separated for the deduction base.
- **Output:** A monthly reconciliation pack: per-challan input-output-wastage-retention reconciliation with variance flag against design-category tolerance band; exception queue of challans outside tolerance for finance sign-off with karigar-signed weight-verification attachment; quarterly ITC-04 filing with supporting design-category-segmented register for the loss-or-waste column; BIS HUID lot-to-challan crosswalk for output verification; Section 17(5) exposure working per quarter aggregating excess wastage across all karigar relationships; Section 393(1) Sl. 4 TDS working per karigar per financial year with cash-labour and retention-valued deduction base segmented at the day's gold rate.

### High-Value Wedding Purchase Reconciliation: Section 269ST Cash Cap and PAN Mandate

Source: https://www.terra-insight.com/insights/wedding-purchase-gst-invoice-vs-cash-jewellery-audit-defensibility-india/

- **Problem:** A high-value wedding jewellery purchase — typically ₹5-30 lakh for a mid-market trousseau, ₹50 lakh and upward for premium — cannot be received in cash under Section 269ST of the Income-tax Act, and every invoice above ₹2 lakh must capture buyer PAN or Form 60 under Rule 114B. Retailers who accept walk-in cash beyond the threshold face Section 271DA penalty equal to the amount received, non-filing of Form 61A SFT attracts Section 271FA penalty, and missing PAN capture surfaces during departmental audit as a systemic control failure. The reconciliation must knit together the customer master (PAN, Form 60, address), the invoice register (per-invoice consideration and tax-rate split), the settlement leg (banking-channel receipt reference — NEFT/RTGS/UPI/card/DD), and the annual SFT filing into a single audit-defensible trail.
- **Logic:** Aggregate all invoices for a single customer against a single occasion (wedding gift list, trousseau order) into a customer-occasion basket, and run three concurrent tests. First, Section 269ST cash-mode test — sum of cash receipts across the basket must stay below ₹2 lakh; any receipt that pushes the aggregate over the threshold must be refused or routed to banking channels. Second, Rule 114B PAN test — every invoice with consideration above ₹2 lakh must have PAN or Form 60 on file at the customer master, keyed to the invoice reference. Third, Rule 114E SFT capture — any cash receipt of ₹2 lakh or above (which should be zero in a compliant setup) is flagged for annual Form 61A reporting. Cross-check the settlement leg against the invoice register — every banking-channel receipt must tie back to an invoice reference, and any orphan receipt (payment without invoice, or invoice without payment) surfaces as an exception. Layer the mixed-rate GST reconciliation (3% gold, 5% making, 0.25% diamond, 18% ancillary) on the invoice level and the SAC 9988 making-charges classification on the karigar-labour side (Section 393(1) Sl. 4 TDS).
- **Config:** Customer master with PAN or Form 60 reference, address proof link, and occasion tag (wedding date, wedding party name); invoice register with per-invoice consideration, tax-rate split (HSN 7113 / 7102 / 7103 / 9988 / 7326), and customer-master link; settlement register with mode (NEFT / RTGS / UPI / IMPS / card / cheque / DD / cash), reference (UTR / RRN / cheque number), amount, date, and invoice link; occasion aggregation layer that rolls invoices by customer and occasion tag for Section 269ST clause (c) aggregation; Section 271DA exception flag on any cash receipt approaching or crossing the ₹2 lakh aggregate; Rule 114B exception flag on any above-threshold invoice missing PAN or Form 60; Form 61A SFT extract runner for annual 31 May filing; karigar labour bill register with Section 393(1) Sl. 4 code (1001 or 1023) TDS tracking.
- **Output:** A monthly reconciliation pack: customer-occasion aggregation with cash-mode test result per basket; Rule 114B PAN capture completeness by invoice count and value; settlement-to-invoice tie-back with orphan receipt and orphan invoice exception lists; mixed-rate GST tax-rate row split feeding GSTR-1 (3% / 5% / 0.25% / 18%); karigar labour TDS reconciliation at Section 393(1) Sl. 4 rate against Form 26AS; per-invoice audit trail linking customer PAN, invoice reference, tax-rate split, settlement reference, and occasion tag; annual Form 61A SFT extract with cash-receipt lines (target zero in a compliant setup) and buyer identity fields. Retailers running the reconciliation see clean audit walkthroughs during departmental inspections and defensible walkthroughs during statutory audit.

### Weekend and Holiday Settlement Stretch: 4-Day Cycle Reconciliation

Source: https://www.terra-insight.com/insights/weekend-holiday-settlement-stretch-streaming-payment-gateway-india/

- **Problem:** Payment gateway settlement cycles in India count bank working days, not calendar days. A long weekend, Republic Day, or RBI clearing house holiday stretches T+2 into T+4 or T+5 calendar days, and streaming platforms with continuous capture see multi-day gaps in their settlement file that a naive reconciliation flags as failed. Missing this creates false failure alerts, distorts daily gross booked revenue, and blocks month-end close.
- **Logic:** Weekend-holiday reconciliation overlays the RBI clearing house holiday calendar and the acquirer bank's working-day definition on the expected-settlement-cycle table. For every capture date, the system computes the expected settlement arrival date by adding T+1 or T+2 working days, skipping Sundays, second and fourth Saturdays, national holidays, and gazetted state holidays that fall in the escrow bank's operating jurisdiction.
- **Config:** Expected-settlement-cycle table by gateway and payment method, RBI clearing house holiday calendar loader (annual), acquirer-bank working-day pattern, and settlement-arrival trigger with configurable buffer. Missing-settlement alerts fire only after the recomputed expected date plus buffer has elapsed.
- **Output:** Holiday-aware expected settlement register that distinguishes stretched-cycle transactions from genuine settlement failures, a settlement-arrival trigger that reports on time versus delayed with the correct working-day baseline, and an audit log of every stretched cycle for finance-team review.

### Waterbase and Nekkanti Shrimp Feed + Export Integrated Reconciliation

Source: https://www.terra-insight.com/insights/waterbase-nekkanti-shrimp-feed-export-integrated-reconciliation/

- **Problem:** An integrated shrimp feed and export operator producing about 120,000 MT of feed per year — 60 percent (72,000 MT) sold to third-party farmers on credit and 40 percent (48,000 MT) retained for captive shrimp culture whose harvest blends with third-party procurement into an annual export bucket of about 35,000 MT to the EU, US, and Japan — has to close a reconciliation loop across at least six distinct registers: feed production and dispatch, farmer credit ledger, captive-pond harvest, processing-plant batch test, per-container EIC Health Certificate, and shipping-bill file with e-BRC realisation. A single EU consignment failing the RASFF antibiotic-residue tolerance (chloramphenicol reference around 0.3 ppb; nitrofuran metabolites reference around 1 ppb) triggers a re-import shipping bill, a public RASFF listing that persists in the EU database, and a Section 54(3) refund line that becomes disputed at the proper officer's scrutiny. On the tax side, the feed-to-processing inter-segment transfer between the group's two separate legal entities is a Section 92 associated-enterprises transaction that must be documented at arm's length under the Comparable Uncontrolled Price (CUP) benchmark of the third-party feed price grid.
- **Logic:** Anchor every export container back through the reconciliation chain: EIC Health Certificate to processing-plant batch test to captive-pond harvest or third-party purchase register to feed batch consumed in grow-out to feed production and dispatch record. Split the feed dispatch register into a third-party farmer credit book (dispatch note keyed to MPEDA farmer registration, priced at the standard grid, credit-period aligned to grow-out) and an inter-segment transfer book (dispatch note keyed to group farm cluster and pond number, priced at CUP arm's length, feeding the processing entity's cost of production). Reconcile the shipping-bill file for each tax period against the GSTR-1 export invoice register and the ITC ledger for feed, packaging, cold-chain, power, and water treatment; run the Rule 89(4) formula (Turnover of zero-rated supply × Net ITC / Adjusted Total Turnover) to compute the refundable amount and file Form GST RFD-01 with the shipping-bill file, e-BRC evidence, and ITC extract. Maintain a per-container Health Certificate audit trail — border-rejection scenario walkthrough — so that a RASFF alert can be root-caused within the withdrawal window without cascading to unrelated shipments. Maintain the Section 92 TP documentation set (Form 3CEB, Master File where applicable, Local File) with the CUP benchmark and the variance band that absorbs natural market movement.
- **Config:** Feed master with feed code, formulation, medicated-feed flag with withdrawal-period rule, standard third-party price grid versioned by effective date, MSME flag on ingredient suppliers for Section 43B(h) discipline; farmer master with MPEDA registration number, pond location, grow-out cycle, feed credit ledger with buy-back linkage; captive-pond master with farm cluster, pond number, feed batch consumption, harvest tally; inter-segment transfer register keyed to the Section 92 associated-enterprises identifier, CUP third-party price snapshot per transfer date, variance-band tolerance (typically 3 percent); processing-plant batch register with pre-harvest and post-harvest lab tests for chloramphenicol, nitrofuran metabolites, tetracyclines, and heavy metals; EIC Health Certificate register keyed to container number, FOB value, destination market, and panel result; shipping-bill file feed with GSTR-1 export invoice cross-reference; e-BRC realisation feed from AD bank with fx-variance reconciliation to invoice date rate; Rule 89(4) refund workbook with Net ITC classification by input category; Section 92 TP documentation register with Form 3CEB filing calendar.
- **Output:** A monthly integrated shrimp reconciliation pack: feed production tally split into third-party dispatch (with farmer credit ledger position and buy-back schedule) and captive transfer (with inter-segment CUP variance band); captive-pond harvest tally cross-referenced to feed consumption FCR; processing-plant batch test log with any excursions flagged for withdrawal-period review; per-container EIC Health Certificate register reconciled against the shipping-bill file; a Section 54(3) refund draft under Rule 89(4) with the ITC ledger extract, the FOB export turnover, and the RFD-01 filing base ready for the proper officer; an inter-segment TP register with the third-party CUP grid, the transfer-price variance, and the Form 3CEB attachment schedule; and — for the year-end trigger — a Section 43B(h) MSME payable ageing on the feed ingredient supplier book. A RASFF-alert walkthrough register maintains the container-to-pond-to-feed traceability so a border rejection is root-caused and quarantined before it cascades to unrelated shipments.

### What Is Bank Reconciliation? Definition and Process for Indian Finance Teams

Source: https://www.terra-insight.com/insights/what-is-bank-reconciliation/

- **Problem:** Cash book balance and bank statement balance diverge at period end due to outstanding cheques, deposits in transit, bank charges, and timing differences.
- **Logic:** Match each cash book entry to a bank statement entry using UTR, amount, date, and narration tokens. Unmatched entries are classified as outstanding, error, or UNEXPLAINED.
- **Config:** Tolerance band ≤ ₹1, UTR as primary key, date window ±3 business days, narration substring matching enabled.
- **Output:** Reconciled BRS showing matched pairs, outstanding entries with age, and classified variances ready for auditor sign-off.

### Bank Statement Analysis India: What Lenders and NBFCs Actually Check

Source: https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india/

- **Problem:** Manual income verification from bank statements takes 2–3 hours per file, produces analyst-to-analyst variance, and misses digital fraud signals that are invisible to visual review
- **Logic:** Automated ingestion pipeline processes the PDF, classifies income and expense across channels, tracks obligation continuity, and runs forensic checks — producing a structured credit report
- **Config:** 34+ bank parsers, 40+ engineered credit signals, 150+ RBI holidays, 10 risk categories, 24 expense categories, OCR fallback for degraded scans
- **Output:** Structured Excel workbook with financial analysis, credit signals, fraud flags, and a JSON version for LOS/CRM integration

### What is Cash Application (Cash App) in Receivables Reconciliation: Indian Finance Reference

Source: https://www.terra-insight.com/insights/what-is-cash-app-cash-application-glossary/

- **Problem:** Indian AR teams accumulate days of unapplied cash because incoming customer receipts in NEFT, RTGS, IMPS, and UPI rarely carry the invoice reference, customers settle multiple invoices in one transfer, and TDS deducted at source breaks every clean amount match.
- **Logic:** Run cash application as a tiered match — first UTR or virtual account, then invoice reference in narration, then amount-plus-customer probabilistic match — and quarantine any residual credit into an unapplied bucket with structured follow-up to the customer.
- **Config:** A customer master enriched with bank account fingerprints, GST-aware TDS expectations per income-type code, virtual-account assignments where active, and a 24-hour ageing rule for unapplied cash.
- **Output:** An AR sub-ledger where every settled invoice carries a UTR and a bank narration line, an unapplied cash balance that ages within a known SLA, and a customer-confirmation trail for every disputed allocation.

### What is a Debit Note vs Credit Note under GST Section 34: Indian Reference

Source: https://www.terra-insight.com/insights/what-is-debit-note-credit-note-section-34-glossary/

- **Problem:** Indian suppliers and recipients lose GST effect on price corrections, goods returns, and post-supply discounts because credit notes are not issued before the Section 34 cut-off date or because debit notes are not picked up correctly by the recipient against the original invoice.
- **Logic:** Maintain a closed-loop reference between every credit note, every debit note, and the original tax invoice; track the Section 34 30 November cut-off automatically; reconcile the GSTR-2B impact on the recipient side to the GSTR-1 declaration on the supplier side.
- **Config:** A document master that enforces original invoice reference on every credit and debit note, an alert thirty days before the 30 November cut-off, and a reconciliation rule that pairs supplier credit notes to recipient ITC reversals.
- **Output:** A clean Section 34 register at year-end with no overdue credit notes, every debit note matched to a recipient ITC claim, and a documented GSTR-2B trail that survives audit.

### What is Form 168 in Income Tax Act 2025: TDS Credit Statement Replacing Form 26AS for FY 2026-27 onwards

Source: https://www.terra-insight.com/insights/what-is-form-168-tds-glossary/

- **Problem:** From FY 2026-27 onwards Indian deductors and deductees must transition from Form 26AS to Form 168, with the additional complexity that the new income-type codes 1001-1092 replace section-name reporting and a single mis-classification flows into the recipient's tax credit record.
- **Logic:** Map every legacy Section 194x code to its FY 2026-27 income-type code at deduction time, deduct and report under the new code, and reconcile Form 168 entries to the books on the basis of the income-type code, gross amount, and deductor TAN.
- **Config:** A maintained mapping table from old Section codes to new income-type codes 1001-1092, refreshed when CBDT issues clarifications, plus an automated check that flags Form 168 entries whose code does not match the books.
- **Output:** A reconciled Form 168 view at quarter-end and year-end with every deductor entry tied to a books entry under the matching new income-type code, and a clean audit trail for any open mismatches.

### What Is GSTR-2B? The Auto-Populated ITC Statement Explained

Source: https://www.terra-insight.com/insights/what-is-gstr-2b/

- **Problem:** ITC claimed in GSTR-3B may exceed GSTR-2B credits due to supplier non-filing, invoice mismatches, or timing differences — exposing the company to demand notices and interest.
- **Logic:** Match purchase register invoices to GSTR-2B entries by GSTIN, invoice number, date, and taxable amount. Unmatched invoices classified as supplier-not-filed, amount-mismatch, or not-in-period.
- **Config:** Rule 36(4) compliance limit, GSTIN validation, tolerance ≤ ₹2 on taxable value, IGST/CGST/SGST component matching.
- **Output:** Reconciled ITC register with GSTR-2B backing, ineligible ITC flagged, reversals identified, and net claimable ITC per return period.

### What is ITC-04: Job Work Quarterly Form Explained for Indian Manufacturers

Source: https://www.terra-insight.com/insights/what-is-itc-04-job-work-glossary/

- **Problem:** Indian principal manufacturers lose ITC and incur interest because job-work dispatches under Section 143 are not closed within the one-year or three-year statutory window, and the issue surfaces only at the half-yearly ITC-04 filing.
- **Logic:** Maintain a live challan-level register linking every outbound dispatch to either a return challan, an onward job-work challan, or a supply invoice. Age the open challans against the statutory clock and flag any approaching the limit.
- **Config:** Master data flagging input goods versus capital goods, the applicable one-year or three-year clock per challan type, and an alert threshold at 30 days before the deemed-supply date.
- **Output:** A clean ITC-04 statement with all outbound, return, onward, and supply movements reconciled at the challan level, and zero overdue dispatches by the filing date.

### What Is NACH in Banking? National Automated Clearing House Explained

Source: https://www.terra-insight.com/insights/what-is-nach/

- **Problem:** NACH batch debit files show presentment counts that differ from bank-confirmed debit counts; return files arrive with coded reasons requiring classification and lender action.
- **Logic:** Match each UMRN in the presentment file to the bank acknowledgement file, then to the return file by UMRN and amount. Returns classified by code (01/05/20/25/27) and linked to loan account records.
- **Config:** UMRN as primary key, return code taxonomy, DPD calculation from due date, NPA trigger thresholds per RBI guidelines.
- **Output:** Per-UMRN status (presented/cleared/returned), return reason distribution, DPD report, and portfolio health dashboard.

### What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account

Source: https://www.terra-insight.com/insights/what-is-payment-gateway-settlement/

- **Problem:** Payment gateways remit net settlements after deducting MDR, GST on MDR, buyer-side TDS where applicable under Section 393(1) Sl. 8(ii) code 1031 (purchase of goods, 0.1% above ₹50 lakh — successor to Section 194Q; Section 206C(1H) TCS on goods sale is inapplicable since 1 April 2025 under the Finance Act 2025 proviso and has no successor TCS code in the 1001-1092 schedule), and refund adjustments. The net amount does not match any single order value.
- **Logic:** Decompose each settlement into gross collection less MDR, less GST on MDR, less refunds, less any buyer-side TDS (Section 393(1) Sl. 8(ii) code 1031 where applicable) equals net payout. Match each component to order-level records using payment reference ID.
- **Config:** Gateway-specific MDR rates, GST at 18% on MDR, Section 393 code 1031 threshold ₹50 lakh aggregate, refund netting window ±7 days, settlement cycle T+1 for UPI and T+2 for cards.
- **Output:** Order-level settlement breakdown with typed variance codes (FEE_DEDUCTION for MDR, TAX_DEDUCTION for GST and any Section 393 code 1031 TDS), unmatched settlements flagged.

### What is RMPV (Raw Material Price Variation): Auto-Component Index-Linked Pricing

Source: https://www.terra-insight.com/insights/what-is-rmpv-raw-material-price-variation-glossary/

- **Problem:** Auto-component suppliers and OEMs disagree on the rupee amount due under index-linked RMPV clauses because the two sides use slightly different index series, different period definitions, or different rounding conventions, leaving cumulative settlement gaps over a quarter.
- **Logic:** Reconstruct the contractual formula — base index, period index, weightage, applicable quantity — independently on both buyer and seller side, recompute the variation rupee value, and isolate disagreements to a specific formula input rather than the rupee output.
- **Config:** A part-number-level master that stores the contractual base index, the index source and series, the period definition, the quantity basis (dispatched, received, invoiced), and the rounding rule per OEM-supplier pair.
- **Output:** An RMPV credit or debit note backed by a transparent worksheet showing every formula input, the GST treatment under Section 34, and a clean link to the original supply invoices in the OEM's GSTR-2B.

### What Is TDS Deduction? How Tax Deducted at Source Works in India

Source: https://www.terra-insight.com/insights/what-is-tds-deduction/

- **Problem:** TDS deducted by payers appears in TRACES/Form 26AS but may not match the company's TDS receivable ledger due to wrong PAN, wrong section, short deduction, or non-deposit by deductor.
- **Logic:** Match TDS receivable ledger entries to Form 26AS credits by deductor TAN, PAN, amount, and quarter. Mismatches classified as short deduction, wrong section, or UNEXPLAINED.
- **Config:** Section-wise rate table (194C: 1%/2%, 194J: 10%, 194H: 5%), TAN-PAN pair validation, quarter-end aggregation.
- **Output:** Reconciled TDS receivable ledger with TRACES credits, unmatched entries with deductor details for follow-up, and Form 26AS delta report.

### What is Three-Way Matching in Indian Accounts Payable: PO–GRN–Invoice Reconciliation

Source: https://www.terra-insight.com/insights/what-is-three-way-match-india-glossary/

- **Problem:** Indian AP teams release payments against invoices that did not have a matching goods receipt, exposing the company to ITC reversal under Section 16, duplicate payments, and TDS coding errors at year-end.
- **Logic:** Cross-validate three documents — Purchase Order, Goods Receipt Note, and Vendor Invoice — on quantity, rate, and tax treatment before any payment authorisation. Block payment release if any field falls outside the configured tolerance band.
- **Config:** Tolerance bands per spend category — for example zero quantity tolerance on capital items, plus or minus two percent rate tolerance on commodity inputs — plus a configurable hold list for vendors with repeated mismatches.
- **Output:** A payment-ready voucher with a clean audit trail linking PO, GRN, and invoice, the correct GST treatment, and the correct new TDS code populated for the FY 2026-27 return.

### What is a Virtual Account in Bank Reconciliation: Indian Treasury Reference

Source: https://www.terra-insight.com/insights/what-is-virtual-account-bank-reconciliation-glossary/

- **Problem:** Indian AR and treasury teams cannot identify which customer paid a given bank credit when the underlying NEFT, RTGS, IMPS, or UPI rail carries a UTR but no invoice reference in the narration, leading to high unapplied cash balances.
- **Logic:** Issue each customer a unique virtual account number mapped to a single physical master collection account, so every incoming credit carries the payer's virtual identifier and customer identification is deterministic at the bank-file level.
- **Config:** A customer master enriched with virtual account assignments, a daily bank file ingestion that reads the virtual ID field, and a reconciliation rule that matches virtual ID to customer code as the primary key before any narration-based fallback.
- **Output:** A bank reconciliation in which every master-account credit is tagged to a customer at the point of receipt, unapplied cash collapses to near zero, and AR cash application becomes a one-pass invoice allocation rather than a payer-identification puzzle.

### White-Label Reconciliation for CA Firms: Branded Client Deliverables

Source: https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india/

- **Problem:** CA firms deliver reconciliation reports under the firm's letterhead and partner sign-off, but most reconciliation platforms ship with vendor branding in the PDFs, the portal URL, and the email notifications — undermining the firm's brand continuity and violating the unwritten rule that the client should see only the firm's identity on compliance deliverables.
- **Logic:** Deploy white-label settings that remove all vendor branding from client-facing output: firm logo and address block on every PDF, partner signature placeholder, custom sub-domain (clients.firmname.com) for the portal, email notifications from the firm's own domain, and optional custom terminology. ICAI Code of Ethics permits this so long as professional responsibility is retained and the engagement letter discloses the underlying technology.
- **Config:** Firm branding pack — logo, colour palette, address block, signature image, sub-domain and DNS settings, SMTP credentials for email, and custom terminology overrides. Per-client toggles so some clients can optionally receive co-branded output while others get firm-only branding.
- **Output:** Every reconciliation report, client portal session, and email notification carries the CA firm's identity exclusively, enabling a fee uplift of ₹2,000–₹8,000 per client per month without adding staff and preserving the firm's multi-year client relationship equity.

### Why OEMs Pay 8-12% Less Than Invoice Value — And How Indian Auto Suppliers Reconcile the Gap

Source: https://www.terra-insight.com/insights/why-oem-pays-less-than-invoice-auto-component-india/

- **Problem:** Suppliers new to the OEM commercial model are blindsided by the 8-12% structural short-pay that arrives with the first Maruti, Tata, Mahindra, Hyundai or Bajaj payment. The auto-debit regime — OEM pays first, supplier reconciles second — runs six standard deduction categories at predictable rate bands. The GST credit-note overhang under Section 34, the working-capital cost of carrying the variance through ageing, and the differentiation between OEM-initiated auto-debit and supplier-initiated back-charge are all unfamiliar territory for a new-to-OEM Tier-1 or Tier-2 supplier.
- **Logic:** Frame the OEM commercial relationship as a structurally different model from regular B2B — no pre-payment negotiation window, deduction first then reconciliation, scheduling-agreement call-offs not POs, running cumulative quantities not discrete units. Decompose each settlement into the six standard deduction categories with their typical rate bands, compute the working-capital implication, calendar the Section 34 GST credit-note window, and separate the OEM-initiated auto-debit cycle from the supplier-initiated Tier-2 back-charge cycle.
- **Config:** OEM customer master with payment terms (typically 45-60 days from GRN), six-category deduction-rate matrix as planning benchmarks (FOMP 1-3%, JIT 0.5-1.5%, quality 0.5-1.5%, line-stop 0.2-0.7%, tooling 0.2-0.5%, transport 0.3-0.8%), Section 34 GST credit-note calendar keyed to 30 November of next FY, ageing buckets for variance carry-cost computation, and separate workflow tracks for auto-debit reconciliation and Tier-2 back-charge recovery.
- **Output:** A new-to-OEM supplier orientation pack: expected short-pay band per OEM, six-category planning provision, working-capital cost forecast at typical billing volume, GST credit-note calendar pack, reconciliation-engine readiness assessment, and the differentiation between auto-debit reconciliation and back-charge recovery as separate operating processes.

### Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity

Source: https://www.terra-insight.com/insights/why-reconciliation-different-india/

- **Problem:** Indian reconciliation operates three simultaneous tax-at-source layers (TDS, TCS, GST ITC) that each create a gap between invoice amount and received amount. Generic accounting tools treat the bank line as the truth and cannot reconcile invoice, bank credit, and Form 26AS or GSTR-2B portal credit as a single matched event.
- **Logic:** Match at three levels for every receipt: invoice to bank credit (net of TDS), deducted TDS to Form 26AS on TRACES by TAN and section, and GST on the invoice to GSTR-2B by GSTIN. For platform settlements, disaggregate each bulk credit into its underlying orders, MDR, TCS, and GST components before matching.
- **Config:** TAN-aware TDS matching, GSTIN and invoice tolerance rules, platform settlement disaggregation templates per gateway (Razorpay, PayU, Cashfree), and NACH batch unpacking with UMRN keys.
- **Output:** A unified matched ledger where bank, invoice, TDS portal credit, GST portal credit, and platform settlement all reconcile to the same transaction — ready for statutory audit, GSTR-9 working papers, and ITR filing.

### Working Capital Leakage from Reconciliation Delays: A CFO Estimation Framework

Source: https://www.terra-insight.com/insights/working-capital-leakage-reconciliation-delay-india/

- **Problem:** Indian businesses with manual or partially-automated reconciliation operations carry 12-22 days of reconciliation delay between cash receipt and invoice closure. On a ₹140 crore receivable base this traps ₹4.6 to ₹8.4 crore of working capital relative to a mature 4-day cycle. At MCLR-anchored cost-of-capital of 10-11%, the annual leakage runs ₹46 to ₹92 lakh. The leakage does not appear on any conventional P&L line — it is buried in financing cost on bank-borrowed working capital that could have been displaced by faster reconciliation.
- **Logic:** Define days-recon-delay as the average days between bank credit date and AR invoice-close date over a quarter. Multiply by daily average receivable base to compute trapped working capital. Multiply by realistic cost-of-capital input — MCLR plus spread for bank-financed working capital, AAA short-tenor placement rate for operating cash, weighted issuance yield for businesses with NCD or CP programmes. Express the leakage as annual rupee figure feeding the audit committee pack and the board-case business case for reconciliation investment.
- **Config:** Receivable base measurement at daily granularity across the quarter. Days-recon-delay calculator with bank-credit-date and AR-close-date primary keys. Cost-of-capital input table with MCLR plus spread, placement rate, and CP yield variants. Quarterly leakage trend report by business unit. Sensitivity analysis on cycle reduction targets. Integration with the broader Discovered Money register as the financing-cost overlay on every other leakage class.
- **Output:** A monthly working-capital leakage dashboard with current cycle days, trapped cash, and annual leakage figure. A quarterly trend showing cycle reduction and leakage recovery. A board-pack one-pager showing cycle reduction from baseline to target with rupee value. A sensitivity table by cost-of-capital input. An integrated leakage view combining working-capital cost with the other six leakage classes.

### Working Capital Release via Leakage Recovery: A Treasury Playbook for Indian Enterprises

Source: https://www.terra-insight.com/insights/working-capital-release-leakage-recovery-india/

- **Problem:** Indian Group Treasurers and CFOs typically run the working-capital line and the leakage-recovery line on separate tracks. The treasurer sizes the cash-credit facility, manages drawdown, and reports utilisation. The controllership runs reconciliation, classifies residuals, and chases disputes. The two functions rarely share a number. The result is that unrecovered leakage sits on the balance sheet as a current asset funded silently by CC/OD facility at the prevailing rate — 9 to 11 percent in the current environment — without anyone treating it as a working-capital problem. A treasury playbook that connects the two functions through a joint committee, a monthly close cycle, and a working-capital release board pack converts leakage recovery into measurable balance-sheet management and equivalent debt reduction.
- **Logic:** Treat every rupee of unrecovered leakage as a rupee of CC/OD facility consumed at the marginal cost of capital. Map the seven leakage classes to a conversion model that shows days locked and working-capital impact per class. Establish a joint working-capital-and-leakage committee with shared KPIs across treasury and controllership. Operate a five-business-day monthly close cycle (T+5 cut-off, T+8 register update, T+12 treasury impact, T+15 audit-committee delta). Report to the board as rupees released this quarter, rupees in pipeline, rupees structurally lost, and equivalent debt reduction with annualised interest saving. Integrate with the broader Discovered Money register and the existing reconciliation engine so the treasury view is a derived layer rather than a parallel record.
- **Config:** Per-class leakage-to-working-capital conversion model with days locked and CC/OD cost per rupee. Joint committee terms of reference covering chair, attendees, agenda, and shared KPIs. Monthly leakage close cycle calendar with T+5, T+8, T+12, T+15 milestones. Working-capital release board pack template with the four numbers and the trend chart. Equivalent debt reduction roll-forward register that ties recovered leakage to actual CC/OD movement or to opportunity-cost saving. Cost-of-capital rate sourced from the actual CC/OD facility and updated quarterly. Integration spec with the Discovered Money register and the reconciliation engine residual feed.
- **Output:** A monthly treasury view of leakage outstanding by class, leakage as a percentage of average CC/OD utilisation, and the annualised interest burden. A monthly five-business-day close cycle that produces the audit-committee delta on the same rhythm as the main treasury report. A quarterly working-capital release board pack with rupees released, in pipeline, structurally lost, and equivalent debt reduction. An annual treasury-and-controllership joint review covering KPI evolution, cost-of-capital movement, and the next-year leakage recovery target translated into a working-capital release target.

### Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment

Source: https://www.terra-insight.com/insights/works-contract-reconciliation-india/

- **Problem:** Indian manufacturers running factory expansion, civil works, plant maintenance and turnkey installation contracts struggle to reconcile contractor RA (running account) bills against the PO because of composite supply complexity (goods and services bundled), the 12% vs 18% GST rate split for specified categories, Section 17(5) blocked credit on building works, retention and mobilisation advance recovery accruals, and Section 393(1) Sl. 6(i) contractor TDS (codes 1023/1024) calculated on the gross bill — producing a long-tail of stuck contractor payments and ITC mis-claims.
- **Logic:** Classify each works contract by immovable vs movable property (Section 2(119) test), by rate category (12% concessional vs 18% standard), and by ITC eligibility (blocked under Section 17(5) for building/civil, allowed for plant and machinery foundation); on each RA bill apply retention deduction, mobilisation recovery, material recovery, and TDS under Section 393(1) Sl. 6(i) — code 1023 at 1% (Ind/HUF) or code 1024 at 2% (other) — on the gross value excluding GST; reconcile cumulative retention held, mobilisation balance and material recovery across the contract life.
- **Config:** Works contract master with contract type (immovable/movable), GST rate (12%/18%), ITC eligibility flag (blocked/allowed/plant-machinery), retention percentage, mobilisation advance balance, material recovery rate, contractor PAN/GSTIN, Section 393(1) Sl. 6(i) TDS rate (code 1023 at 1% Ind/HUF, code 1024 at 2% other), threshold tracker per PAN, and RA bill ageing buckets.
- **Output:** A clean works contract ledger where each RA bill ties to the PO, retention held accumulates to the contract retention account, mobilisation balance reduces with each recovery, TDS deducted at 1% or 2% on the correct base ties to the monthly Section 393 challan and quarterly Form 26Q, ITC is claimed only on the plant-and-machinery portion (not on blocked building works), and final retention release at defect liability period closure ties back to the original holdback ledger.

### Works Contractor Payments TDS: Section 393(1) Sl. 4 (Legacy 194C) for Developers

Source: https://www.terra-insight.com/insights/works-contractor-tds-section-194c-real-estate-code-1023-india/

- **Problem:** An Indian real estate developer paying dozens of works contractors — main contractor, MEP, façade, finishing, landscaping, HVAC, electrical, plumbing — must deduct TDS under Section 393(1) Sl. 4 (legacy 194C) at 1% for individual/HUF payees (code 1001) or 2% for companies and other entities (code 1023), monitor the ₹30,000 single / ₹1,00,000 aggregate per-PAN threshold with mid-year back-deduction where needed, file Form 26Q quarterly with correct section codes and PANs, and reconcile the contractor GST on 18% construction services against Rule 42 proportionate ITC given the pre-CC taxable / post-CC exempt output mix.
- **Logic:** Classify each contractor PAN at onboarding using the fourth character (P/C/F/H/T) to derive the correct TDS rate; monitor per-PAN running aggregate against ₹30K single / ₹1L annual thresholds and trigger back-deduction where crossed; deduct on invoice value net of GST where GST is separately indicated; tie contractor ledger to TDS challan register monthly and to Form 26Q data pack quarterly before filing; separately track contractor GST for Rule 42 proportionate ITC computation and annual true-up at project close.
- **Config:** Contractor master with PAN, fourth-character-derived category, deduction section (Sl. 4 code 1001 or 1023), applicable rate, GSTIN, GST rate 18% HSN 9954; per-PAN running aggregate tracker with FY reset; TDS challan register with challan number, BSR code, deposit date, amount tied per deduction; Form 26Q data pack with PAN-wise deductee lines aggregated across projects under one TAN; Rule 42 configuration with taxable/exempt output ratio per project and monthly common-credit apportionment; project master flagging affordable (1%) vs non-affordable (5%) output rate.
- **Output:** A monthly per-project contractor ledger reconciled to bank payments and TDS challans; a TAN-level Form 26Q data pack ready for quarterly TRACES filing with PAN validation and section code accuracy; a Rule 42 monthly apportionment showing common-credit ITC availed vs reversed with a running true-up figure; an audit-ready evidence trail per contractor invoice showing invoice-to-payment-to-TDS-to-26Q chain with challan reference, deduction section, PAN category, and GST portion tagged for ITC treatment.

### Yarn-to-Fabric Inverted-Duty Refund — Rule 89(5) Application for Textile

Source: https://www.terra-insight.com/insights/yarn-fabric-inverted-duty-refund-textile-rule-89-5/

- **Problem:** Indian composite textile mills that spin yarn at a 5% output rate and weave fabric at a 12% output rate accumulate input tax credit faster than the output tax utilises it — the classic inverted-duty structure. Cash is trapped in the electronic credit ledger every month unless the mill files a Rule 89(5) refund application on RFD-01. The formula is exacting: Net ITC excludes input services and capital goods per Notification 14/2022, Adjusted Total Turnover must be computed per period, and the result is netted against tax already paid on the inverted-rated supply. Errors in the Net ITC split (mixing services with goods), in the turnover attribution (crediting the whole book instead of the inverted-rated leg only), or in the timeline (missing the 2-year window from the relevant date) either forfeit the refund or trigger an RFD-01 rejection with re-filing burden.
- **Logic:** Split the ITC register at source into three buckets for every tax period: input goods (eligible for Net ITC), input services (excluded), and capital goods (excluded). Split the turnover register into inverted-rated supply (fabric leg at 12%), non-inverted supply (yarn at 5%), exempt supply, and zero-rated exports. For each month, compute Net ITC = input-goods ITC availed less any reversals. Compute Adjusted Total Turnover per the rule reading. Apply the formula: (Fabric turnover × Net ITC ÷ Adjusted Total Turnover) − Fabric output GST already paid. If the result is positive, file RFD-01 for that amount within the month. If negative or zero, log the workpaper and skip the month. Track the 2-year window per period so no eligible refund lapses.
- **Config:** ITC ledger with per-invoice type flag (input goods / input services / capital goods) at the moment of GSTR-2B reconciliation; turnover ledger by HSN with output-rate mapping (5% yarn versus 12% fabric); RFD-01 monthly workpaper template with Statement 1 (Net ITC computation) and Statement 1A (inverted-rated supply turnover auto-populated from GSTR-1); Notification 14/2022 exclusion policy encoded in the ITC-classification rules; 2-year time-limit tracker per relevant-date computation; audit trail of every month's calculation including zero-refund and negative-refund periods.
- **Output:** Monthly RFD-01 application ready for GST portal filing with Statement 1 Net ITC figure, Statement 1A inverted-rated turnover figure, calculation of maximum refund per Rule 89(5), and the netting against tax already paid. A period-by-period ledger of refunds claimed, refunds sanctioned, refunds rejected (with reason codes), and refunds pending. A separate register of periods where the formula returned zero or negative (with workpaper backing) so no assumption is left unverified. A relevant-date tracker flags any period nearing the 2-year window with sufficient lead time to file the refund before it lapses.

### Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices

Source: https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india/

- **Problem:** March 31 is a hard deadline for Indian year-end reconciliation: unresolved TDS mismatches in Form 26AS, unclaimed ITC from GSTR-2B, and unreconciled bank or RERA escrow entries roll into the next assessment year with compounding penalty and interest consequences.
- **Logic:** Sequence the close by deadline: bank recon first, then TDS receivable against Form 26AS by TAN and section code, GSTR-2B versus purchase register by GSTIN and invoice, platform settlements by UTR, and finally fixed-asset and statutory dues. Raise deductor correction requests before March 31 to preserve the claim in the correct AY.
- **Config:** Calendar-anchored workflow starting in February, deductor-level TDS matching rules, GSTR-2B invoice-level tolerance bands, and an exception queue with March 25 cutoff for matching and March 28 for escalation.
- **Output:** Auditor-ready year-end pack: signed bank recon statements, Form 26AS reconciled TDS register, GSTR-9 and GSTR-9C working papers, and a documented exception trail for statutory audit.

### Yes Bank Corporate Statement Reconciliation

Source: https://www.terra-insight.com/insights/yes-bank-corporate-reconciliation-india/

- **Problem:** Yes Bank corporate statements arrive across YES Online portal exports, YES Connect host-to-host files, and MT940 — each carrying forward-slash-delimited narrations that look similar to HDFC and ICICI but with no /INF/ prefix in MT940, leading parsers misconfigured for vendor prefixes to either strip valid characters or miss UTRs entirely. NACH batch credits collapse mandate-level detail, and the post-2020 reconstruction adds a legacy account-number remap consideration for historical reconciliation.
- **Logic:** Channel-aware parsing routes YES Online portal CSV, YES Connect SFTP files, and MT940 to dedicated configurations. Narrations are split on forward slashes and the second segment validated as a 22-character UTR for NEFT and RTGS, a 12-digit reference for UPI, and a batch reference for NACH. NACH single-line batch credits are exploded against the NPCI settlement report or the YES Connect NACH MIS file. Legacy account-number remap is applied only for pre-2020 historical reconciliation when flagged by the relationship manager.
- **Config:** Yes Bank forward-slash parser profile with no vendor prefix strip, YES Connect SFTP ingestion for host-to-host files and MT940, YES Online CSV fallback with completeness alert, legacy account remap toggle for historical pre-2020 reconciliation, Section 194A TDS auto-reconciliation for interest credits above ₹40,000.
- **Output:** Clean transaction ledger from Yes Bank statements regardless of channel, mandate-level NACH explosion via the NPCI or YES Connect MIS join, bank-charges GL line with ITC-eligible GST schedule, and Section 194A TDS credit aligned to Form 26AS.

### Yield Reconciliation in Auto-Component Stamping: Skeleton Scrap, FI Steel and Section 394 TCS

Source: https://www.terra-insight.com/insights/yield-reconciliation-stamping-skeleton-scrap-auto-india/

- **Problem:** Indian auto-panel stamping suppliers operate on OEM-owned (free-issue) coil where the coil enters under Rule 55 challan with no GST, gets converted into good parts at part-specific yield bands of 55-85%, and returns to the OEM as good parts plus skeleton scrap plus end scrap, with a small reconciled in-process loss — every kilogram must close between coil-in, good-parts-out, scrap-returned-or-sold and process-loss; a stamping yield drop of 3 percentage points below the MSA-agreed band on a door-inner triggers an OEM yield-deviation short-pay on the conversion-charge bill, and the scrap leg attracts Section 394 TCS at 1% under payment code 1071 (replacing legacy Section 206C(1) from 1 April 2026) on the supplier or the OEM depending on the disposal contract; on a typical 12 MT/day panel supplier with 68% yield on door-inners the annual TCS exposure on skeleton-scrap sale alone runs to ₹4-7 lakh and the yield-deviation short-pay exposure runs to ₹15-25 lakh.
- **Logic:** Stamp every FI-steel inward at the supplier's gate with coil weight, grade, OEM dispatch challan reference and intended part programme; track the conversion: coil weight = good-parts weight + skeleton-scrap weight + end-scrap weight + reconciled in-process loss; calculate actual yield against the MSA-agreed band per part programme; surface yield deviation in real time and route to short-pay-candidate queue if below lower bound; classify scrap by disposition (returned to OEM under Rule 55 / sold from supplier premises under OEM authorisation / sold from OEM premises after return); apply Section 394 TCS at 1% under payment code 1071 on the leg that sells from supplier premises; reconcile to the OEM's outbound dispatch register and the supplier's gate-pass and production records monthly.
- **Config:** Part programme master with MSA-agreed yield band, scrap-equivalent rate, scrap disposal contract type (return / sell-from-supplier / sell-from-OEM), Section 394 TCS applicability flag; FI-steel inward register with Rule 55 challan reference, coil weight and grade; production register with good-parts weight and count per shift; scrap register with skeleton and end scrap weights returned or disposed; yield calculation engine with band-comparison and short-pay-candidate generation; TCS application at 1% under payment code 1071 on supplier-sold scrap; monthly reconciliation pack to OEM outbound register.
- **Output:** A daily yield report by part programme with band-comparison status; the yield-deviation short-pay candidate queue with OEM debit-note projection; the FI-steel monthly reconciliation pack closing coil-in to good-parts-out plus scrap plus loss; the Section 394 TCS register on scrap-sold-from-supplier-premises with payment-code 1071 tagging; the supplier-side three-way match exception register tied to yield deviation; and a board-visible yield-and-FI-steel dashboard for the panel programme.

### Zepto FMCG Settlement Reconciliation

Source: https://www.terra-insight.com/insights/zepto-fmcg-settlement-reconciliation/

- **Problem:** An Indian FMCG brand selling ₹2 to ₹3 crore monthly on Zepto receives a settlement file on a T+10 cycle covering multiple SKUs across personal care, biscuits, chocolates and home care, with seven deduction categories per cycle, BOGO scheme reimbursement claimed at 8 to 10 percent of gross, listing-fee debits for new-launch SKUs at 2 to 3 percent of gross, Section 52 TCS withheld at the 0.5 percent notified rate, and a residual bank credit that has to reconcile back to GSTR-1 outward supply, Zepto's GSTR-8 TCS line, GSTR-2A TCS credit and the bank statement. Without a structured Zepto-specific reconciliation discipline that includes the MRP-versus-listing-price audit and the BOGO scheme claim cross-check, brands typically lose 1.5 to 3 percent of Zepto channel revenue inside silent off-MRP discounting and over-claimed scheme reimbursements that the reconciliation never decomposed.
- **Logic:** Ingest Zepto's daily settlement file with a Zepto-specific parser; decompose every gross invoice into seven buckets — item-level margin off MRP, listing fee per new-launch SKU, ad and slotting invoices (kept separate, 18 percent GST claimed as ITC), BOGO and scheme reimbursement classified by Section 15(2) treatment per scheme, fill-rate and QC penalties, return-to-vendor credit notes against expiry-near stock, and Section 52 TCS at the 0.5 percent notified rate. Run the MRP-versus-listing-price audit each cycle — printed MRP, brand PTR, Zepto app price and net realisation tracked per SKU per cycle. Tie the Section 52 TCS line three-way (settlement file, GSTR-8, GSTR-2A). Cross-check BOGO claims against Zepto's promotion-redemption file. Apply the rate-by-date table for the 22 September 2025 GST 2.0 cut-over on chocolate, biscuits, soaps, shampoos and toothpaste HSN categories.
- **Config:** Zepto settlement-file parser with deduction-taxonomy mapping; SKU master with printed MRP, HSN, GST rate and 22 September 2025 cut-over flag; PTR-to-Zepto-app-price audit register with per-SKU per-cycle tracking; scheme master with Section 15(2) treatment flag per scheme and per-promotion redemption mechanic; BOGO claim reconciler against Zepto promotion-redemption file; ad-invoice register routed to marketing GL with ITC claim; Section 52 TCS register at the 0.5 percent notified rate (CBIC Notification 15/2024-CT); GSTR-1 tagging rule for Zepto-channelled outward supplies (Zepto TCS-collector GSTIN); GSTR-8 ingestion for Zepto per month; GSTR-2A TCS credit reconciliation rule; bank-statement matcher for Zepto net settlement receipts on T+10 horizon; Section 9(5) exclusion flag (FMCG goods are NOT in the deemed-supplier regime).
- **Output:** A monthly Zepto settlement pack: gross invoice raised, seven-bucket deduction decomposition with named-line breaks, MRP-versus-Zepto-app-price audit with per-SKU per-unit net realisation, BOGO claim cross-check against Zepto redemption file with leakage flagged, net bank receipt tied to Zepto payment advice on the T+10 cycle, Section 52 TCS three-way tie (settlement file, GSTR-8, GSTR-2A), GSTR-1 outward-supply tagging audit trail, ad-spend invoice register with ITC posture, scheme reimbursement ageing buckets (0-30 / 31-60 / 61-90 / 90+ days), GST 2.0 rate-by-date audit log for chocolate, biscuits, soaps, shampoos and toothpaste, and a leakage summary surfacing unrecovered listing fees, mis-tagged ad-spend deductions, off-MRP discounting and any Section 9(5) versus Section 52 treatment error before it reaches the GSTR-3B cycle close.

### ZF and Continental India Tier-1 Reconciliation: Global Captive Operating Model

Source: https://www.terra-insight.com/insights/zf-continental-india-supplier-reconciliation/

- **Problem:** Global Tier-1 captives in India — ZF (Pune, Chennai, Coimbatore), Continental (Bangalore, Pune, Gurgaon) — operate a dual-purpose commercial model selling domestically to Indian OEMs in INR while exporting to the global parent for onward delivery to global OEMs in EUR / USD. The reconciliation engine must handle two parallel commercial frameworks inside one legal entity: domestic INR book under Indian tax discipline with Section 393 TDS / GSTR-1 / Section 34 credit-note timing; and export EUR / USD book under cross-border invoicing with LUT / GSTR-1 Table 6A / RoDTEP / IGST refund discipline, transfer pricing under Section 92 / 92CA with APA target, EDI translation between parent-format (VDA / ANSI X12) and Indian-convention messages, and Section 393(2) Sl. 17 code 1057 on the cross-border pay-leg for technical-service fees and royalty.
- **Logic:** Decompose each captive transaction into the domestic INR sub-ledger (sales to Maruti / Tata / Mahindra / HMI / commercial-vehicle OEMs) or the export EUR / USD sub-ledger (sales to global parent), tie each sale to the source vehicle programme on both sides, reconcile the export invoice to the LUT / GSTR-1 Table 6A submission and the RoDTEP claim file, track the operating margin on the export book against the APA target with year-end true-up exposure, reconcile EDI translation variance between parent-format messages and Tier-2-friendly formats, age each FOMP / warranty claim against the per-OEM / per-programme running account, calendar Section 34 GST credit notes per accepted debit on the domestic leg, and reconcile Form 168 TDS deductions separately for Section 393 (domestic Tier-2) and Section 393(2) (cross-border pay-leg).
- **Config:** Captive customer master with separate parent records for domestic OEMs (Maruti / Tata / Mahindra / HMI / commercial-vehicle OEMs) and the global parent (inter-company), portal export-mapping per domestic OEM and EDI middleware logs for parent-format messages, RMPV register split by INR-denominated domestic and EUR / USD-denominated export with currency variance carved out separately, transfer pricing register tracking actual operating margin against APA target, LUT / GSTR-1 Table 6A export-invoice register, RoDTEP claim register, Form 168 TDS register split between Section 393 (domestic Tier-2) and Section 393(2) Sl. 17 code 1057 (cross-border pay-leg), DTAA rate reference for the relevant parent jurisdiction (Germany for Continental and ZF parent flows), Section 34 GST credit-note calendar.
- **Output:** A dual-ledger captive view — domestic INR settlement decomposed per OEM per programme with debit / credit reason coding, and export EUR / USD settlement reconciled against LUT / GSTR-1 Table 6A submissions and RoDTEP claims with currency revaluation at close. Transfer pricing tracker showing operating margin vs APA target with year-end true-up exposure flagged. EDI translation variance register surfacing parent-format vs Tier-2-format message discrepancies. Form 168 TDS register split between Section 393 domestic and Section 393(2) cross-border. RMPV register with currency variance carved out from commodity variance. Section 34 GST credit-note action queue.

### Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale

Source: https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india/

- **Problem:** Zoho Books' native GSTR-2B matcher, bank feeds, and pre-built Razorpay/PayU/Cashfree connectors work for Indian SMEs but break at specific scaling thresholds — 1,000 transactions per month per bank account, 500-row CSV bulk import cap, 100–200 API calls per minute rate limit, and no variance classification for CARO 2020 or Ind AS 115 audit evidence.
- **Logic:** Add an external reconciliation layer above Zoho Books via REST API v3 with OAuth 2.0. Pull invoices, bills, bank transactions, and customer payments in batched windows (200 records per call), run multi-pass matching with tolerance bands and a full variance taxonomy (FEE_DEDUCTION, TAX_DEDUCTION, TIMING_DIFFERENCE, ROUNDING, DUPLICATE), and push cleared-status updates back via the same API.
- **Config:** Zoho Books connector with OAuth 2.0 client credentials, endpoint registry (/invoices, /bills, /banktransactions, /customerpayments), rate-limit-aware batch scheduler, payment gateway aggregation logic for Razorpay/PayU/Cashfree/Stripe net-settlement grossing, and variance classification rubric keyed to audit evidence requirements.
- **Output:** A reconciled Zoho Books ledger beyond the native ceiling — gateway net-settlement grossed correctly, GSTIN typos and timing mismatches classified, CARO 2020 / Ind AS 115 audit evidence complete, and cleared-status updates pushed back to Zoho so the native UI reflects the true reconciled state.

### Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets

Source: https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig/

- **Problem:** A multi-outlet QSR chain reconciling Zomato weekly settlements at 50-plus outlets faces three structurally different process choices — manual Excel, an aggregator-side reconciliation tool, or reconciliation infrastructure — each with a different break point on order-level trace, deduction-stack accuracy, Section 393 and Section 52 ledger separation, GSTR-2B commission ITC matching, multi-outlet rollup, and CARO 2020 audit evidence.
- **Logic:** Walk each approach through the same Zomato weekly cycle: ingest the settlement file with order-level breakup, decompose the deduction stack (commission 25-35%, GST on commission at 18%, Section 393 TDS at 0.1% under payment code 1035 (down from the legacy 1% under 194O), Section 52 CGST TCS at 1% intra-state CGST/SGST or inter-state IGST, ad spend, restaurant-borne discounts, refund reversals), match against POS gross sales, link to the bank credit narration, post commission ITC against GSTR-2B, accept the TCS credit into the electronic cash ledger via GSTR-8A, post the income-tax TDS receivable, flag any Section 9(5) GST liability, roll up across outlets and GSTINs, and retain the audit trail.
- **Config:** Zomato weekly settlement-file connector with order-level breakup; commission tier rules; Section 393 TDS calculator at 0.1% on gross supply with payment code 1035 mapping; Section 52 CGST TCS calculator with intra-state CGST/SGST and inter-state IGST split; GSTR-2B commission ITC matcher; GSTR-8A cash-ledger acceptance flow; Section 9(5) GST liability classifier; refund-period reversal logic; multi-outlet and multi-GSTIN rollup; CARO 2020 audit evidence retention.
- **Output:** A weekly Zomato reconciliation in which every rupee in the bank credit traces back to an order, every deduction has an offsetting ledger entry posted to the right statute, the Section 393 TDS receivable and Section 52 TCS cash-ledger balance reconcile cleanly to source, GSTR-2B commission ITC is accepted on time, multi-outlet and multi-GSTIN rollups close inside the month, and CARO 2020 audit evidence is one query away.

### Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders

Source: https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation/

- **Problem:** Zomato's weekly settlement to restaurants is a single net bank credit covering hundreds of orders, but it conceals seven separate deduction streams — commission, GST on commission, TDS 194O, TCS Section 52, ad spend, refund reversals, and platform fees — none of which appear as individual line items in the bank statement.
- **Logic:** Pull the Zomato settlement file with order-level breakup, classify each order by deduction stack, accrue revenue at gross order value, book commission and GST on commission as expense with ITC, post TDS 194O receivable to balance with Form 26AS, post TCS as credit to offset GSTR-3B liability, and reverse any refunds against the original sale period.
- **Config:** Zomato settlement file connector with weekly cycle awareness; commission tier rules per restaurant agreement; TDS 194O 1% calculator on net taxable supply; TCS Section 52 calculator with intra-state vs inter-state split; ad-spend deduction parser; refund-period reversal logic keyed to original order ID.
- **Output:** A reconciled weekly Zomato payout where every rupee in the bank credit traces back to an order, every deduction has an offsetting ledger entry, and the TDS receivable plus TCS credit are claimable in the restaurant's quarterly tax filings without manual chase.

## Representative FAQs by cluster

The full FAQ corpus — every Q&A from every article — is available as structured JSON at https://www.terra-insight.com/faqs.json and as a human-readable page at https://www.terra-insight.com/faqs/. The FAQ sample below gives orientation.

### TDS Reconciliation

Q: What is the TDS rate under Section 194C for contractor payments?
A: The rate is 1% if the deductee is an individual or HUF, and 2% if the deductee is any other person (company, firm, LLP). The threshold for deduction is a single payment exceeding ₹30,000 or aggregate payments exceeding ₹1,00,000 in a financial year.

Q: What happens when TDS appears in Form 26AS but not in the company's books?
A: This is a timing mismatch — the deductor has filed and deposited TDS, but the company's TDS receivable ledger was not updated. The reconciliation fix is to post the TDS receivable entry in the books matching the 26AS credit by deductor TAN, PAN, section, and quarter.

Q: What is Section 206AB and when does it apply?
A: Section 206AB requires TDS at twice the applicable rate (or 5%, whichever is higher) when paying a "specified person" — someone who has not filed ITR for two preceding financial years and whose aggregate TDS/TCS was ₹50,000 or more in each of those years. Deductors run a TRACES Compliance Check before each payment.

### GST Reconciliation

Q: What is the difference between GSTR-2A and GSTR-2B for ITC reconciliation?
A: GSTR-2A is dynamic — it updates every time a supplier files or amends an invoice. GSTR-2B is static — it locks on the 14th of each month and reflects only invoices filed by suppliers up to that date. ITC can only be claimed based on GSTR-2B under Rule 36(4).

Q: What is the interest rate for wrongly claimed ITC in GST?
A: Interest at 18% per annum under Section 50 of the CGST Act applies on ITC claimed in excess of GSTR-2B entitlement. For ITC reversal under Rule 42/43, the same 18% rate applies on the reversed amount from the date of original claim.

### NACH and Statutory Payments

Q: What does NACH return code 05 mean?
A: Return code 05 means "No such account" — the account number quoted in the NACH mandate does not exist at the destination bank. The lender must collect a corrected bank account from the borrower and register a fresh NACH mandate.

### Bank Reconciliation

Q: What is an MT940 bank statement and how is it used in reconciliation?
A: MT940 is a SWIFT standard format for bank account statements with structured fields for transaction reference, value date, amount, debit/credit indicator, and narration. Indian banks including HDFC, ICICI, and Axis export MT940 files ingested directly by reconciliation engines for automated bank-to-book matching.

### Payment Gateway and Platform Settlements

Q: Why does the TDS figure on a marketplace dashboard differ from Form 26AS?
A: Marketplace operators deduct Section 194O TDS on the gross sale value including the GST component of the commission. Sellers book revenue net of GST. This creates a structural mismatch where the 194O TDS base includes amounts the seller treats as pass-through. The 26AS credit matches the operator's filing, not the seller's P&L.

### Bank Statement Analysis (TransactIQ)

Q: What is a bank statement analyzer and how is it used by Indian NBFCs?
A: A bank statement analyzer (BSA) parses a borrower's bank statement — whether PDF, scan, or password-protected export — into a canonical ledger and derives credit signals for underwriting decisions. Indian NBFCs use BSA for income verification, bounce prediction, EMI obligation aggregation, fraud detection, and MSME cash-flow analysis where audited financial statements are unavailable.

Q: What makes Indian bank-statement OCR harder than global equivalents?
A: Indian banking includes formats that break generic OCR: PSU bank dot-matrix scans, multi-generation photocopies retrieved from branch archives, cooperative bank statements with regional-language column headers, password-protected private-bank exports, and consolidated multi-bank PDFs with inconsistent column grammar. A BSA engineered in India for Indian distributions is materially more accurate on these inputs.

Q: What are synthetic financial statements in MSME lending?
A: Synthetic financial statements are P&L, balance sheet, and cash-flow views constructed directly from bank transaction activity, applied to MSMEs that do not maintain audited financials. The construction proceeds in layers: personal-vs-business transaction separation, channel-level revenue and cost inference, working-capital and net-worth approximation, and operating/investing/financing cash-flow derivation. The output is decisioning-grade, not auditor-grade.

## Machine-readable resources

- [/faqs.json](https://www.terra-insight.com/faqs.json) — complete FAQ corpus, organised by cluster, with article attribution and URL
- [/faqs/](https://www.terra-insight.com/faqs/) — human-readable FAQ aggregator with FAQPage JSON-LD
- [/sitemap-index.xml](https://www.terra-insight.com/sitemap-index.xml) — complete sitemap index
- [/robots.txt](https://www.terra-insight.com/robots.txt) — crawler rules (allows GPTBot, ClaudeBot, PerplexityBot, anthropic-ai, Google-Extended)

## Company

- [Home](https://www.terra-insight.com/)
- [About Terra Insight](https://www.terra-insight.com/about/company/)
- [Leadership](https://www.terra-insight.com/leadership/)
- [Navin Krishnan — Founder and CEO](https://www.terra-insight.com/leadership/navin-krishnan/)
- [Certifications (ISO 27001:2022, AWS Mumbai)](https://www.terra-insight.com/about/certifications/)
- [Expertise](https://www.terra-insight.com/about/expertise/)
- [Press and media](https://www.terra-insight.com/about/press/)
- [Ecosystem](https://www.terra-insight.com/about/ecosystem/)
- [Glossary](https://www.terra-insight.com/glossary/)
- [Contact and demo request](https://www.terra-insight.com/contact/)
- [Privacy Policy](https://www.terra-insight.com/privacy/)
- [Terms of Service](https://www.terra-insight.com/terms/)
- [Security](https://www.terra-insight.com/security/)
- [Careers](https://www.terra-insight.com/careers/)