Why we bill in your currency, not ours (and what that costs us)

Invoicing every client in their own currency, USD, CAD, AUD, NZD, or GBP, sounds like a small courtesy from the outside. From the inside, it's a real operational decision that carries genuine cost and complexity for us, and we still do it as the default rather than the exception, because the alternative shifts a real cost onto clients who have no reason to absorb it.

We made this decision early, before it was fully clear how much it would cost us in a volatile currency year, and we've kept it in place since, on the theory that a policy you only honor when it's cheap isn't really a policy at all.

Every invoice denominated in a foreign currency exposes us to exchange rate movement between the invoice date and the day we actually convert the payment into rupees for local expenses. On a typical month, that swing is small. Across a full year of invoices, it's a real, non-trivial cost, and it's one we've deliberately chosen to carry rather than pass on as a line-item surcharge, which most clients would rightly find irritating on a fixed-price contract.

We track this cost internally as its own line in our own finances, specifically so it stays a known, managed number rather than an invisible drag on margin that nobody's actually watching. Treating it as a real, named cost is part of why we've been comfortable keeping the policy rather than quietly abandoning it.

Billing everyone in rupees would push the exchange rate risk onto the client instead, meaning their actual cost in their own currency would fluctuate month to month for reasons that have nothing to do with the work delivered. A CAD 5,000 monthly retainer that quietly becomes CAD 5,200 one month and CAD 4,850 the next, purely from currency movement, makes budgeting harder for a client's finance team for no real benefit to anyone.

We've talked to finance teams at prospective clients who specifically flagged this as a dealbreaker with a previous vendor, a retainer whose actual local-currency cost moved around enough from month to month that it complicated their own budgeting and forecasting in ways that had nothing to do with the value of the work.

We use forward contracts for larger, longer fixed-price engagements to lock in a conversion rate close to the invoice date, and we accept the float on smaller, shorter retainers where the exposure per invoice is small enough not to be worth hedging. It's not a perfect system, and a genuinely extreme currency swing could still hurt a specific quarter, but it's a manageable, bounded cost rather than an open-ended one.

We review this policy roughly annually against actual currency volatility over the previous year, adjusting the specific threshold at which we hedge versus accept the float, rather than treating it as a fixed rule set once and never revisited.

The one thing we do ask: pay on the agreed schedule. A payment delayed by six weeks during a period of currency volatility can turn a manageable exposure into a real loss, and it's the one variable in this whole arrangement that's genuinely in the client's control. Reliable payment timing is worth more to us than almost any other single term in a contract.

We say this directly to every new client during the proposal conversation, not because we expect payment problems, most clients pay reliably, but because being explicit about why timing matters here, not just as a generic contract term, tends to make the actual payment schedule easier to hold to on both sides.

The obvious alternative to absorbing exchange rate risk directly is quietly padding every quote by a few percent to cover the average expected currency movement across a year. We've deliberately avoided this, since it means clients in a stable currency year subsidize the cost of protecting against a volatile one, and it obscures the actual price of the work behind a hidden buffer nobody can see or question.

We'd rather quote the real cost of the work and treat currency exposure as a separate, visible business cost we manage on our own side, even though it would be operationally simpler to just build a small premium into every rate and call it done. Simpler isn't always more honest, and we've chosen the less simple option here on purpose.

A client's accounts payable team generally cares about exactly one thing regarding currency: does the invoice amount match what they budgeted, in their own currency, without a surprise. Billing in their currency means the number in their system matches the number we sent, every time, with no internal conversion step introducing its own possibility for error or confusion during a busy month-end close.

We've had finance contacts at client companies specifically thank us for this during a vendor onboarding process, since it's one fewer thing their own systems have to handle specially, and one fewer explanation needed when a foreign-currency line item shows up differently than expected on an internal report.

We've also found this small operational courtesy tends to correlate with longer client relationships, not because currency billing itself retains anyone, but because a vendor that's thought through this kind of unglamorous operational detail tends to have thought through the similarly unglamorous details elsewhere in the relationship too. It's a small, visible signal of a larger pattern.

Our current approach assumes a currency swing that's meaningful but bounded, the kind that costs real money over a year without threatening the business itself. If a specific currency moved sharply and persistently, well beyond the historical volatility our hedging thresholds are built around, we'd revisit the policy rather than absorb an open-ended loss on principle.

We've been explicit with long-term clients that this is a possibility, not a hidden condition buried in a contract, since a policy that quietly changes only when it's convenient for us isn't really the policy we're describing here. Any change would come with advance notice and a real conversation, not a surprise line item on an invoice.