How to invoice as a digital nomad: legal and tax considerations

Your client is in San Francisco, your bank is in Estonia, you signed the contract from Bali, and you'll invoice next month from Lisbon. That gap between "where you are" and "where your business lives" is where tax and legal problems quietly accumulate.

Your invoicing address is a legal statement, not a convenience

Every invoice you send is a document that asserts something about your business: who you are, where you operate, and what tax rules apply. If your invoice shows a Bali co-working space address one month and a Tbilisi apartment the next, you are signalling to clients (and their finance teams) that your business has no fixed seat. That creates friction.

The fix is to pick one legal address and use it consistently. This is usually:

• The address of your registered company (an Estonian e-Residency OÜ, a US LLC, a UK Ltd)
• The address of your registered agent in that jurisdiction
• Your tax residency address, if you have established one (Georgia, Portugal, UAE, etc.)

It does not have to be where you sleep. It has to be where your business is legally constituted. Once you decide, every invoice gets that address. Every contract references it. You stop looking like a ghost.

What clients actually check

US and EU corporate clients run vendor onboarding processes. They will ask for a W-8BEN-E or W-9 (US), a VAT number validation (EU), or both. Your invoice address needs to match the entity on those forms. A mismatch between the form you submitted to procurement and the address on invoice #47 is the kind of thing that delays a $14,000 wire by three weeks.

VAT and reverse-charge: what you actually owe

If you invoice a US corporate from a non-EU entity, VAT usually does not apply at all. But if your registered entity is in an EU country and you invoice another EU-registered business, the reverse-charge mechanism shifts the VAT obligation to your client. Your invoice must explicitly state that, or you risk the client's accounts payable team rejecting it or, worse, paying it wrong.

The rule: if you are EU-registered and invoicing an EU business that has given you a valid VAT number, you zero-rate the invoice and add the reverse-charge note. If you are invoicing a US company from your EU entity, no VAT applies. If you are invoicing an EU consumer (not a business), you may owe VAT in their country under OSS rules.

What to put on the invoice

For an EU B2B reverse-charge invoice, the invoice must show:

• Your VAT number
• The client's VAT number
• The line: "VAT reverse-charged under Article 196 of Directive 2006/112/EC" (or equivalent national wording)
• A zero VAT amount

ZenPay handles this with a per-invoice reverse-charge VAT toggle that zeros the tax line and appends the required statutory note automatically. No copy-pasting legalese from a Google Doc each time.

Multi-currency invoicing without losing track of your actual earnings

You bill a Berlin agency in EUR, a New York startup in USD, and a London SaaS company in GBP. By the end of the quarter you have three piles of money that mean nothing until you convert them to your reporting currency. The problem is not the conversion. It is knowing what you actually earned before you convert.

Proving tax residency through your invoices

Tax authorities in your home country (or a country you spent 183+ days in) may ask for proof that you are genuinely conducting business from your declared tax jurisdiction. Your invoices are evidence. Specifically, they look at:

• The entity name and address on each invoice
• The dates invoices were issued relative to your entry/exit stamps
• The currency and payment method used

If your invoices consistently show a registered Estonian OÜ or a Georgian LLC address, and payments route to a business bank account in that jurisdiction, you have a paper trail that supports your residency claim. If your invoices show a shifting personal address, you have the opposite.

Keep at least one PDF copy of every invoice you send, timestamped and unedited. ZenPay exports all invoices to PDF and CSV at any time, which is exactly the format a tax adviser or authority will ask for.

Auto-reminders work even when you are twelve time zones away

The most common nomad invoicing failure is not a legal one. It is chasing a $9,500 USD invoice from a US client while you are running on Bangkok time and the client's accounts payable team is in New York. By the time you remember to follow up, the invoice is 22 days overdue and nobody on the client side remembers approving it.

Auto-reminders set to fire 3 days before and 7 days after the due date, sent in your name, from your email address, require nothing from you at 2am. You set them once per account, edit the template to match your tone, and the system runs the follow-up regardless of your timezone.

For recurring advisory retainers ($8k–$18k monthly with US corporates), recurring invoices auto-send at a user-set local time, so the invoice lands in the client's inbox at the start of their business day, not at midnight Pacific when it was generated at noon in Chiang Mai.

The legal and administrative side of nomad invoicing is genuinely more complex than invoicing from a fixed address. But the complexity is finite. Lock down your legal entity, apply the right VAT treatment for each client's jurisdiction, keep consistent records, and automate the follow-up. That is the entire problem.