Invoice Chasing for Freelance Translators

Why translators face slower, murkier payment cycles

A large share of freelance translation work runs through agencies rather than direct clients, and agencies often default to Net 30 or Net 60 as a matter of internal policy rather than any reflection of how quickly they were paid by the end client. That gap between "job delivered" and "invoice due" is frequently longer than in most other freelance work, and it is set by someone else's process, not yours.

Cross-border work adds a second layer of friction: different currencies, different banking rails, and sometimes a finance team in a different time zone that only processes payment runs on a fixed weekly or monthly schedule. A one-day delay in submitting an invoice can mean missing that cycle entirely and waiting for the next one.

Translators also often juggle several agencies and direct clients at once, each with its own portal, PO number requirements, or invoice-submission format — which makes it easy for one invoice to get stuck in an admin queue without anyone noticing until it is weeks overdue.

What actually keeps translator invoices moving

Submitting the invoice the moment the job is marked delivered — not batching it for later — matters more here than almost anywhere else, since a delayed submission can push you into the next payment cycle by default.

A follow-up reminder timed to when you know a client's payment run happens (for example, a nudge just before the end of the month) is more effective than a generic day-30 reminder, because agency payment cycles are calendar-driven, not delivery-driven.

Tracking invoices by agency rather than by job also helps: if one agency is consistently the last to pay across several projects, that is a signal to tighten terms or ask for prepayment on the next assignment, not just chase harder on this one.

Handling multi-currency and cross-border follow-up

State the currency and amount unambiguously on every invoice, and where possible give the client a direct payment link rather than relying on them to correctly key in international bank details — wrong account digits or a missed SWIFT code are a common, avoidable cause of "the payment is stuck" delays.

When a payment does appear late specifically because of a cross-border transfer (correspondent bank delays, currency conversion holds), it is worth asking the client which stage it is stuck at before assuming non-payment — the fix is often on the banking side, not a refusal to pay.

How to choose honestly

If you work with one or two steady agencies who pay reliably on their stated cycle, a simple invoicing tool with basic reminders is probably enough — the relationship itself is doing most of the work.

If you are juggling multiple agencies on different cycles, in different currencies, and small delays keep turning into forgotten invoices, a tool that tracks every open invoice in one place and reminds on a schedule you set (not just a generic day count) removes the part of the job that has nothing to do with translating.

FAQ

Why do translation agencies use such long payment terms?

Agencies often standardize on Net 30 or Net 60 across all their freelancers as an internal policy, sometimes tied to when the agency itself gets paid by the end client — it is rarely a reflection of your specific invoice or relationship.

What should I do if an international payment seems stuck?

Ask the client which stage it is at before assuming non-payment — cross-border transfers can stall at a correspondent bank or during currency conversion, and that delay is often resolvable without an adversarial conversation.

Does it help to track invoices by agency instead of by job?

Yes — if one agency is consistently the slowest payer across several assignments, that pattern is more useful for deciding on terms (or asking for prepayment) than treating each late invoice as an isolated incident.