Invoice Mistakes That Stall Overseas Payments

You sent a clean invoice to a client in Berlin on the 3rd. It is now the 47th day. AP says they never received it, your bank shows nothing, and the project manager has stopped replying on Slack. Somewhere between your outbox and their payment run, something went wrong. Usually it is one of the same eight things.

Quoting one currency and billing in another

You agreed the project at 8,000 USD. The contract says USD. The invoice you sent shows EUR 7,380 because that is what your accounting tool defaulted to. AP now has to reconcile two numbers that do not match, the client questions the rate you used, and the invoice sits in a queue waiting for someone to decide who is right.

Pick a currency before you start the work and put it in writing. Match the invoice exactly. If you genuinely need to bill in a different currency than you quoted, show both on the invoice with the rate and the date you used. Our currency converter is fine for a sanity check, but the rate that matters is the one your client's bank applies on settlement day.

Sending bank details that the payer's bank cannot use

A US routing number means nothing to a bank in Singapore. A bare IBAN with no BIC will get rejected by some payers' systems. "Wire to my Wise account" with no beneficiary address fails compliance checks. Each rejection costs you three to seven days while the message bounces back through AP.

For SEPA payments, give IBAN and BIC. For wires, give the full beneficiary name as it appears on the account, beneficiary address, account number, SWIFT/BIC, bank name, bank address, and any intermediary bank if your bank requires one. Run the IBAN through an IBAN validator before you send. If you take payments from multiple regions, list local rails where you have them (ACH for US, Faster Payments for UK, SEPA for the eurozone) so the client picks the cheapest route.

Ignoring the PO number requirement

Most companies above about 50 people will not pay an invoice without a purchase order number on it. The invoice arrives, AP cannot match it to anything in their system, and it goes into a pile that someone reviews on Fridays. Your contact does not know this is happening because they are not in AP.

Ask for the PO number before you invoice, and make it easy to add later if it changes. With JupiterInvoice the recipient can drop in a PO number on their own without emailing you, which is the whole point of letting the client edit their own invoice. If you are not sure their format is valid, the PO number format checker will flag the obvious mistakes.

Getting the billing entity wrong

You invoiced "Acme Inc" because that is the brand on the website. The contracting entity is actually "Acme Europe B.V." in the Netherlands, which is who signed the contract and who pays the bills. AP rejects the invoice. You reissue. Two more weeks gone.

Confirm the legal billing entity, the registered address, and any tax ID (VAT, GST, ABN) before you issue. The same applies to your side: if your business name and your bank account name differ, the payment may bounce on a name mismatch. The practical guide to international invoicing walks through the entity and tax fields country by country.

Skipping the tax section because "it is export, so zero"

Sometimes it is zero. Often it is not, and even when it is, you still need to show it correctly. A UK freelancer billing a German business with no VAT line and no "reverse charge" note is sending an invoice the client's accountant cannot file. A US contractor billing an Australian company with no W-8BEN on record may have 30% withheld.

State the tax position explicitly on the invoice. If it is zero-rated or reverse charge, say so in the exact words the destination country expects (try the invoice phrase translator if you are unsure). If withholding tax applies, agree who absorbs it before you start work.

Vague payment terms

"Payable on receipt" means nothing to an AP team that runs weekly payment batches on Thursdays. "Net 30" with no issue date is ambiguous when the client claims they received it a week after you sent it.

Put the issue date, the exact due date, and the payment terms in plain numbers. "Issued 3 March 2025, due 2 April 2025, Net 30" leaves nothing to interpret. If you need help picking terms that match how overseas AP cycles work, comparing Net 15, 30 and 60 is a good starting point.

Emailing a PDF and hoping

You attached the PDF to a thread with six people on it. Three days later you cannot tell if anyone opened it. Your contact says she forwarded it to AP. AP says they never got it. Nobody is lying, but nobody can prove anything either.

Share a link instead of an attachment. You can see when it was opened, the recipient can forward it to AP inside the tool, and there is no "the PDF was in spam" story to chase down. Stop guessing whether they saw it.

No follow-up cadence

Day 30 passes. You feel awkward chasing. You wait until day 45, send a polite nudge, wait another week, send a firmer one. By day 60 you are negotiating from a weak position because the work was finished two months ago.

Decide the cadence before you send: a soft reminder three days before due, a check-in on the due date, a firmer note at day 7 past due, an escalation at day 14. Write the messages once and reuse them. When the client is overseas and you cannot just call, the cadence is the whole game.

Fix these eight and most international invoices settle on time. When you are ready to send the next one, start a new invoice and put a link in front of your client instead of an attachment in their spam folder.