How to invoice international clients in multiple currencies

Sending invoices to clients in three different countries means three different currencies, three different tax rules, and three different "where's my payment?" conversations. If you're a digital nomad consultant billing US corporates in USD, EU agencies in EUR, and the occasional UK client in GBP, the admin alone can swallow half a day each month.

Here's how to get it under control.

Choosing which currency to invoice in

The short answer: invoice in your client's currency whenever you can. A New York-based SaaS company receiving a bill in EUR will sit on it longer because someone in finance has to approve the FX conversion. Invoice them in USD and you remove that friction entirely.

A few rules that hold up in practice:

• Bill in the currency your contract specifies. If the SOW says USD, don't switch to EUR at invoice time even if the rate moved in your favour.
• Know who absorbs the FX risk. If you invoice in the client's currency and your home currency weakens, you lose. Build a small buffer (2-3%) into your rate for long projects, or agree on a rate-lock clause.
• Keep currencies consistent per client. Switching between USD and EUR on successive invoices creates reconciliation headaches on both sides.

For a digital nomad with income in four currencies, tracking what you're actually earning requires capturing the exchange rate at the moment each payment lands, not at invoice date. That gap can be significant on a $14,000 USD retainer paid 45 days after issue.

Setting up your invoice for cross-border compliance

An invoice that clears customs (the finance department kind) hits several requirements that domestic invoices skip.

What international invoices need

• Your legal name or trading name, registered address, and tax ID
• Your client's VAT number or tax ID (especially for EU B2B)
• A clear currency code (USD, not just "$") on every line item
• Payment details in the recipient's format: SWIFT/BIC + IBAN for Europe, ACH routing + account number for the US, PIX key for Brazil
• Correct reverse-charge VAT language for EU B2B transactions where your client handles the VAT

Reverse-charge VAT is the one that trips up new-to-EU consultants the most. When you invoice a VAT-registered business in another EU country, you zero-rate your invoice and add the line: "VAT reverse charged." Your client self-accounts for the VAT. Skip that line and you may inadvertently charge VAT you're not entitled to collect, or trigger a compliance question from your client's accounts team.

Payment terms matter more internationally

NET 30 from a Berlin agency and NET 30 from a US corporate are different experiences. US enterprise procurement regularly runs NET 60 or NET 90 as standard. Set your payment terms explicitly on every invoice. "Due on receipt" is appropriate for smaller project balances; NET 30 is fair for most retainers. Whatever you choose, state it in writing so there's no ambiguity when you follow up.

How most consultants handle this versus a smarter setup

Getting paid across borders: payment methods that actually clear

The invoice is only half the job. Payment methods that work domestically often fail internationally.

• SEPA for EUR transfers within Europe: low fees, 1-business-day settlement
• ACH for USD payments from US clients: standard for B2B, usually free for the payer
• SWIFT/wire for everyone else: slower (2-5 days) and often involves intermediary bank fees
• PIX if you have Brazilian clients: instant, 24/7, and your invoice QR code can encode your PIX key directly so clients pay in two taps
• WeChat Pay / Alipay for clients in China: QR codes on invoices work here too

The practical move is to list every relevant payment method on your invoice upfront, grouped by region. A US client scanning for "how do I pay this?" should see ACH details immediately, not hunt through SEPA and IBAN fields that mean nothing to them.

Keeping your books clean when income arrives in four currencies

When a $14,000 USD payment lands in your account, what's the EUR equivalent in your books? It depends on the rate on settlement day, not the rate when you issued the invoice. That difference is a real gain or loss that affects your tax filing.

A clean workflow:

1. Record the exchange rate at payment time, not invoice time.
2. Separate your wallets by currency so USD income and EUR income don't blur together until you deliberately consolidate.
3. Export to CSV monthly so your accountant has clean line-by-line data: invoice date, payment date, currency, amount, exchange rate applied.
4. Flag unpaid invoices by currency in your ageing report so you know whether that overdue balance is a €3,200 EUR problem or a $9,500 USD problem. They require different follow-up conversations.

ZenPay captures the exchange rate at payment time and lets you export everything to CSV, which is exactly what your accountant wants when tax season arrives.

Running a multi-currency practice is genuinely more complex than billing in one currency, but the complexity is mostly administrative. Solve the admin layer and the rest is just doing good work.