Multi-currency invoicing: how to invoice in any currency without losing money on the FX

Sending your first invoice in a foreign currency costs the average freelancer 2-4% of the invoice value in hidden FX fees — money lost to card-network markups, bad exchange rates, and intermediary bank charges that nobody told them about. This guide explains how multi-currency invoicing actually works, where the fees hide, and the cleanest way to send invoices in USD, EUR, GBP, or AUD without leaking margin.

What is multi-currency invoicing?

Multi-currency invoicing means issuing an invoice in a currency other than your home currency. A UK freelancer can invoice a US client in dollars; a German agency can bill a French client in euros; an Australian designer can quote in pounds. The invoice itself shows the foreign currency, the client pays in that currency, and you receive the funds (after FX) in your own bank account.

There are three things that have to be true for multi-currency invoicing to work in practice:

• Your invoicing software must let you pick the currency per invoice (not just per account).
• Your payment processor must accept the foreign currency from the client without forcing them to convert first.
• Either you or your payment processor must handle the FX conversion into your home currency, at a rate you understand.

The three fee layers nobody talks about

When you invoice in a foreign currency, the headline rate you see on Google ("1 USD = 0.79 GBP") is the mid-market rate — the real rate banks use to trade with each other. What you actually get is the mid-market rate minus three separate fees, applied in sequence:

1. Card-network FX markup (1-3%): when the client pays by card, Visa/Mastercard apply their own FX rate, which is typically 1-3% worse than mid-market. This is automatic and hidden in the card statement as a "currency conversion fee."
2. Payment-processor FX margin (0.5-1.5%): PayPal, Wise, and traditional banks all add their own margin on top of the card-network rate. Stripe is one of the few processors that uses the card-network rate with no extra markup.
3. Bank receiving fees (£5-£15 per wire): if the client pays by international bank transfer, your bank will likely charge a "receiving fee" and may apply a third FX rate at the worst possible moment.

The two clean approaches that work

After watching 200+ freelancers fumble with this, there are really only two setups that work without losing meaningful money:

Approach A: Card payments via a no-markup processor

The client pays by card in their currency. The card network converts to your currency at the wholesale rate. You receive your home currency, minus the standard card-processing fee (2.9% + 30¢ for international cards on Stripe). The total cost is the card-processing fee plus a small currency-conversion margin baked into the card-network rate — usually under 1% on top of mid-market.

This is the cheapest, fastest path for invoices under $5,000. Above that, the card-processing fee starts to bite.

Approach B: Bank transfer in the client's currency

You open a multi-currency account (Wise, Revolut, or a bank like HSBC with a USD/EUR account), invoice the client in their currency, and they pay by local bank transfer. The FX happens at your account level, on your schedule, at the mid-market rate plus a small margin (Wise charges 0.4-1.5% depending on currency).

This is the cheapest path for invoices over $5,000, because the per-invoice cost is near zero. The trade-off is the client has to initiate a bank transfer manually, which adds 1-2 days to the payment timeline.

What to put on the invoice itself

Beyond the obvious line items, a multi-currency invoice needs four details a single-currency invoice can skip:

• Currency code in every monetary field (e.g. "USD 1,000.00" not "$1,000.00") so there is zero ambiguity if the invoice is opened on a device with different locale settings.
• The client's VAT / tax ID, if they provided one. Many EU B2B clients need this on the invoice for their own tax reporting.
• A clear payment-terms line in both currencies where useful, e.g. "Due in 30 days. Late fee: USD 25 / EUR 23 per week."
• A bank-details block (or card-payment link) in the same currency as the totals. Never make the client convert before paying.

How Invosi handles multi-currency

Invosi supports invoicing in four currencies: USD, EUR, GBP, and AUD. You pick the currency per invoice (not per account), and the system handles the rest:

• Per-invoice currency — switch between USD/EUR/GBP/AUD on any invoice without changing your account settings.
• Stripe card payments — your client pays in the invoice currency; you receive USD; Stripe handles the FX at the wholesale rate with no Invosi markup.
• Bank transfer (no fees) — your IBAN / sort code / routing number appears in the client's currency, they pay locally, no FX happens at payment time.
• Localised display — UK visitors see £, EU visitors see €, AU visitors see A$. The pricing page and invoices adapt without you doing anything.

Starter is $7/mo, Pro is $12/mo, Scale is $25/mo — all USD. Your card network handles the FX at checkout. Invosi does not add a margin on top, and there are no per-invoice fees.

Compare how Invosi stacks up against the other multi-currency options in our /vs hub — most of the competitors charge per-invoice fees (Stripe Invoicing is 0.4% per paid invoice, FreshBooks is per-user pricing that adds up fast) or gate multi-currency behind a premium tier.

Written by Charlotte West.