Rupee-Dirham Settlement and the Currency Mismatch Hiding in Gulf Insurance Placements

India and the UAE built a local currency settlement (LCS) mechanism to let bilateral trade clear directly in rupee and dirham rather than routing through the US dollar. The framework sits on a July 2023 agreement signed alongside the India-UAE CEPA free-trade pact, reinforced by a 14 January 2025 RBI amendment to FEMA regulations that widened how authorised dealer banks and their overseas branches can open and operate rupee accounts for non-residents. The policy ambition is explicit: push bilateral trade toward the USD 100 billion CEPA target and cut dependence on the dollar leg.

Adoption, though, has lagged the trade growth. Public commentary through 2025 and into 2026 keeps repeating the same point: CEPA volumes have moved well, but the LCS share has not, held back by thin private-sector uptake, limited awareness among smaller exporters, and the practical friction of holding and pricing dirham or rupee balances. The result is a corridor where the trade increasingly settles in local currency for some counterparties while the insurance on that trade was bought, and is still booked, in dollars.

That split is the whole problem for a broker. A marine cargo or trade-credit policy is a promise to make the insured whole in a defined currency. When the underlying receivable shifts to dirham or rupee but the policy still indemnifies in dollars, the client carries an exchange-rate basis between the currency it actually loses and the currency the insurer actually pays. Nobody underwrote that gap on purpose. It arrives quietly, as a by-product of a treasury decision the insurance team was never copied on.

On any Gulf-corridor placement there are really three distinct currencies in play, and a clean programme keeps them aligned.

The first is the currency of the trade, meaning the currency in which the invoice, the receivable, or the goods value is actually denominated. Post-LCS, this might now be dirham for a UAE buyer or rupee for an Indian supplier that has agreed to invoice in INR.

The second is the currency of the sum insured, the figure written into the schedule against which loss is measured and the average clause is tested. This is usually dollars on Gulf accounts out of old habit and reinsurance convenience.

The third is the currency of settlement, meaning what the insurer hands over when the claim pays. The policy wording, not the client's expectation, decides this, and it may differ from the sum-insured currency through a conversion clause.

When all three agree, the indemnity is clean: the client loses dirham, the cover is sized in dirham, and the cheque arrives in dirham. When they diverge, the insured absorbs the difference between the rate on the day of loss and the rate on the day of payment, plus any conversion-date ambiguity in the wording. On a single shipment this is noise. On a stock-throughput programme, a marine open cover running hundreds of declarations, or a trade-credit policy with a large insured turnover, the accumulated basis becomes a real number that shows up as an under-recovery the client blames on the broker.

Why dollars stuck around

Dollar-denominated wordings persist because reinsurance treaties, facultative slips, and London or Singapore capacity all think in dollars, and because exporters historically invoiced in dollars anyway. LCS breaks that last assumption for part of the book without anyone re-papering the policy. The broker's job is to notice when a client's trade currency has drifted away from the schedule currency and to decide, deliberately, whether to follow it.

Marine cargo is where the mismatch shows up first, because the insured value tracks an invoice that treasury can change without telling anyone. Under most Institute Cargo Clauses placements the insured value is invoice cost plus freight plus a notional margin, and the policy pays against that value in the policy currency.

Consider an Indian exporter that historically invoiced its UAE distributor in dollars and now, to use the LCS rail, invoices in dirham. The open cover still reads in dollars. A total loss on a declared consignment is now a dirham receivable that the insurer settles by converting an originally dollar-stated sum insured at whatever conversion date the wording specifies. Between the loss date and the settlement date the dirham, which is pegged to the dollar, behaves predictably, so the exposure here is modest. The sharper exposure is on the rupee leg: where the trade or the receivable is in rupees and the cover pays dollars, the INR-USD move over a claim cycle of several weeks is unhedged and unbudgeted.

Stock throughput multiplies the issue. A throughput programme covers goods from supplier through transit, free-trade-warehousing storage, and onward movement under one limit. If parts of that flow now price in dirham or rupee while the policy limit and the average clause sit in dollars, a partial loss can trip the average calculation on a currency basis the client never modelled, shaving the recovery below the figure the CFO expected.

The practical move is to align the open cover currency to the dominant invoicing currency of the actual flow, or to split declarations by currency so each loss is measured in the money it was lost in.

Trade-credit and export-credit cover are even more currency-sensitive than cargo, because the entire insured value is a currency-denominated receivable. The policy indemnifies a percentage of an unpaid invoice after a buyer default or protracted default, and the insured loss is precisely the rupee or dirham the seller failed to collect.

If an Indian exporter to the UAE moves its invoicing to dirham under LCS but holds a dollar-denominated trade-credit policy, a default crystallises a dirham loss settled in dollars. Because the dirham is dollar-pegged, that specific pairing is relatively benign. The dangerous configuration is the reverse and the rupee leg: a receivable in rupees, or a buyer obligation that has been converted to rupees under the settlement mechanism, sitting under cover denominated in a foreign currency. There the insured percentage of an INR receivable gets paid in a currency that has drifted against the rupee since the credit period began, and the exporter under-recovers on the gap even though the policy paid out in full on its own terms.

