Invoicing Guide
How to Invoice International Clients in Their Currency
8 min read · Updated September 2026
A US consultant billing a Munich operations team, or a freelance photographer invoicing a London magazine, often waits longer when the PDF says “USD 4,800” and the buyer has to convert before they can approve it. Invoicing in the client's currency puts a familiar number on the purchase order. It can cut disputes and speed payment. It also moves the conversion onto you. This guide is about that commercial choice. It is not a comparison of SWIFT versus local rails — that sits in the 2026 payments overview. CurrencyCentral does not issue invoices or collect funds.
Invoice currency is not the payment method
The invoice states what they owe and in which ISO code. The rail is how they send it. You can bill EUR 3,500 and still receive a SEPA credit, a SWIFT wire, or a card charge. Mixing those two decisions is how operators write “we invoice in euros” when they mean “we asked them to use our Wise details.” Keep them separate. This page is the bill. The other guide is the pipe.
Billing in the buyer's currency is also not a hedge by itself. You have created a foreign-currency receivable. Until it settles and you convert — or until you match it to a euro cost — the dollar value can move. That is transaction risk, described in the FX risk management explainer. If you already spend in that same currency, natural hedging can shrink how much you convert at all.
Why local-currency bills get paid faster
Accounts payable teams approve numbers they recognize. A euro invoice matches a euro budget line. A dollar invoice often needs a conversion estimate, a second approver, or a “we will pay when we see the USD equivalent” pause. Freelancers feel this as quiet delay. Marketplace sellers feel it when a European wholesale buyer asks for a EUR price list so their PO system can ingest it.
Disputes shrink when the face amount never changes. If you billed USD and the dollar strengthened, the buyer may claim they “overpaid” in local terms. If you billed their currency, the face amount is stable; the conversion is your problem on receipt. That is a trade: fewer arguments, more FX on your side. Write on the invoice who pays transfer charges so a correspondent deduction does not reopen the fee. What happens to the money on the way in — and when you convert the receipt — is getting paid without losing fees.
| Choice | Who converts | Typical friction |
|---|---|---|
| Invoice in USD | The client, on their side | Approval delay; disputes if their local cost moves |
| Invoice in their currency | You, when you convert the receipt | Faster PO match; you hold the receivable move |
| Dual display | Still one legal currency on the bill | A USD equivalent note can help; it is not a second amount due |
If the pair is EUR/USD, the operating notes in the USD vs EUR guide help you read the midpoint. They do not tell you which currency to print on the invoice.
Practical takeaway
Put one currency on the invoice, make the amount due unambiguous, and treat any second figure as a reference note. Then decide the rail separately.
Price the work, then pick the printed currency
Start from the dollar (or home-currency) price you need. Convert that to the client currency using a dated reference — a daily ECB midpoint from the CurrencyCentral converter— and write the local amount as the amount due. Record the midpoint and the date in your file so you can explain the quote later. Do not promise that the client's bank will convert at that same number if they somehow pay in dollars anyway.
Payment terms still matter. Net-30 on a foreign-currency invoice is thirty days of transaction risk. Shorten terms if the receivable is large relative to margin, or accept the move as a cost of winning the work. That is a screening question in 7 signs your business needs an FX risk strategy, not a reason to invent a “better rate” story.
An invoicing checklist
- One invoice currency; one amount due; who pays transfer charges.
- Optional USD equivalent labeled as reference only, with the midpoint date.
- Bank or payout details that can receive that currency without a surprise conversion.
- How you will convert the receipt — spot, match to a local cost, or a later dated decision.
- Rail choice after the invoice is agreed, using the payments-overview guide.
When you pay overseas contractors in their currency, you are on the other side of this choice. That flow is paying international contractors, not this page.
The bottom line
Invoicing in the client's currency is a sales and collections decision. It can reduce approval friction and arguments about the face amount. It does not lock a favorable market rate, and it is not the same as picking SWIFT or a local rail. Print one currency, record a reference midpoint when you price the work, and convert the receipt on purpose. For pair-level context, open today's top currency pairs. For how this site treats rates as information only, read About CurrencyCentral. More guides sit on the blog index.
Frequently asked questions
Why invoice a foreign client in their currency instead of USD?
The client can approve a familiar number without converting first. That often shortens the “I need to check the dollar amount” delay and reduces disputes about who was supposed to absorb the FX move. You then carry the conversion when the funds arrive.
Is invoicing in the client’s currency the same as choosing SWIFT or local rails?
No. Invoice currency is what the bill says they owe. The rail is how the money moves. A euro invoice can still arrive by SEPA, SWIFT, or a card checkout. Compare methods separately in the payments-overview guide.
Does billing in euros lock in a good exchange rate?
No. You are choosing who holds the move between invoice date and settlement. The converted dollar amount is unknown until you convert, unless you later use a dated instrument for a known receivable. That is planning, not a promised market outcome.
Does CurrencyCentral issue invoices or collect in foreign currency?
No. CurrencyCentral publishes educational explainers and daily ECB reference rates. It is not billing software, not a payment processor, and not a trading desk.