How should you price when your buyer pays in another currency?

How should you price when your buyer pays in another currency?

Quote in the currency your buyer makes decisions in, and decide deliberately who carries the exchange rate risk. Those are two separate choices, and most people accidentally make the second one by not thinking about it. The invoice is where that inattention shows up, months later.

I sell from Bengaluru, mostly to buyers outside India, on fixed fees. That means every project involves a currency decision before it involves a scope decision, and I got it wrong often enough early on to have opinions about it now.

This is not a tax or accounting article, and I am not your accountant. It is about the commercial decision: what number you put in front of a buyer, in which currency, and what happens between that moment and the money landing.

Should you quote in your currency or theirs?

Theirs, in almost every case. A buyer evaluating a proposal is comparing your price against budgets, salaries and competitors denominated in their own currency. If they have to convert your number to understand it, you have added friction to the exact moment you wanted to be frictionless.

There is a positioning cost too, and it is larger than the arithmetic. A price quoted in an unfamiliar currency reads as foreign, and foreign reads as risky to a buyer who is already wondering about time zones and contracts. Quoting in their currency removes an objection you never hear spoken aloud.

The exception is when your buyer genuinely operates in your currency, or when regulation or your accounting makes it impractical. Then quote in yours and state it plainly rather than half-converting. What you must never do is show a number without saying which currency it is, which happens more often than you would believe. I publish my prices for related reasons, and I have written about why I publish my pricing as a solo consultant.

What does the payment processor actually do with the conversion?

By default it converts everything into one currency, yours. Stripe's documentation states that Stripe automatically converts all incoming funds into your default currency. That default is doing something to every cross-border payment you take, whether or not you have looked at it.

You can change that arrangement. Stripe's documentation describes multi-currency settlement, where you configure your account to accrue balances and get paid out in up to 18 supported currencies, in order to pay suppliers, process refunds and avoid FX fees. Avoiding conversion entirely is the cleanest answer when it is available to you.

It comes with mechanics worth knowing before you plan around it. To accrue a balance in a given currency you must first accept payments in that currency, which Stripe calls presentment. You must also provide a separate supported bank account for each settlement currency, matching the bank account currency to the settlement currency. And you cannot pay out until your balance for that currency meets the minimum payout amount.

Why does where you are registered change your options?

Because these features are not global, and this is the part that catches founders outside the largest markets. Stripe's multi-currency settlement page lists its availability as AE, AU, CH, EU, GB, HK, LI, NO, SG and US. India does not appear on that list.

I mention that specifically because it is my own situation, and because advice written from inside the United States or the European Union tends to assume a menu that is not on the table everywhere. If you are selling internationally from a country that is not on a vendor's availability list, the clever multi-currency setup you read about is simply not an option for you.

So check availability for your own jurisdiction before you design a pricing strategy around a feature. Then build the strategy that works with what you actually have, which is usually a single settlement currency and a conversion happening on every payment. That constraint is workable. Pretending it is not there is what costs money.

Who should absorb the exchange rate risk?

Whoever can absorb it without renegotiating, which on a small project is you and on a long project should be shared. The mistake is leaving it unassigned, because then it defaults to whoever notices last, and on a fixed fee that is always the person doing the work.

The exposure is a function of time rather than size. A project quoted and paid within three weeks carries little risk, because rates rarely move far in three weeks. A retainer priced once and invoiced monthly for a year carries real exposure, and the person who set that price twelve months ago is the one paying for the drift.

My own rule is to accept the risk on anything short and to revisit the number on anything that renews. Not to hedge, not to add a currency clause with formulae in it, just to reprice at renewal like an adult. Complexity in a small contract costs more in confusion than it saves in exchange rates.

Should you charge the same number in every market?

No, and converting one number at today's rate is not pricing, it is arithmetic. What a buyer will pay for the same outcome differs by market because their budgets, alternatives and expectations differ. Converting your home price into their currency imports your market's assumptions about value.

This cuts both ways and the direction surprises people. Sometimes the converted number is far below what that market pays, and you have quietly underpriced yourself into looking cheap, which is its own objection. Sometimes it is above what the market bears and you never hear back, with no way to tell price from fit.

What I do instead is set a price per market in round local numbers and sanity-check it against my own floor. Round numbers matter more than exactness here, because a price like 4,850 reads as a conversion and invites the buyer to wonder about the rate. A round number reads as a decision. If you are showing prices on a site, the mechanics of that are worth getting right, and I have covered the currency switcher on a global pricing page separately.

What should a fixed-fee quote say about currency?

Three things, in one sentence each. The currency, stated explicitly with the code rather than just a symbol. How long the quote is valid. And who pays any transfer or conversion charges on the way. Leave any of the three out and you will be discussing it later at a worse moment.

The symbol problem is real and avoidable. A dollar sign means something different in several countries, and a buyer who assumes the cheaper reading of your number will feel misled when the invoice arrives, even though you both saw the same character. Write the code. It costs three letters.

Validity is the one people find awkward and it is the one that protects you. A quote that is good for thirty days is not aggressive, it is normal, and it gives you a clean reason to reprice if the rate has moved by the time someone comes back four months later. Most projects I do are fixed fee, between $1,000 and $10,000, and these clauses are why I can hold that price honestly. I have written about what I put in a fixed-fee proposal in more detail.

How do you stop small losses from accumulating?

By looking at what actually landed rather than what you invoiced. Reconcile one real payment end to end, from the number on the quote to the number in your bank, and find out what the gap is. Almost nobody does this, and it is the only way to know your real rate.

The gap is rarely one charge. It is a conversion somewhere, a transfer fee somewhere else, possibly an intermediary bank taking a slice you were never told about. None of the individual pieces look big enough to investigate, which is precisely why they survive for years. One reconciliation tells you more than any amount of comparing published rates.

Timing is worth watching too. Stripe's documentation notes that it charges the applicable fee when funds settle into a non-primary settlement currency, rather than when you initiate a payout. Fees attaching at settlement rather than payout is the sort of detail that makes your own arithmetic disagree with your statement, so read your provider's current pricing table rather than assuming.

What should you do next?

Take your last international invoice and trace it. Write down what you quoted, what the buyer paid, and what arrived in your account. If you cannot explain the difference between the second and third numbers, that is the work, and it takes one afternoon to fix permanently.

Then do the two decisions this article separates. Pick the currency you will quote in per market, in round numbers you chose rather than converted. And decide in writing who carries the rate risk on anything that renews. Both decisions are cheap to make now and expensive to discover later.

Selling from India to buyers elsewhere over 6+ years and 25+ clients, the currency question turned out to be a commercial decision rather than a finance one, and I wish someone had told me that before I spent a year converting my rate card at whatever today's number was. If you are about to price your first overseas project, reach out and let's get the quote worded properly the first time.