The Central Board of Direct Taxes (CBDT) Section 206C(1G) of the Income Tax Act 1961 governs Tax Collection at Source (TCS) on overseas remittances under the Liberalised Remittance Scheme (LRS). The Budget 2025 amendments effective from April 1 2026 raised the threshold from ₹7 lakh to ₹10 lakh per financial year and reduced the rate to 2% on health and education remittances (from earlier 5%). Authorized Dealer (AD) banks — HDFC, ICICI, SBI, Axis, IDFC FIRST, Kotak, IndusInd, Yes Bank, and others — implement the framework through specific operational procedures that combine threshold tracking, rate determination, real-time TCS calculation, statutory reporting via Form 27Q, and customer-side certificates via Form 27D. The compounded operational complexity affects both the bank's internal systems and the customer's documentation experience. Understanding the implementation procedure helps customers verify their TCS treatment, reconcile their Income Tax Return claims, and identify any discrepancies in bank-side processing.

This piece walks through the Section 206C(1G) procedural specifics, the bank-side implementation workflow, the customer-side documentation, and three reads on what the FY 2026-27 implementation reveals about Indian forex tax administration.

The Section 206C(1G) Procedural Specifics

The framework operates through several procedural elements:

Element 1 — Threshold definition: ₹10 lakh aggregated remittance per Financial Year per PAN-holder, across all AD banks. Threshold is per individual (per PAN), not per bank.

Element 2 — Rate determination: 0% TCS up to ₹10 lakh threshold. Above threshold: 5% on amount exceeding (general LRS purposes), 2% (health and education), 0.5% (education with loan via authorized financial institution).

Element 3 — Aggregation tracking: AD banks query a central PAN-linked aggregation database (or rely on customer self-declaration plus their own records) to determine if customer has crossed threshold across all banks.

Element 4 — Customer self-declaration: customer must self-declare LRS purpose at remittance time. Banks verify against permitted purposes; misdeclaration carries penalty exposure.

Element 5 — Statutory reporting: AD banks file quarterly Form 27Q with Income Tax Department reporting TCS collected, customer PAN, transaction details. Form 27D issued to customer as TCS certificate.

Element 6 — Income Tax claim: customer claims TCS as advance tax in Income Tax Return (typically July-October post-FY-end). TCS reduces final income tax liability.

The Bank-Side Implementation Workflow

When a customer initiates an LRS remittance through a digital banking platform or branch:

StepBank ActionCustomer Visibility
1Receive remittance request with purpose categorizationCustomer enters purpose in app/form
2Verify customer KYC and PANReal-time API call to UIDAI and PAN database
3Query annual aggregation tracking systemInternal bank query
4Determine threshold status (under/over ₹10 lakh)Internal calculation
5Apply appropriate TCS rateTCS deducted from remittance amount
6Process remittance via SWIFT or correspondent bank networkCustomer receives confirmation
7Record transaction in TCS registerInternal record
8Generate Form 27D certificateCustomer-facing certificate available
9File quarterly Form 27Q with Income Tax DeptStatutory reporting
10Update annual aggregation trackingInternal

The complete cycle from customer request to TCS deduction and remittance completion typically runs 1-3 business days for digital channels and 3-7 business days for branch-initiated transactions. Major banks (HDFC, ICICI, SBI) maintain integrated systems that automate steps 3-9 substantially, reducing manual error.

The Customer-Side Documentation

The customer's documentation responsibilities under the framework:

Pre-remittance: customer must have valid PAN, valid KYC at the AD bank, and clearly identifiable LRS purpose. Education remittances may require proof of admission/enrollment; health remittances may require medical documentation; investment remittances may require investment account details.

At remittance: customer self-declares purpose, confirms understanding of TCS implications, and provides supporting documentation as required by the bank.

Post-remittance: customer should download/preserve Form 27D TCS certificate from bank's digital banking platform. Certificate documents TCS collected and is used in Income Tax filing.

Annual ITR filing: customer claims aggregate TCS (across all banks for that FY) as advance tax in the Income Tax Return. The TCS reduces final tax liability dollar-for-dollar (TCS amount deducted from final tax due).

Refund scenario: if customer's TCS exceeds final income tax liability, the excess is refunded by Income Tax Department within typical processing timelines (3-12 months post ITR filing).

How the Section 206C(1G) Framework Compares Internationally

Country / FrameworkWithholding MechanismThresholdRate
India (Section 206C(1G))TCS on outbound LRS₹10 lakh per FY5% general / 2% health-edu
Brazil (IOF tax on FX)IOF on foreign exchange purchaseNo threshold0.38% (pessoa física basic)
Mexico (ISR on foreign income)Income tax (not TCS)VariableMarginal rates
Argentina (capital control)Multiple taxes/restrictionsVariableHistorically high
China (SAFE)$50,000 cap, no withholding$50,000 annual0% within cap
EU (no equivalent)Free flow within EurozoneN/AN/A
US (no outbound withholding)Income tax on foreign earningsN/AMarginal rates

India's TCS mechanism is administratively unique; most countries use either income tax integration (US, Mexico) or transaction taxes (Brazil IOF) rather than the TCS-and-claim model India uses. The TCS framework provides revenue advance to government while leaving final liability to be calculated at year-end.

What the FY 2026-27 Implementation Reveals

First, the framework's operational complexity affects every LRS user. The threshold tracking, rate determination, and statutory reporting create a layered process that requires bank-side automation and customer-side documentation. Errors at any step can produce incorrect TCS or claim discrepancies.

Second, the framework's revenue impact is meaningful. CBDT's TCS collection on LRS remittances reaches ₹10,000 crore+ annually based on Q1 2026 trends. The collection serves both revenue purposes and compliance signaling.

Third, the framework specifically distinguishes permissible LRS purposes from prohibited (margin trading) — but the TCS mechanism itself doesn't prevent prohibited remittance attempts. FEMA framework prohibits margin trading; the TCS framework taxes permitted remittances. The two frameworks operate independently.

What This Desk Tracks Through FY 2026-27

For Section 206C(1G) operational rollout, three datapoints define the trajectory.

First, ITR filing patterns for FY 2026-27 (July 2027 due date). Whether TCS claims process smoothly through Income Tax Department systems will indicate the framework's full-cycle effectiveness.

Second, possible additional CBDT clarifications. CBDT periodically issues clarifications on edge cases (purpose recategorization, education-loan alignment, multi-bank aggregation issues). Watch for circulars during 2026-27.

Third, CBDT consultation on possible further changes. Future Budget cycles may further adjust the framework. Industry stakeholder representations on operational concerns may produce 2027 Budget changes.

Honest Limits

Specific implementation details may vary by AD bank; customers should verify with their primary banking relationship. Tax advice on specific transactions or claims requires consultation with qualified Chartered Accountants. This piece is not tax or legal advice.

Sources