How to Invoice as a Translator: Rates, Terms and Templates

TL;DR: State the language pair, source word count, and per-word or project rate on every invoice, separate rush fees and formatting surcharges from the base translation charge, reference the project or PO number for agency work, and fix the payment currency in the quote.

Translators usually bill per source word, per project, or hourly for creative transcreation and review meetings. Invoices should state language pair, word count basis (source vs target), and any minimum fee so agencies and direct clients can reconcile files.

Certified or sworn work may carry flat page rates—note certification statements separately where required.

CAT-tool fuzzy matches, repetitions, and pre-translated segments change what you can ethically charge—if you discount them, reference the TM log or a short note so finance sees the same math you saw in the quote.

Typical rates

Rate per word with tiered discounts for volume; rush multiplier (e.g. 25%–50%) with deadline on the invoice. MTPE (machine translation post-editing) often uses lower per-word rates with quality SLAs. The American Translators Association offers professional standards context for U.S. linguists—external credibility without promising specific outcomes.

Formatting-heavy PDFs deserve surcharges—call them out.

Video work should split transcription, time-coding, and subtitle delivery when priced separately so marketing teams approve costs in stages instead of rejecting one lump sum.

Sample invoice line items

When to send the invoice

For agency work, invoice immediately upon file delivery. Most LSPs (language service providers) process invoices in monthly or biweekly batches; submitting the day you deliver starts the payment clock at the earliest possible point. Include the agency's PO or project number in the header.

On direct client projects, invoice on delivery with payment due before or at the time you release the final files. For larger projects, split into 50% at kick-off and 50% on delivery.

For high-volume ongoing agency relationships, consolidate all projects delivered during the month into a single monthly invoice with each project listed as its own line item (including PO, language pair, word count, and rate). This simplifies AP processing and reduces the number of invoices the agency has to handle.

Payment terms

Net 30 with agencies; 50% upfront for large direct clients or new relationships. Net 15 once established. Currency fixed in quote—repeat on invoice. Late fees per signed T&Cs.

PO numbers for enterprise LSPs—never omit.

Cross-border B2B may need reverse-charge VAT language on the PDF—have a tax advisor review your standard footer once, then reuse it.

High-volume LSP work often uses consolidated monthly statements—still list each project or PO on its own row or attach a schedule. One opaque monthly total guarantees disputes when any single file is questioned weeks later.

What to include

Project name, language pair, word count and how measured, service (translation, proof, MTPE), delivery date, rush flag, tax if applicable, total, due date. Read what to include on an invoice for business details.

Reference file names or batch IDs help AP match payments.

Our guide to writing an invoice covers numbering and legal identifiers—enterprise portals reject incomplete PDFs constantly.

Common mistakes

Target word billing without client agreement—mismatch with quotes. Hidden minimums—disputes. Scope creep (DTP, voiceover) folded into “translation.” Copyright assumptions—rights stay contractual, not invoice magic words.

Ignoring currency—state payment currency and who pays wire fees on international jobs.

Quoting words without naming the count tool or what counts as a word—align CAT logs with billed totals.

UI and software strings without character limits and context screenshots in scope—engineers ship endless CSV updates that eat margin if you billed a naive word count.

NDA project names on invoices—use internal codes when confidentiality matters; keep the real title in your private job log.

Template link

Use our translation services invoice template for words, hours, and fees.

FAQ

Should I bill source words or target words? Bill source words -- it is the industry standard because you and the client can verify the count before work begins. Target-word billing (common in some European markets) can lead to disputes because the target word count is unknown until translation is complete. Whichever you choose, state the basis clearly on the invoice and in the quote.

How do I handle CAT-tool fuzzy matches and repetitions? Apply tiered discounts per industry norms (e.g., 100% matches at 10% of your base rate, 75-99% matches at 40%, etc.) and note the discount structure on the invoice or in the attached word-count report. This transparency shows the client they are getting fair pricing for leveraged content while you are compensated for review work.

What if the client provides poor source material that requires extra editing? Note in your quote that the rate assumes publication-ready source text. If the source requires significant editing before translation, issue a change order for editing hours or a per-word surcharge. Show the editing work as a separate line on the invoice ("source text editing -- EN, pre-translation cleanup") so it is clear this was not part of the translation scope.

Reuse the same section headers each month so repeat LSP clients recognize your format instantly.

---

Join early access to invoice translation work with less back-and-forth.