Freelance Translator Invoicing: Per-Word Rates, Multi-Currency Invoices, and Getting Paid on Time

You delivered 4,000 words on Tuesday, invoiced in a currency you do not bank in, and the money will land two months later minus a conversion fee nobody discussed. Nothing went wrong — that is simply what happens when a translator invoices like a generic hourly freelancer. Translation has its own billing physics: the buyer sets the unit, the unit hides the effort, and the payment terms arrive as a policy. This guide shows how to invoice so every word, currency, and agency cut is accounted for.

The Per-Word Rate Is a Quote Format, Not a Pay Rate​

Per-word pricing is the industry standard because it is transparent and scalable — but the number on your rate card tells you almost nothing about what you earn per hour. A thousand words of a marketing brochure and a thousand words of a patent filing are the same count and wildly different jobs.

Before quoting anything, convert your rate into reality. Take your last three jobs, count every hour honestly — including the glossary build, the client queries, and the revision round nobody quoted for — then divide each fee by those hours. If your per-word rate has not moved in three years while your rent has, this exercise usually explains the squeeze. Current US market data puts professional human translation around $0.08–$0.14 per word for common pairs, with certified, legal, and technical work priced higher. Whatever your pair commands, the hourly number underneath is the one that tells you whether the job pays.

Three details change what a word count is worth:

• Source vs. target counts. Some languages expand 15–30% in translation. Agree in writing which count the invoice uses before the first job, because the difference is pure margin either way.
• Weighted CAT counts. Translation-memory matches are not full-effort words. Many translators bill 100% matches and repetitions at a fraction of the base rate, with fuzzy-match bands (for example 75–99%) discounted on a sliding scale. Put the band table in your quote terms so the invoice math is never a surprise.
• What the count excludes. Screenshots, embedded spreadsheets, and uneditable PDFs all take time that a word counter never sees. Quote file preparation and desktop publishing separately, by the hour.

Build the Invoice Like an Auditor Will Read It​

Accounts-payable departments reject far more translator invoices over a missing reference than over a disputed price. Every invoice you send — to an agency or a direct client — should carry the same complete anatomy:

1. Your identifiers: legal name, tax ID where required, and remittance details.
2. Their references: purchase order number, vendor ID, and the project or job number from the assignment.
3. The work lines: one line per service (see below), each with its unit, quantity, and rate.
4. The money lines: subtotal, any discount, tax or reverse-charge wording where applicable, total, currency, and payment terms with a due date — not just "Net 30" but the actual calendar date.
5. The proof trail: delivery date and a reference to the delivery confirmation, so a missing attachment never becomes a missing payment.

Ask for the PO number, vendor number, and accounts-payable email before you start the job, not when the invoice goes overdue. Project managers cannot pay you and usually know it; the AP contact is the person your invoice needs to satisfy.

Price the Extras on Their Own Lines​

The fastest way to stop doing unpaid work is to give every extra its own price before the job starts. Per-word suits predictable prose where you know the effort. Everything else deserves its own unit:

• Revision and proofreading: by the hour, quoted separately from translation. A badly written thousand words can take longer than a clean three thousand, so never bundle editing into the per-word rate.
• Terminology and glossary work: by the hour, with the glossary itself listed as a deliverable.
• Certified translations: per certificate or per project, since the liability and formatting far outweigh the word count.
• Formatting and desktop publishing: by the hour, after you have seen the file.
• Rush and weekend work: a surcharge on the base rate. A standard professional pace is roughly 2,500 words per day; anything beyond that is legitimately rush territory, and 25–50% surcharges are normal market practice. Define the threshold in your terms so "urgent" has a price instead of a negotiation.
• Minimum charge: a floor that makes small jobs worth opening. Industry surveys put typical minimums around the equivalent of a short solid hour of your time — set yours from your own effective rate, and apply it to agencies as well as direct clients.

Save these once as a rate card — translation, revision, certification, rush, minimum — so pricing is a document, not a late-night decision. A second revision round is much harder to request as a favor once it already has a published price.

Invoice Multi-Currency Work Without Donating the FX Spread​

Translation is one of the most cross-border freelance trades there is, which means currency handling belongs in your invoicing process, not just your banking. Three agreements, made in writing before the first job, prevent nearly every dispute:

1. The invoice currency. Invoicing in your own currency gives you predictability; invoicing in the client's currency is often the price of winning the work. Either is fine — undiscussed is not.
2. Who carries the transfer fee. State on the invoice whether you or the client absorbs international transfer costs, so a $25 wire fee never comes out of your margin by default.
3. The reference rate and date. When you record foreign-currency income, note the amount in the invoice currency, the exchange rate, and the rate date on your own copy. Your books need the original amount preserved, not just whatever dollars eventually landed.

