Skip to main content
Economy & PolicyHigh impact

DGFT broadens rupee export settlement: what Notification 30/2026-27 changes

The FTP amendment reduces a practical gap between rupee settlement and export-policy benefits. The reform is meaningful for invoicing and compliance, but it does not by itself create international demand for the rupee.

Finin2min editorial illustration for DGFT broadens rupee export settlement: what Notification 30/2026-27 changes
Finin2min original editorial illustration
Effective from20 Aug 2026
Financial year2026-27
ProvisionsFTP 2023 Paras 2.52 and 2.53

What changed

DGFT issued Notification No. 30/2026-27 on Aug 20, amending FTP 2023 paras 2.52 and 2.53.

Why it matters

The FTP amendment reduces a practical gap between rupee settlement and export-policy benefits. The reform is meaningful for invoicing and compliance, but it does not by itself create international demand for the rupee.

Who is affected

Exporters, importers, banks, MSMEs, EPCG/authorisation holders and treasury teams.

Action required

Review Notification 30/2026-27 and banking documentation before changing invoice or settlement currency.

What changed

The Directorate General of Foreign Trade issued **Notification No. 30/2026-27 dated August 20, 2026**, amending paragraphs 2.52 and 2.53 of the Foreign Trade Policy 2023. The practical objective is to make rupee-denominated trade settlement fit more cleanly into India’s export-policy framework.

Reuters reports that export contracts and invoices with countries outside the Asian Clearing Union framework can be denominated and settled in Indian rupees or freely convertible foreign currency, subject to the applicable banking rules. Eligible export proceeds realised in rupees can also be recognised for Foreign Trade Policy benefits and obligations, with special treatment continuing for Nepal and Bhutan.

For exporters, this is important because settlement currency and policy eligibility must work together. A company has little incentive to accept rupee payment if doing so creates uncertainty over whether the receipt counts toward export obligations or incentive schemes.

Why this matters beyond currency symbolism

The internationalisation of the rupee is sometimes discussed as if it were primarily about geopolitical prestige. For a business, the decision is more practical: which currency reduces conversion cost, improves working-capital predictability, limits sanctions or correspondent-banking friction and allows both counterparties to manage risk?

The DGFT change addresses one part of that stack by aligning trade-policy treatment with rupee settlement. It can make rupee invoicing more operationally credible for exporters that already have counterparties willing to settle in INR.

But regulation cannot create two-way demand on its own. Overseas buyers need access to rupee liquidity; banks need workable correspondent or special-account arrangements; hedging markets must be usable; and exporters need confidence that accumulated rupee balances can be deployed or converted efficiently.

What exporters should check

A company should not change invoice currency simply because the policy permits it. Treasury and compliance teams should review four layers.

**Contract currency:** The sales contract, commercial invoice and payment terms should be consistent.

**Banking channel:** The receipt must move through an authorised mechanism accepted under FEMA and RBI directions.

**FTP linkage:** Where the exporter is relying on an authorisation, benefit or export-obligation discharge, documentation should clearly demonstrate that the rupee receipt qualifies.

**Hedging economics:** An INR invoice shifts currency risk between buyer and seller. The economically cheaper currency depends on each party’s funding and hedge access.

Impact on MSMEs

Smaller exporters can benefit disproportionately if rupee settlement reduces conversion charges or correspondent-banking friction. But they can also be hurt disproportionately by unclear bank documentation. This is why the rule change should be read alongside the RBI’s broader push for more transparent retail and small-business FX service.

An MSME should ask its bank for a written checklist covering account structure, permitted remittance route, documentation, charges, expected settlement time and the evidence required for export realisation.

Macro impact

More rupee settlement can reduce marginal demand for hard currency in specific trade corridors, but it would be misleading to claim that one FTP notification will materially change the rupee’s exchange rate. India’s aggregate currency dynamics remain dominated by the trade balance, oil imports, capital flows, global rates and investor risk appetite.

The long-term value is optionality: more transactions can settle in INR where both parties find it efficient, without losing access to domestic export-policy recognition.

Finin2min bottom line

Notification 30/2026-27 is a useful **plumbing reform**. It removes a policy mismatch that could discourage exporters from accepting rupee payments. The next test is operational—bank processes, documentation and counterparty demand. Exporters should use the route where it lowers total transaction risk and cost, not because rupee settlement is automatically superior in every trade corridor.

Accounting and control implications

Finance teams should update more than the invoice template. ERP currency fields, export-realisation evidence, bank-reconciliation procedures, hedging documentation and internal approval matrices may all need to reflect the chosen settlement route. Where export incentives or authorisation obligations are material, the evidence trail should be strong enough to survive a later DGFT or bank review.

The strongest use case is likely where both buyer and seller already have natural rupee needs. Where the overseas counterparty ultimately has to buy rupees in an illiquid market, the FX cost may simply move to the other side of the contract and return through pricing. Settlement-currency reform improves flexibility; commercial economics still decide adoption.

Primary source DGFT + Reuters · DGFT Notification No. 30/2026-27 dated 20 Aug 2026; Reuters context. · issued 20 Aug 2026
View official source →

FinNews is educational and professional reference material, not financial, tax or legal advice. Confirm the current official position from the primary source before acting on any figure, rate, provision or deadline mentioned here.