You finish a 3,000-word technical manual for a client in Germany, invoice €450, and three weeks later €431 lands in your bank account. No explanation, no line item, just a smaller number than you expected. If you've ever stared at that gap wondering where €19 went, you're not alone — it's one of the most common financial mysteries freelance translators and interpreters run into, and it's almost always a combination of exchange-rate spread and a payment processor's cut that never showed up on any invoice.
Translation and interpretation are unusual freelance professions from a bookkeeping standpoint. Most freelancers bill one currency, one client type, and one unit of work. Translators and interpreters often juggle all three at once: a per-word rate for one client, a per-hour rate for another, a rush surcharge tacked onto a weekend request, and payments arriving in euros, pounds, or yen through four different platforms. None of that is complicated in isolation — it just needs a system, because the default habit of "check the bank balance and hope" falls apart fast once currency conversion and multiple pricing units enter the picture.
Per-Word vs. Per-Hour: Picking (and Tracking) the Right Unit
Most professional translation work is quoted per word, not per hour. That's because a per-word rate gives both sides a measurable, predictable unit — the client knows the cost before the job starts, and you're paid for output rather than how fast you happen to type. In 2026, typical per-word rates run from about $0.08 to $0.30, with the range shaped heavily by subject matter:
- General or marketing content: roughly $0.08–$0.12/word
- Technical or medical translation: roughly $0.15–$0.25+/word
- Legal translation: roughly $0.25–$0.40/word
Interpretation, by contrast, is almost always billed by time, because the "unit of output" for live spoken language doesn't translate into a countable word count the way written text does. Hourly rates for general interpretation average around $30–$35/hour, while specialized conference or legal interpreters — particularly those doing simultaneous interpretation — can command $75–$200/hour or more. Remote simultaneous interpretation is increasingly billed per minute, often in the $1.50–$4.00/minute range.
The bookkeeping implication: if you work across both disciplines, or across multiple clients with different pricing models, a single "hourly rate" column in your records won't capture what's actually happening in your business. You need line items that record, per project: the pricing unit (word, hour, minute, or project), the rate, the quantity, and the resulting subtotal — before any rush fee or minimum charge is applied. Without that breakdown, you can't answer basic questions like "which service line is actually more profitable per hour worked," which matters more than it sounds, because a $0.12/word general translation job that takes you three hours to research and format can easily pay less per hour than a $30/hour interpretation booking.
Rush Fees and Minimum Charges: Small Line Items That Move the Bottom Line
Two pricing add-ons are standard in this industry and easy to undertrack:
Rush fees. A same-day or overnight turnaround typically adds a 25%–50% surcharge on top of the base per-word rate. If you don't record the rush premium as its own line item — folding it into a single "translation services" total instead — you lose the ability to see how much of your revenue actually comes from expedited work, which matters when you're deciding whether to keep accepting rush jobs that disrupt your schedule for a proportionally small bump in pay.
Minimum project fees. Most translators set a minimum charge of $50–$150 to cover the fixed overhead of any job — file setup, formatting, a quick client email exchange — regardless of how short the actual text is. Interpreters do the same with minimum booking windows, commonly 2–4 hours even for a 45-minute assignment, because travel time, prep, and schedule-blocking make a shorter booking unprofitable otherwise.
Both of these exist to protect your effective hourly rate on small jobs. But if your invoicing habit is "charge whatever feels fair" rather than a written minimum you apply consistently, you'll end up with a pile of five- and ten-dollar low-margin jobs that quietly drag your average rate down over the year — and you often won't notice until you do the math at tax time.
Multi-Currency Payments: Where the Money Actually Goes
This is the part of the business that trips up even experienced freelancers. If you work with international clients or agencies, you're likely getting paid through some combination of Wise, PayPal, Payoneer, direct bank wire, or a client's in-house payment portal — and each one handles currency conversion differently.
Exchange-rate spread is a real cost, even when no fee is itemized. PayPal and similar platforms typically add 3%–4% on top of the market exchange rate when converting a payment to your home currency. That markup rarely appears as a labeled "fee" — it's baked into the conversion rate you're given, which is why a €450 invoice can land as $431 or less in your account without a corresponding line item you can point to. Wise, by contrast, is built around using the actual market rate with a much smaller, disclosed markup (roughly 0.33%–2.5% depending on currency pair and amount), which is why many translators route payments through it specifically to avoid the spread.
1099 reporting won't match your invoiced amount. Freelancers who receive $600 or more from a US-based client should get a Form 1099-NEC reflecting what the client paid, not what you received after conversion or platform fees. Payment processors like PayPal issue their own Form 1099-K once your gross payment volume crosses their threshold — but that figure reflects gross inflows before fees, refunds, or currency conversion costs are backed out. Wise doesn't issue a 1099-K at all, which means every Wise-received payment is entirely on you to log and categorize.
The fix is the same regardless of platform: record the invoiced amount and the received amount as two separate numbers, and post the difference to its own expense category (something like "Bank & FX fees") rather than letting it vanish into rounding. That gives you an accurate revenue figure for tax purposes — the IRS expects you to report the full amount earned, not the discounted amount that happened to clear your bank — while still letting you see, client by client and platform by platform, how much currency conversion is actually costing you. Over a year of international work, that spread often adds up to hundreds of dollars that's fully deductible as a business expense, but only if it's tracked as one instead of silently absorbed into "I guess that's just what I got paid."
Building a System That Doesn't Depend on Memory
The common thread across pricing units, rush fees, minimums, and currency spread is the same: none of these are hard to track individually, but a freelancer relying on invoices in one folder, PayPal statements in another, and a bank balance nobody reconciles will lose the details that make the numbers meaningful. A workable system for a translator or interpreter needs, at minimum:
- One invoice record per project that separates base rate, quantity, rush surcharge, and minimum-charge adjustment as distinct line items rather than a single lump total.
- A currency-received log that captures the invoiced amount, the received amount, the platform used, and the resulting FX/fee variance — so year-end totals reconcile against 1099s instead of contradicting them.
- A recurring monthly reconciliation where you match what platforms report against what you actually invoiced, catching missing payments and unexplained shortfalls while the details are still fresh, not in April.
This is exactly the kind of record-keeping that plain-text accounting handles well, because every invoice, currency conversion, and fee is a discrete, auditable entry rather than a number buried in a spreadsheet tab or a PDF statement. Beancount.io lets you track per-project income in its original currency, log the converted amount separately, and see the FX spread as its own line — all in version-controlled, human-readable files you can review at tax time without reconstructing six months of PayPal history. Get started for free and see why translators, interpreters, and other multi-currency freelancers are moving their books to plain-text accounting.