Paying course developers, curriculum writers and translators across borders

Every published course is the visible tip of a lot of behind-the-scenes work. Content developers, curriculum and instructional designers, subject-matter experts and, above all, the localisation and translation contributors who adapt a course for each market all sit behind it. Most of these people are cross-border freelancers, paid per project or per milestone as the work is delivered rather than on a fixed monthly cycle.

Localisation makes the payment picture especially busy: to ship one course in several languages you may be paying many contributors, in many countries, for overlapping pieces of work. The payments are staggered against milestones, they are in different currencies, and you still need to know which course and which language edition each cost belongs to. This guide looks at how to run that without the spend turning into an untraceable blur. It is general information, not financial advice, so confirm your own position before acting on it.

The people behind the course

This is production talent, not teaching talent. Where a tutor earns a share of what learners pay, a curriculum writer or translator is delivering a defined piece of work for an agreed fee, usually broken into milestones: an outline, a draft, a first language pass, a review. Each milestone releases a payment, so the cash goes out in stages over the life of the project rather than in one settlement.

Because these contributors are scattered internationally, a single course can involve people in several countries before it ever launches. The localisation layer multiplies this: each target language is its own small project with its own translator, reviewer and sometimes a cultural adaptation pass, each owed at their own milestones in their own currency.

Why localisation multiplies the payments

Shipping one course in one language is a manageable set of payments. Shipping the same course in several languages is the same work repeated per market, so the number of contributors and the number of staggered milestone payments grows with every edition you add. You are no longer paying a few freelancers; you are running many small, overlapping payment schedules at once.

Each of those cross-border payments can carry its own transfer fee and its own conversion step. On milestone-sized amounts to many contributors, that cost adds up quietly. And contributors, like anyone, prefer to be paid reliably and in a currency that works where they live, so an awkward converted amount in the wrong currency is friction you do not want when you are trying to keep good localisation people available for the next edition.

Ring-fencing each course's production budget

The hardest part to get right is attribution. If every contributor payment comes out of one general balance, you lose the ability to say what a given course, or a given language edition, actually cost to produce. That matters for deciding whether a market was worth localising into and for pricing the next one.

A practical approach is to ring-fence the budget per course or per edition, keeping that production spend separated from the rest of your money, and to pay contributors in a currency that suits them. Holding balances in more than one currency lets you do that without converting on every milestone, and if you hold the balances you can run conversion on your own timeline rather than at the moment of each payment.

Keeping each cost attributable

The operational goal is that every contributor payment carries the course and language edition it relates to. When the records are clean, you can answer what each edition cost, compare that against what the market earns once it launches, and give your accountant a view that ties production spend to specific products rather than to a single undifferentiated outflow.

That argues for categorised payout records and, where it helps, separate pots or cards for each production budget so the spend is naturally grouped before you even reconcile it. The earlier you capture which course and language a cost belongs to, the simpler every later conversation becomes.

How Altery fits

Altery gives you cross-border payouts and multi-currency business accounts holding USD, EUR and GBP, so you can pay localisation and content contributors in a currency that works for them rather than converting on every milestone. Because you hold the balances, you run FX on your own timeline, converting in deliberate batches when the timing suits rather than at each individual payment.

Ring-fencing pots and sub-accounts, plus business cards with per-card limits, let you fence off a course's production budget so the spend on one edition stays separate and visible. Categorised, real-time records let you attribute each contributor payment to the course or language edition it belongs to, so you can see what each edition cost and tie it back to the product. Multi-entity management helps if you produce through more than one company. Altery is not a bank, and this is general information rather than advice.

Frequently asked questions