DEV Community

郭委
郭委

Posted on

Proving Translation Income: Words, Invoices and the Language Service File

Translators and interpreters run one of the most quantifiable freelance businesses in existence — every project has a word count, a per-word rate, and a delivery date. Yet translation income frequently fails verification anyway, because the file a translator submits looks like a pile of small PayPal transfers instead of a coherent revenue practice. The fix is the same quantification verifiers already understand: show words × rate = invoice, invoice × payment terms = deposit. Here's how to build the language service file.

The word-rate math that makes income legible

Translation work is billed per word (translation), per minute (interpreting), or per project. The most underwriter-friendly presentation converts everything to a realized monthly figure:

  • Blended rate: $0.11/word average across projects
  • Average monthly volume: 54,000 words
  • Realized monthly revenue: ~$5,940

The per-word rate alone proves nothing — a verifier can't tell whether 10,000 words a month is 2 projects or 20. Present the volume trend, not just the rate. And separate your service types, because they carry different evidence:

  1. Document translation — per-word billing, invoices, agency or direct clients. The core, labelable block.
  2. Interpreting — per-hour/per-day billing, often with booking confirmations. Label as event-based.
  3. Subtitling / localization — per-minute or per-asset billing, often platform-mediated (see the platform payout framework).
  4. Rush fees / minimums — surcharges and project minimums. Include, but label as variable.

A combined letter reads: "$4,200/month average in document translation, $950/month average in interpreting bookings, $790/month in localization platform payouts — total monthly equivalent $5,940."

The evidence chain: CAT stats → invoice → deposit

Translators have an evidence type almost no other freelancer has: project statistics. CAT tools (Trados, MemoQ, Smartcat, Phrase) export per-project word counts and rates — this is your timesheet equivalent:

  • Word counts per project, per client, per month
  • Invoices issued at stated per-word rates
  • Deposits matching invoiced amounts

The chain — stats → invoice → deposit — is self-verifying: anyone can multiply the word count by the rate and check it against the invoice. Include a summary table (client, month, word count, invoice, paid) and the file practically underwrites itself.

Agency clients vs. direct clients

Most translators split their work between agencies and end clients, and the evidence differs:

  • Agency clients: the agency pays reliably against invoices, and their payment records + your invoice history form a clean trail. Agency statements or payment remittances carry a third-party voice. Many agencies will confirm your engagement on request — ask your project manager; ongoing vendors get confirmed routinely.
  • Direct clients: your invoice + their payment + (ideally) a client confirmation letter. Translation buyers — law firms, publishers, corporations — respond well to confirmation requests because they already treat you as a vendor.

Label each block by source. The agency block underwrites easily; the direct block leans on the letter.

Failure modes and fixes

Failure 1: PayPal-dominated deposits with no labels. Fifty unmarked PayPal transfers a month look like casual payments, not business revenue. Fix: match each transfer to an invoice number in a summary table — labeled, the same deposits become an invoice trail.

Failure 2: Interpreting gaps. Conference interpreting is seasonal; empty conference months read as decline. Fix: show the booking calendar or pending confirmations alongside the dip, and anchor the file on the translation core.

Failure 3: Currency mixing without structure. Translators often bill in two or three currencies for different clients. A mixed deposit stream without labels looks chaotic. Fix: present per-client currency with a conversion note, or follow the multi-currency framework — structure beats volume.

Failure 4: Machine-translation-adjusted rates unexplained. Post-editing (MTPE) projects bill at lower per-word rates. A verifier seeing two rate tiers may assume inconsistency. Fix: label MTPE separately ("post-editing at $0.05/word, from-scratch translation at $0.11/word") — tiered rates are standard industry practice, not instability.

Failure 5: Minimum-fee distortions. Small projects billed at $35 minimums inflate the average word rate. Fix: disclose minimums as a line item; present the blended realized rate honestly.

The letter formula

State: your language pairs and years in practice, the service mix with each block's realized monthly average, your blended volume (words/month or bookings/month), and one line on client mix (agency vs. direct). Attach the project statistics summary, invoices, deposit trail, and agency remittances or client letters. The verifier should finish seeing a quantified professional service — words in, invoices out, deposits matching — not a stream of unlabeled transfers.

Translation income is verification-friendly income trapped in unlabeled presentation. Export the stats, number the invoices, label the deposits, and the math does the persuading.

Related guides

- https://gist.github.com/GuoXiaoWeiY/95c86e780fdd5ac057d1e0c72f3b5769

Need an income letter built for a translation practice? ProofLetter generates verifier-ready income letters for translators and language professionals.

Top comments (0)