How to Invoice International Clients in Multiple Currencies

Published October 9, 2026

If you bill clients outside your home country — as a freelance designer, developer, consultant, or small agency — currency isn't a side detail on an invoice. It's one of the first things a client checks, and getting it wrong (the wrong symbol, an unclear code, a format they don't recognize) is a small but real source of friction and payment delay. This guide walks through a practical workflow for invoicing international clients in the currency they actually expect, and explains why keeping that process offline and on-device matters once you're dealing with clients across different countries and accounting systems.

Why currency choice matters more than it seems

A client in London expects GBP. A client in Manila expects PHP, or sometimes USD if that's how your contract was negotiated. A client in Tokyo expects JPY, formatted without decimal places the way yen typically is. None of this is exotic — it's just the baseline expectation of someone receiving a bill in their own country. Sending a US-freelancer-style invoice with a bare dollar sign to a client who bills and reports in euros creates ambiguity: is that USD or a local dollar-denominated currency like AUD or CAD? Ambiguity on an invoice is exactly the kind of thing that gets a payment held up while someone in accounts payable asks a clarifying question.

The fix isn't complicated: pick the currency the client actually invoices and pays in, label it clearly with its currency code (not just a symbol), and keep that consistent across every invoice you send that client. The harder part is doing that for ten or twenty clients across different countries without rebuilding your invoice format for each one.

A practical workflow for multi-currency invoicing

Confirm the billing currency when you onboard the client, not when the first invoice is due. Ask directly: "What currency should invoices be issued in?" Many clients have a standard answer tied to their own accounting setup.
Set that currency once per client record, rather than re-selecting it on every invoice. If your tool lets you save a default currency per client, use it — it removes a step you'd otherwise repeat every billing cycle.
Use the currency code, not just the symbol, somewhere on the invoice. "$" is ambiguous across USD, CAD, AUD, SGD, MXN, and others. "USD $1,200.00" is not.
Keep line-item amounts in that one currency for the whole invoice. Mixing currencies on a single invoice (e.g., listing some line items in USD and others in EUR) is a common source of confusion and should be avoided — issue separate invoices per currency if a client is somehow billed in more than one.
Export to PDF before sending, so the formatting — currency symbol, decimal places, alignment — is locked in and won't shift depending on what software the client opens it with.

What "100+ currencies" actually means in practice

Invoice Template includes a built-in list of more than 100 currencies — 138 at last count, covering major and regional currencies from USD, EUR, and GBP to JPY, INR, PHP, IDR, VND, AED, and dozens more. Picking a currency for an invoice sets the currency code and symbol used throughout that invoice and updates the formatting accordingly, and you can save a different default currency per client so you're not re-selecting it each time you bill the same person.

What it doesn't do: Invoice Template does not perform automatic currency conversion or pull live exchange rates. It lets you issue an invoice in the currency you choose and displays amounts correctly formatted in that currency — it does not convert an amount from one currency to another for you. If you're quoting a client in EUR but need to know what that equals in your own home currency, that's a separate step you'd handle with a currency converter or your accounting software, not something built into the invoice itself. We'd rather say that plainly than imply a conversion feature that isn't there.

Why offline, on-device billing matters across jurisdictions

Once you're invoicing clients in multiple countries, you're also implicitly handling data that touches multiple accounting and privacy jurisdictions — a UK client's billing address, an EU client's company registration details, a client in a country with its own data-residency expectations. Many cloud-based invoicing tools store that information in a database hosted in one specific country, under that provider's terms, regardless of where your client is. That's an extra variable you don't need.

Invoice Template avoids that variable entirely by not sending invoice or client data anywhere. It runs as a Chrome extension and saves everything — client records, invoice history, status — using the browser's local storage (chrome.storage.local) directly on your device. There's no server-side database, no account, and no sync step where a client's billing details cross the network. That's true no matter which country the client is in or which currency you're billing them in, which removes one layer of jurisdictional uncertainty when you're dealing with clients spread across the US, UK, Canada, Australia, or anywhere else. For the fuller explanation of what that means and why it's structured this way, see Privacy by Design.

It also means the currency and client-selection workflow above works the same whether you're at a desk with a fast connection or finishing an invoice on a flight before a client's payment terms run out — because none of it depends on a live connection. See the FAQ for the full rundown of what works offline and what's stored where.

A simple example

Say you're a freelance developer with three clients: one in New York (USD), one in Berlin (EUR), and one in Manila (PHP, historically invoiced in USD by agreement). In practice, that means three client records, each with its own saved default currency, each invoice automatically formatted and labeled correctly without you touching a currency setting mid-invoice, and three separate invoice histories you can track by status — all stored locally, all exportable to PDF the same way regardless of which currency is on the page. That's the whole workflow: set the currency once per client, let the invoice tool carry it forward, and keep the underlying data where only you can see it.