Transcript
You've probably heard the promise of an upfront payment. In the published terms, upfront usually doesn't mean money at signing. It means one payment, made after the data is delivered, or after the buyer accepts it.
First, when the money actually moves, and which published claims you can check and which you can only take on trust.
Published terms name five events that can trigger payment: signing, delivery, acceptance, the buyer's own receipt of money, and each later sale or use.
Most buyers pay when a contract event happens, usually delivery or acceptance, and rarely at signing. One program states a wire on delivery. Another invoices only after acceptance. One states a fee at signing.
How long does it take? Published timing runs from under three weeks to about three months. Every one of those figures is the buyer's own claim, and no seller statement or filing confirms when any program actually paid.
Even one buyer's own pages can disagree. One line says it pays in full within thirty days of acceptance. The FAQ says up to thirty days to review, then payment within thirty days of invoicing. That's the difference between waiting one month or two.
Next, what happens between delivery and the money, and after it.
Here's how one set of master terms works. The buyer has thirty business days to reject. A delivery not rejected in that window is deemed accepted. Then comes the invoice. And the license only attaches after acceptance and payment.
A clawback lets a buyer recover money it already paid. In published seller terms, it's tied to how accurate your description was, not to how well the buyer's model performs.
One buyer states a refund if your data manifest is materially inaccurate, and that right survives acceptance. It also allows claims for latent defects within sixty days after acceptance.
Then there's the other direction. One buyer's kill clause forces deletion within thirty days. But trained models cannot be unlearned, and no refund term is stated. So deletion doesn't undo the training.
Third, the shape of the payment, and what's left of it when it arrives.
Payment comes in four shapes. A single fixed fee. Installments or milestones. A revenue share. Or an upfront fee combined with a revenue share.
Some buyers combine the two. One program states an upfront licensing fee at signing, plus a revenue share on downstream use. Another says its offers are typically an upfront cash payment plus a perpetual revenue share. That pays you early, and keeps you a stake in reuse.
One program's own example uses a typical share of twenty percent. Apart from that, none of the four programs that state a revenue share publishes a split. And the share pays only on later sales you don't control.
No structure is safe by default. A fixed fee caps your upside. A revenue share defers it, and can pay nothing. And both depend on terms signed before any money moves.
Fixed doesn't always mean guaranteed. In one filed deal, the buyer may end a multi-year schedule of fixed payments on twelve months' notice. And on a marketplace, your pass-through payment depends on the buyer's customer paying first. Check who can end the deal, and when.
The money arrives by bank wire or through a payment processor. And the price can shrink, through an intermediary's fee or tax withheld at source. Marketplaces add a wait: one pays you within fifteen days of the buyer's payment.
Get six answers in writing, in the order form. Which event triggers payment? How long is the acceptance window, and does silence count? How many days pass before the money? Is the price fixed, milestone based or a share? On what grounds can money be clawed back? And who bears fees and tax withheld?
Now, tax. And a note first: this is information, not tax advice.
A buyer paying a royalty across a border often has to deduct tax before the money leaves. A US payer withholds thirty percent of US-source royalties to a foreign corporation. The UK rate is twenty percent, and Canada's is twenty-five.
Where does the income count as coming from? A royalty is sourced where the data is used. So training in the United States makes the license income US-source, even when the seller is abroad. That's what pulls a foreign seller into the withholding rules.
A tax treaty can cut that rate, even to zero. But it depends on whether the payment counts as know-how or as copyright. Italy goes from eight percent to zero. Egypt goes from thirty percent to fifteen. Check the treaty text before you rely on any rate.
A foreign seller claims the treaty rate with the W-8BEN-E. It stays valid until the last day of the third succeeding calendar year. A wrong income code on that form is a listed risk. And a US payer reports royalties to US persons on Form 1099-MISC.
VAT works differently. It follows where the customer is. For a business customer in another EU country, the customer accounts for it, under the reverse charge. A business outside the EU is outside EU VAT. Consumers follow other rules.
Put the tax questions in writing before you sign. Which category does the payment fall under? Where will the data be used? Which party withholds, and at what rate? Who accounts for VAT? And who bears the tax if the rate turns out wrong?
The tax page says it plainly. It's information, not tax advice, and you should consult a tax adviser before signing. So take those questions to a professional.
Last, the accounting. This is a different question from tax: when does the revenue count in your books, and how does the archive itself appear there?
Accounting asks what you promised. Continuing access, say to data you keep updating, is recognized over the license term. A fixed copy, delivered once, is recognized when it's made available. Whether the buyer gets updates or only a fixed copy is a question for your auditor.
You can see both patterns in annual reports. A big social platform says its licensing revenue is generally recognized ratably, over the license period. An image library says its data deals typically recognize a greater portion up front.
One stock media company's latest quarterly report shows its data, distribution and services revenue down seventy-six percent from a year earlier. It ties the change to delivery timing. Point-in-time recognition makes revenue lumpy, and that's one filing, not a forecast.
A revenue share gets its own accounting rule. It's recognized only when the buyer's later sale or use happens, or when your own obligation is satisfied, if that comes later. In a combined deal, the fixed fee follows the access or use test, and the share follows that exception. The percentage has to come from the contract.
Cash and revenue run on different clocks. Cash can arrive before revenue, or revenue before cash. One stock media company reports about fifty-one million dollars of unbilled receivables, which is revenue recognized before the invoice.
Does your data archive sit on your balance sheet? Under the international rule for intangibles, internally generated customer lists and similar items aren't recognized, so your own records usually carry no book value. The price comes from the market, not the books.
Selling the data outright is different from licensing it. That's a derecognition, and the gain shall not be classified as revenue. Which standard applies to an archive that was never recognized isn't settled by any text on the page. Ask your auditor.
So, in one line. Know which event triggers your payment, get the acceptance and clawback terms in writing, expect tax withheld at source, and ask your auditor when the revenue counts. And remember, deciding not to sell is a valid outcome too.
Next up is lesson A9, When to say no, and spotting scams.
Read and watch the full lesson free. Enter your email to unlock every lesson of the academy.