ECGC and commercial trade-credit insurers can usually denominate the policy and the credit limit in the currency of the underlying contract. The discipline is to set the credit limit, the maximum liability, and the indemnity all in the same currency as the invoice the client will actually raise. Where a client runs a mixed book, some buyers in dollars, some now in dirham or rupee, the cleaner answer is currency-specific limits rather than one blended dollar limit that quietly mistranslates a chunk of the portfolio.

Brokers should also read the protracted-default waiting period against currency exposure. A default that pays after a long waiting period means the rate gap accrues over months, so a currency-matched policy is not a nicety on these accounts, it is the difference between a full and a partial recovery.

This is a wordings problem before it is a pricing problem, and a handful of clauses carry the whole load.

1. Policy currency definition. State the currency of the sum insured or credit limit explicitly and match it to the dominant invoicing currency of the insured flow. Do not let it default to dollars because the slip template did.
2. Currency conversion clause. Specify the conversion rate source (RBI reference rate, the settling bank's rate, or a named published rate) and, critically, the conversion date. Push for date-of-loss conversion on rupee-exposed accounts so the basis between loss and payment sits with the insurer.
3. Multi-currency declaration mechanism. On open covers and throughput, allow declarations in more than one currency so each consignment is insured in the money it trades in, with the limit expressed as an aggregate that the insurer and reinsurer can still track.
4. Average clause currency. Make explicit which currency the sum insured is tested in, because a currency mismatch can trigger under-insurance on conversion even when the client thought it was fully covered.
5. Claims-payment currency and account. Name the currency and, where LCS is in use, confirm the insurer can pay into the relevant SRVA-linked or local-currency arrangement without a forced dollar round-trip that re-imports the basis you just removed.

None of this needs heavy diagnosis up front. Ask the client's treasury function one question at renewal, namely which corridor flows have moved, or will move, to rupee-dirham settlement in the next twelve months, and that single answer tells you which policies need a currency review and which can stay in dollars.

None of this requires a new product. It requires the broker to treat currency of settlement as a placement variable with the same seriousness as limit, deductible, and territory, rather than as a back-office assumption.

The reason this gap exists is organisational, not technical. The decision to invoice a UAE buyer in dirham, or to route a payment through the LCS rail, is made by a treasury or finance team optimising for transaction cost and dollar independence. Commentary around the corridor notes exporters carrying transaction costs in the region of a couple of percent on conventional dollar routing, which is exactly the friction LCS is meant to remove. That is a treasury win. The insurance consequence travels in the opposite direction and lands on a different desk that was never consulted.

A broker who only ever talks to the risk or HR function will miss the currency switch entirely until a claim exposes it. The move is to insert one structured checkpoint: at every renewal on a Gulf-corridor account, confirm the currency of the underlying flow with whoever owns the invoicing decision, and reconcile it against the schedule currency. This is not heavy work. It is a single reconciliation that prevents an avoidable under-recovery.

There is also a positioning advantage here. Most brokers placing India-UAE marine and trade-credit business still write everything in dollars on autopilot. A broker who can walk a CFO through the three-currency alignment, show where the basis sits, and re-paper the wording to remove it is having a conversation a commodity placement broker cannot have. On the same corridor, this pairs naturally with the trade-credit and bancassurance work already flowing through the India-UAE relationship, so the currency review becomes a reason to revisit the whole programme rather than a standalone task.

The honest framing for the client is simple. LCS is a genuine cost saving on the trade. It is also a silent re-denomination of the loss that your insurance was sized to cover. Capture the saving, but match the cover to the new currency before a claim does the matching for you, at a worse rate and at your expense.

Translating the argument into desk practice, here is the sequence to run across every India-UAE account at the next renewal.

First, map the flow currency. For each insured trade lane, record the currency the invoice is actually raised in today, and flag any lane treasury intends to move to rupee-dirham settlement. This is the master fact everything else keys off.

Second, read the schedule against the map. Compare the policy currency, the sum insured or credit limit currency, and the claims-settlement currency to the flow currency. Any divergence on a rupee-exposed lane is a live basis risk to escalate.

Third, interrogate the conversion clause. Identify the rate source and the conversion date. If the wording fixes the rate at payment date rather than loss date, quantify the typical claim-cycle length and decide whether to negotiate a loss-date trigger.

Fourth, decide align-or-hedge. Either re-denominate the cover to the flow currency, split declarations by currency, or, where the cover must stay in dollars for capacity reasons, hand the residual basis back to treasury to hedge consciously rather than leaving it stranded on the policy.

Fifth, document the decision. Record in the placement file why the policy currency was chosen, so that if a basis loss does occur the broker has evidenced advice rather than an unexamined default. That record is the broker's own professional-indemnity protection as much as it is client service.

The corridor is going to keep migrating toward local-currency settlement, unevenly and over years rather than overnight. The placements that age well are the ones where the broker treated the currency of settlement as a deliberate choice from the start, not a number that got copied from last year's slip.