A US founder hires a Bengaluru contractor at USD 5,000 per month and pays in INR. At signing, USD 1 is INR 83. Twelve months in, USD 1 is INR 88. The contractor’s INR income has risen 6 percent without anyone touching the contract. The founder has paid USD 60,000 expecting USD 60,000 of work. Both sides feel they got the wrong end of the deal. Neither side did anything wrong. The contract just did not say what was supposed to happen.
This is what happens when a cross-border contract is silent on FX. Currency clauses are not glamorous, but they decide whether a multi-year contractor engagement creates or destroys margin for both sides. This guide walks through fixed-rate versus floating FX clauses, rate-setting at signature versus invoice versus payment, cap-and-floor mechanisms, who bears FX risk by default, and the difference between currency-of-record and currency-of-payment.
The three decisions in a multi-currency clause
Every multi-currency contract makes three decisions, explicitly or implicitly.
- Currency-of-record. The currency in which the obligation is denominated.
- Currency-of-payment. The currency actually transferred.
- Conversion mechanic. When and how the rate is set, and what reference rate is used.
Skip any of these and the default rules of the relevant jurisdiction kick in, almost always to one side’s disadvantage.
Currency-of-record vs currency-of-payment
These are independent decisions.
Currency-of-record
The currency the underlying obligation is denominated in. This is what matters for:
- Contract value calculations
- Accounting on both sides
- Tax reporting (the IRS reports payments to foreign contractors in USD on Form 1042-S where applicable, regardless of the actual currency of payment)
- Dispute resolution (an award denominated in USD is enforced in USD)
Currency-of-payment
The currency actually transferred. This is what matters for:
- Operational execution (the rails available, the cost of the transfer, the speed)
- The contractor’s local-currency income predictability
- Tax withholding in the contractor’s jurisdiction
Why they should usually differ
For a US client paying an Indian contractor:
- Record in USD because USD is the client’s functional currency and matches the underlying SOW value
- Pay in INR because the contractor lives in INR and operational rails (Skydo, wire transfer in INR, ACH-to-INR) are simpler when the receiver gets local currency
The contract states both clearly:
The Fees specified in this SOW are denominated in US Dollars. Client shall pay Contractor the INR equivalent of each invoiced amount, converted at the WM/Reuters 16:00 London Fixing on the Business Day immediately preceding the payment date.
This sets currency-of-record (USD), currency-of-payment (INR), and the conversion mechanic (WM/Reuters fix on T-1 of payment).
Fixed-rate vs floating-rate clauses
The core FX decision: lock the rate or let it float.
Fixed-rate clause
The contract fixes an exchange rate at signing for the life of the contract. The fee is then mechanically converted.
Conversion shall use the locked rate of INR 83.00 per USD 1.00 throughout the term of this SOW, regardless of subsequent rate movements.
Who bears the risk: Whoever is paying. If the rate moves to INR 88 and the contract is locked at 83, the client is sending more dollars to buy the INR than the spot rate requires. If the rate moves to INR 78, the client benefits.
When it fits:
- Short engagements (3 months or less)
- High-volume vendor relationships where the client has FX hedging at the corporate level and can offset
- Engagements with a USD denomination but local-currency-equivalent expectations
Failure modes:
- Over a 12-month engagement, currency movement can exceed 10 percent. Whoever was right at signing is wrong by mid-contract.
- It creates an incentive for one side to renegotiate when the rate moves against them.
Floating-rate clause
The conversion uses the spot rate at a defined moment.
Each payment shall be converted from USD to INR at the RBI reference rate published on the Business Day immediately preceding the payment date.
Who bears the risk: The contractor (in this example), because their INR income moves with the rate.
When it fits:
- Most cross-border contracts
- Engagements where both sides expect movement and want to track market reality
- Long engagements where locking a rate creates outsized risk
Failure modes:
- The contractor’s local-currency income is unpredictable, which can affect retention
- Sharp moves create month-to-month variance that complicates the contractor’s planning
Floating with cap-and-floor
The middle path. Float the rate within a corridor and adjust outside it.
The Fee is USD 5,000 per month, payable in INR at the RBI reference rate on the payment date. If the reference rate is outside the corridor of INR 80.00 to INR 88.00 per USD on three consecutive payment dates, the parties shall renegotiate the Fee within 30 days to restore the INR equivalent to within plus or minus 5 percent of the initial INR value at signing.
Who bears the risk: Both, within the corridor. Outside the corridor, the contract reopens.
When it fits:
- Engagements of 6 months or longer
- Pairs where one side is paying significant amounts and cannot absorb the variance alone
This is the most balanced structure for long-term cross-border contractor relationships. It is also the most drafting-heavy.
When the rate is set: signature, invoice, payment
Three options for when the conversion rate is fixed.
At signature
The rate at the date of signature applies throughout. This is a full fixed-rate clause, discussed above.
At invoice
The rate at the invoice date applies. Used in some Net-30 structures.
Each invoice shall be denominated in USD with an INR-equivalent calculated at the RBI reference rate published on the invoice date.
Issue: If payment is delayed (Net-30 actual takes 45 days), the rate at payment time differs from the rate locked at invoice. Either the contractor gets a windfall or absorbs a loss for the client’s delay.
At payment
The rate at the payment date applies. This is the default modern structure.
Each payment shall be converted at the WM/Reuters 16:00 London Fixing on the Business Day immediately preceding the payment date.
This aligns the conversion with the actual cash event and avoids any disputes about timing. It is also the structure that most international banking rails use as their reference (https://www.ecb.europa.eu/stats/pdf/exchange/Frameworkfortheeuroforeignexchangereferencerates.en.pdf).
Which reference rate to name
The rate you name in the contract is not the rate your bank gives you. Banks add markup. The reference rate is the market quote, and naming it puts you closer to the real market.
ECB euro reference rates
Published by the European Central Bank at approximately 16:00 CET each Target trading day. Used for EUR-denominated obligations. Free, transparent, official (https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html).
WM/Reuters Fixing
The global benchmark for cross-currency conversion. Published at 16:00 London time. Used by most multinational corporate treasuries. Reliable for nearly any currency pair.
Central bank reference rates
Each major central bank publishes its own reference rate. RBI publishes the INR reference rate at approximately 13:30 IST. Bank of England publishes daily spot rates for GBP pairs. Use these for jurisdiction-specific obligations or where local-law accounting or tax requires.
What to avoid
Aggregator quotes (Google Finance, XE.com, OANDA retail) include retail markup and lack the legal precision a contract clause needs. Bank quotes from the paying bank are subject to the bank’s own margin. Name a published benchmark in the contract.
FX risk allocation by default
If the contract names a single currency for payment, the party not in that currency bears the conversion risk. Silence is not neutral.
Sample defaults
| Contract says | Client | Contractor | FX risk falls on |
|---|---|---|---|
| Pay USD 5,000 per month | US | India | Contractor (INR conversion at their end) |
| Pay INR 4,15,000 per month | US | India | Client (USD to INR each month) |
| Pay USD 5,000 per month in INR at spot | US | India | Contractor (INR amount varies monthly) |
| Pay USD 5,000 per month in INR at locked rate | US | India | Client (locked rate, USD cost varies) |
Pick the allocation explicitly. Do not let a one-line payment clause make the choice for you.
Cap-and-floor mechanics
A working cap-and-floor clause has five elements:
- A base rate at signing (e.g., INR 83.00 per USD on the date of this SOW)
- A corridor around the base rate (e.g., INR 80.00 to INR 88.00, or plus or minus 5 percent)
- A trigger for renegotiation (e.g., the reference rate falls outside the corridor on three consecutive payment dates)
- A target for the adjustment (e.g., restore the contractor’s INR-equivalent to within plus or minus 5 percent of the initial value)
- A timeline for the renegotiation (e.g., within 30 days, with continued payment at the most recent rate during negotiation)
Sample full clause
Currency and FX. The Fees in this SOW are denominated in US Dollars (USD). Client shall pay Contractor the INR equivalent of each invoiced amount, converted at the RBI Reference Rate published on the Business Day immediately preceding the payment date.
Reference rate at signing: INR 83.00 per USD 1.00.
Corridor: INR 80.00 to INR 88.00 per USD.
Trigger: If the RBI Reference Rate falls outside the Corridor on three consecutive payment dates, either party may invoke renegotiation by written notice.
Adjustment: Upon invocation, the parties shall negotiate in good faith within 30 days to restore the INR-equivalent monthly Fee to within plus or minus 5 percent of the initial value of INR 4,15,000. During the negotiation period, Client shall continue payments at the most recent agreed amount.
Source. All references to the RBI Reference Rate mean the rate published by the Reserve Bank of India at approximately 13:30 IST on the relevant date. If the RBI Reference Rate is not published on a relevant date, the parties shall use the next published rate.
This clause does five things: it sets currency-of-record (USD) and currency-of-payment (INR), names a published reference rate (RBI), defines a corridor, sets a trigger and adjustment mechanic, and handles non-publication dates.
Payment timing and FX
When the contract says “Net-30” and pays in a foreign currency, two FX questions appear.
Locking the rate at invoice
Some contracts let the contractor invoice in USD at the invoice-date rate and require the client to settle the INR amount calculated at invoice. This protects the contractor against rate movement during the Net-30 float but transfers the float risk to the client.
Locking the rate at payment
The dominant modern pattern is to convert at the payment date. The contractor bears the float risk in exchange for a clean operational rule. This is what most cross-border payment platforms default to.
Best practice for long engagements
For monthly retainers over a 12-month engagement, the payment-date conversion with a cap-and-floor corridor is the most stable structure. It tracks the market month-to-month, prevents either side from being trapped by stale rates, and triggers renegotiation only when movement is meaningful.
How Omnivoo handles multi-currency
Omnivoo’s Contract Management product ships templates with the dual currency-of-record and currency-of-payment structure, named reference rates by jurisdiction (RBI for INR, ECB for EUR, BoE for GBP, WM/Reuters as a global fallback), and optional cap-and-floor corridors. For Indian contractor relationships, the platform integrates with Skydo bank transfers that use the RBI reference rate as the conversion benchmark.
For payment-timing structures that sit on top of these FX clauses, see payment terms in contractor contracts. For SOW structure where these clauses live, see drafting a SOW for US companies hiring global contractors. The Contract Management product handles the full contract lifecycle including FX conversion at payment.
Drafting checklist
- Does the contract specify currency-of-record and currency-of-payment separately
- Is the conversion mechanic named (fixed-rate, at invoice, at payment)
- Is the reference rate named with full specificity (e.g., “RBI Reference Rate at 13:30 IST”)
- Is there a fallback for non-publication dates
- Is FX risk allocation explicit, not implicit in the choice of payment currency
- For engagements over 6 months: is there a cap-and-floor or renegotiation trigger
- Does the payment-timing clause clarify whether conversion happens at invoice or payment
- Is the contract value computable in both currencies at any given date
If you remember three things
- Currency-of-record and currency-of-payment are separate decisions. Set both explicitly.
- The reference rate you name matters more than the conversion math. ECB, RBI, and WM/Reuters are credible and free. Bank quotes are not.
- Over a 6-month-plus engagement, cap-and-floor with a renegotiation trigger is more robust than fixed or pure floating. It rewards drafting effort with stable cashflow on both sides.
FX risk does not disappear because the contract is silent. It just defaults to whoever has to do the conversion. Pick the allocation explicitly at signing and the relationship will outlast the next currency cycle.