How to send invoices when working across multiple countries

You landed a $12k engagement from a San Francisco startup, a €4,500 retainer from a Berlin SaaS company, and a £3,200 project from a London agency. Now you need to invoice all three from your current address in Lisbon, and your "home" currency is technically the Singapore dollar. Knowing how to send invoices when working across multiple countries is not a minor admin detail. Done wrong, it creates payment delays, VAT penalties, and FX losses that quietly eat your margin.

Here is how to do it right, step by step.

Pick the right currency for each invoice

The instinct is to bill everything in USD and move on. Resist it, for two reasons.

First, your EU clients almost certainly prefer invoices in EUR. Paying USD from a EUR account triggers a conversion fee on their side, which creates friction and occasionally a request to "adjust the amount" once FX is applied. That conversation costs you time and goodwill.

Second, large US corporates often route invoices through accounts payable systems that are set up for USD. Sending EUR to a US company's AP department is a minor headache for them that becomes a reason to sit on the invoice an extra two weeks.

The practical rule: invoice in the client's operating currency unless you have a specific reason not to. Your $12k San Francisco contract gets a USD invoice. Your Berlin retainer gets a EUR invoice. Your London agency gets a GBP invoice.

What you need, then, is a tool that lets you pick a different currency per invoice and then consolidates totals by currency so you can see your actual receivables without building a manual spreadsheet. ZenPay supports 11 currencies (EUR, USD, GBP, CAD, AUD, JPY, CHF, SEK, SGD, BRL, CNY) with per-invoice currency selection, and its multi-currency wallets aggregate what you are owed per currency in one view.

What to put on each invoice: mandatory fields by recipient country

This is where most generic guides fail you. "Include your name and address" is not useful advice when the legal requirements shift depending on where your client is incorporated.

Invoicing a US corporate

US companies do not have a statutory invoice format the way EU countries do. But their AP departments will hold your invoice if it is missing:

• Your full legal name and address (even if you are currently in Bali, use your registered business address or the address tied to your tax residency)
• Their purchase order (PO) number, if issued. No PO, no pay is a real policy at many companies.
• Your payment details: ACH routing and account number, or wire instructions with SWIFT/BIC. US AP teams almost never send international wires unless you specifically set up that expectation.
• W-8BEN or W-8BEN-E reference: You do not put the form on the invoice, but you should have already submitted it to their AP team. If you have not, they will withhold 30% on payment.

Invoicing an EU company (B2B)

EU-to-EU and non-EU-to-EU B2B invoices are governed by the EU VAT Directive, and the rules are stricter.

For a non-EU supplier invoicing an EU business client (your situation as a nomad registered outside the EU):

• You do not charge VAT. The client accounts for VAT under the reverse-charge mechanism.
• You must include the text "VAT reverse charge" or "Reverse charge - VAT to be accounted for by the recipient" on the invoice. Without this line, your German or Dutch client's finance team will reject the invoice or hold it for clarification.
• Include your client's EU VAT number on the invoice. This is what allows them to self-assess VAT and reclaim it.
• Include your own tax ID or VAT number if you have one.

For an EU-registered supplier invoicing another EU business (if you have a Portuguese NHR setup, for example):

• The same reverse-charge rules apply for cross-border EU B2B.
• You charge 0% VAT and include both VAT numbers plus the reverse-charge statement.

Invoicing a UK company (post-Brexit)

The UK operates its own VAT system now. The reverse-charge rules for B2B services still apply. Include "Customer to account for any VAT to HMRC" if you are not UK VAT-registered. Include your client's UK VAT number.

How auto-reminders save you from the NET 60 black hole

Enterprise clients in the US and EU routinely run NET 30 to NET 60 payment terms. When you are managing three clients in three countries, one of whom is 47 days into a NET 60 term and two of whom are ignoring your follow-up emails, the follow-up work becomes a part-time job.

The lever that actually moves the needle is early, consistent contact, not a panicked email on day 61.

Managing your address and legal identity across borders

This is the practical knot that no generic invoicing guide untangles. You are physically in Lisbon, tax-resident in Singapore (or Dubai, or Georgia), and billing a company in New York. What address goes on the invoice?

Use your registered business address, not where you are sitting today. If you have a Singapore-registered entity, that address goes on every invoice regardless of your current timezone. If you are operating as a sole trader with no fixed registration, use the address tied to your tax residency filing. If you are genuinely unregistered anywhere (a legally risky position), use your last permanent address and get proper advice fast.

Your VAT or tax number (or its absence) signals to your client's finance team how to categorize the invoice. A missing tax ID on a $12k invoice to a US corporate can trigger a 30% withholding; a missing VAT number on a €4,500 invoice to a Berlin company can delay payment by three weeks while their accountant figures out the VAT treatment.

ZenPay lets you store your legal name, trading name, VAT number, and tax ID in your account and stamp them on every invoice automatically, so you never send a bare invoice by accident.

Consolidating everything into one picture

The hidden cost of multi-country invoicing is not any single invoice. It is the cumulative cognitive load of tracking USD receivables, EUR retainers, and GBP projects in separate mental (or actual) spreadsheets. When one client pays late, you lose track of which currency bucket is at risk.

A clear monthly view by currency, with ageing data (current, 1-30 days overdue, 30+ days overdue), is the single most useful thing you can build. ZenPay's reports surface revenue per currency, monthly trends, and ageing status so you can see in 30 seconds whether the problem is your San Francisco client dragging on USD or your Berlin client stalling on EUR.

The complexity of invoicing across multiple countries is real, but it is mostly front-loaded. Nail the currency choice, the mandatory legal fields, and the reminder cadence once, and you have a system that runs itself while you move between countries.