On the receiving side, a multi-currency account that lets you hold euros, pounds, and dollars without forced conversion — and convert near the mid-market rate when you choose — routinely beats a traditional bank that converts on receipt at a 2–4% markup. Batch smaller invoices into one monthly statement per agency where the relationship allows it: flat per-transfer fees punish weekly invoicing, and one consolidated invoice a month is also easier for the agency's AP team to process. Add up a year of conversion and transfer fees sometime and compare it with what one rate rise would have been worth; the result usually settles the "should I raise rates" question.

Agency Payment Terms Are a Policy You Can Negotiate Once​

Most agencies hand you terms — Net 30, 45, or 60 — as a take-it-or-leave-it policy. You will rarely rewrite the policy, but you can almost always negotiate your position inside it:

• Confirm the clock start. "Net 30" should mean 30 days from a correct invoice with all references attached, not 30 days from whenever AP gets around to entering it. Ask, and note the answer.
• Invoice on delivery day. Every day between delivery and invoicing extends terms you never agreed to. Same-day invoicing is the cheapest cash-flow improvement available to you.
• Use their portal properly. Vendor portals and monthly consolidated invoicing exist to make AP's life easier, which makes your payment faster. Learn the required fields once rather than re-submitting every month.
• Ask for a date, not for payment. When an invoice runs late, "could you confirm the payment date?" works far better than "please pay." A date is something a stretched AP clerk can agree to, and it gives you a concrete commitment to follow up on.

If one agency carries most of your year, the late invoice is the smaller half of the problem — client concentration is the bigger one. Track what share of trailing-twelve-month revenue your largest client represents, and treat anything approaching half as a risk to diversify away.

The Late-Invoice Playbook, in Order​

Do not open with a late fee. Industry payment data consistently shows late-fee clauses are almost always written and almost never applied — threatening one you will not enforce costs more credibility than the interest was worth. Work this sequence instead:

1. Re-send the invoice with the PO number and delivery confirmation attached. Missing references cause more delays than disputed prices.
2. Write to accounts payable, not the project manager. Be polite, be specific, and include every reference they need to find you in their system.
3. Ask for a payment date, then calendar a follow-up for the day after it.
4. Pause new work until the oldest invoice clears. This is the only leverage that reliably works, and it works because it is simply true: you cannot finance a client's cash flow indefinitely.

Keep a simple aging list — current, 30, 60, 90+ days — and review it weekly. A client drifting from 30 to 60 days across consecutive months is telling you something before the invoice ever goes critical.

Credit Notes, Corrections, and Deposits​

Word counts get revised, fuzzy bands get disputed, and occasionally you invoice the wrong PO. Handle corrections with formal credit notes rather than edited re-sends: a credit note referencing the original invoice number keeps the audit trail clean and gives the client's AP team a document their system understands.

For large direct-client projects — a book, a website localization, a multi-month retainer — take a deposit. Thirty to fifty percent upfront on first-time engagements is standard professional practice, and it filters out the clients most likely to pay late. Record deposits as a liability until the work is delivered; they are not revenue the day they arrive.

Keep Every Invoice Traceable to the Job​

Your filing system needs one property: any deposit in your bank account must trace back through an invoice to a purchase order, a word count, and a delivered file. A naming convention like 2026-09-014_ClientName_PO-8821_EUR-640.pdf plus a simple log (invoice number, client, PO, currency, amount, sent date, due date, paid date) delivers that without any special software. Reconcile monthly: every open invoice should have a known status, and every deposit should match an invoice total minus only the fees you already agreed to carry.

Per-word billing looks simple from the outside — count words, multiply by rate, get paid. From the inside, it is a small machine with many moving parts: weighted counts, minimums, rush bands, currencies, transfer fees, PO numbers, and payment dates. Build the machine deliberately, and invoicing stops being the part of freelancing you dread. For the other half of the picture — how these invoices flow into your books, your tax records, and your monthly close — see our guide to invoicing international clients for the multi-currency plumbing in more depth.

Simplify Your Financial Management​

As your translation work grows across agencies, currencies, and service lines, keeping every invoice traceable to its job is what separates a calm tax season from a frantic one. Beancount.io offers plain-text accounting that's transparent, version-controlled, and AI-ready — your ledger lives in text files you own, not a black box. Get started for free and see why developers and finance professionals are switching to plain-text accounting.