Paying a global pool of tutors and course creators

If your platform or marketplace shares revenue with the people who actually teach and create, you are not running a simple payroll. You are running a recurring cycle that pays a worldwide pool of tutors, instructors and course creators, each one a different amount tied to what their learners watched, booked or bought. That usually means many small payouts, in several currencies, going to many countries, on a monthly or similar rhythm.

This is a different problem from paying a handful of staff or commissioning a one-off project. The amounts vary per educator and per period, the destinations are scattered, and the educators care a great deal about being paid reliably in a currency that works where they live. This guide looks at how to run that cycle without the slowness and FX leakage of paying everyone one transfer at a time. It is general information, not financial advice, so confirm your own position before acting on it.

Revenue share is not payroll

The defining feature here is that each educator's payout is earned, not fixed. A tutor who delivered more sessions this month, or a creator whose course sold well, is owed more than one who was quieter. The figure is derived from learner activity in the period, so it changes every cycle and has to be calculated per recipient before anyone is paid.

That makes this distinct from project invoices and from salaried staff. You are settling a share of what the platform collected with the front-line teaching talent who generated it, on a repeating cadence. The volume is the challenge: a healthy pool can mean hundreds or thousands of recipients, each owed a different and often modest amount.

Many recipients, many currencies, many destinations

Paying a global pool one transfer at a time is where the cost hides. Every individual cross-border payment can carry its own transfer fee and its own conversion step, so on small amounts the cost of paying can eat a noticeable slice of the payout itself. Across a large pool, that is a meaningful and largely invisible leak, repeated every cycle.

Speed is the other half. Initiating payouts manually, one by one, to scattered destinations is slow and error-prone, and educators notice when payment is late or unpredictable. They also notice when they receive an awkward converted amount in the wrong currency. Reliable, predictable payment in a currency that suits the recipient is part of how you keep good teaching talent on the platform.

Batching payouts and matching the currency

The operational fix is to stop treating each payout as a separate task. If you can submit the whole cycle as a single batch of many recipients, you remove most of the manual effort and the per-transfer friction that comes with it. The earned amounts come out of your reconciliation, and the batch does the distribution.

Matching the currency matters just as much. Holding balances in more than one currency lets you pay educators in a currency that works for them rather than forcing a conversion onto every recipient. And if you hold those balances, you can run conversion on your own timeline, converting in deliberate batches when the timing suits rather than at the moment of every individual payout.

Tying each payout back to each educator

Because every figure is earned, your records have to connect each payout to the educator and the period it relates to. If you cannot show, per recipient, what they were owed and what they were paid, the next cycle becomes a guessing game and disputes are hard to settle. The goal is a clean per-recipient trail: who, how much, in what currency, for which period.

That argues for keeping categorised payout records rather than a single lump outflow. When each payment carries the recipient and period it belongs to, reconciling the cycle against what each educator earned is straightforward, and your accountant gets a view they can actually work with.

How Altery fits

Altery is built for exactly this shape of payment. Global mass payouts let you pay your whole pool of tutors and creators in one batch rather than one transfer at a time, which removes most of the manual effort and per-transfer friction of a recurring cycle. Multi-currency business accounts hold USD, EUR and GBP, so you can pay educators in a currency that works for them instead of pushing a conversion onto every recipient.

Because you hold the balances, you run FX on your own timeline, converting in deliberate batches when the timing suits rather than at every individual payout. Categorised, real-time records give you a clean per-recipient trail of who was paid, how much and for which period, so reconciling the cycle against each educator's earned share is simple. Multi-entity management helps if you run more than one company. Altery is not a bank, and this is general information rather than advice.

Frequently asked questions