Skip to content

Deal economics

Supplier selected dataset payment terms: six triggers before cash

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

A supplier whose dataset is selected has passed a fit decision, not a payment trigger. Between selection and cash usually sit six events the signed terms must define: a fixed scope and amount, conforming delivery, an acceptance decision, a recorded closing, a valid invoice and a payment period. Map who controls each, find any link to someone else being paid, and commit internal effort, not outside spending, until closing.

License terms

Supplier selected dataset

This page covers supplier selected dataset payment terms: six triggers before cash.Illustrative

Key takeaways

  • Selected can mean shortlisted, chosen for a deal, accepted after review or closed; only the document behind the word tells you which.
  • Payment usually waits on six triggers: signed scope and amount, conforming delivery, acceptance, closing, a valid invoice and the payment period.
  • Most payment duties are switched on by conditions, so each triggering event needs a written definition, an owner and a deadline.
  • Check whether your payment depends on an intermediary being paid first; the clause, not the relationship, decides.
  • An invoice that misses a required item can stop the clock, so build the invoice checklist from the contract before closing.

What does it mean when your dataset is selected?

It means someone decided your records fit a need; it does not mean money is owed. Selection is a judgment about fit. Payment follows from events the signed terms define, and in most data licensing deals several of those events still lie ahead when the word selected first appears.

The decision this page supports is what a company should verify before it treats a selected dataset as income, plans spending against it or reports it to a board. The question is not whether the deal is good. It is which contract events still stand between the selection and cash, who controls each one, and what could stop it.

A useful answer needs three documents: the message or notice that used the word selected, the signed terms with their definitions of delivery, acceptance, closing and invoicing, and a list of every condition not yet met. Without the second, selection is still a conversation.

Four things selected can mean, and the document behind each

Selected can describe four different points in a deal, and each leaves a different amount of work and risk open. Ask which one the sender means and which document records it.

The costly mistake is reading the first row as the fourth. A shortlist decision made on a sample is often reported internally as a win, and a team that hears selected starts planning on a number the signed terms have not yet made payable. Read the rows in order:

Four things selected can mean, and the document behind each
What selected meansWho usually says itDocument that proves itStill open after it
Shortlisted on a sampleA buyer's or intermediary's data teamA message or evaluation noteTerms, delivery, acceptance, closing, invoice and payment
Chosen for a dealThe intermediary or buyer, in writingSigned terms fixing scope and amountDelivery, acceptance, closing, invoice and payment
Accepted after reviewThe party running the acceptance reviewA written acceptance decisionClosing, invoice and payment
ClosedBoth partiesA closing record or noticeInvoice and the payment period

The selection-to-cash trigger map

Map six triggers, each with its contract wording, its owner, what can still stop the money and the evidence to keep. A trigger the terms do not define is not a formality; it is the first question to send back.

Owners matter more than order. Two triggers sit mostly with the supplier, conforming delivery and a valid invoice, and two sit mostly with the other side, the acceptance decision and the payment run. The signed scope and closing need both. A deal whose open triggers all belong to the other side is one whose timing the supplier cannot plan, which is why the decision memo records who controls each. Use the map as written:

The selection-to-cash trigger map
TriggerWhat the terms must defineWho controls itWhat can still stop paymentEvidence to keep
Signed scope and amountRecords, fields, years, the amount and how it is calculatedBoth partiesScope narrowed before signingSigned terms and their version
Conforming deliveryFormat, volume, de-identification standard and delivery methodSupplierMissing fields, wrong period, failed checksDelivery manifest, checksums and transfer log
Acceptance decisionThe test, the reviewer, the review window and what silence meansLicensee or intermediaryFailed test, disputed defect, a review never runWritten acceptance or rejection with reasons
Closing recordedThe closing event and who records itBoth partiesAn unresolved defect or a missing rights documentClosing record or notice
Valid invoiceRequired invoice contents and where to send itSupplierA missing reference, wrong entity or wrong bank detailsInvoice copy and proof of receipt
Payment period and methodDays from which event, method, currency and deductionsPayerSet-off, holdback or dependence on another party being paidRemittance advice and bank record
A horizontal rail from selected to payment with six gates, signed scope, delivery, acceptance, closing, valid invoice and payment, each tagged with the party that controls it.
Selection starts the rail; six triggers stand before cash. Illustrative allocation of control.

Which conditions switch payment on, and which switch it off?

Most payment duties in data licensing are switched on by conditions: they take effect only when a defined event happens, such as acceptance or closing. A few are switched off by conditions, which end or reverse an obligation when an event occurs, such as a refund if a rights warranty proves false. Read the terms for both kinds.

The UNIDROIT Principles of International Commercial Contracts, a widely used restatement of contract rules, name the two types. Article 5.3.1 calls a condition suspensive when the contract or obligation takes effect only if a future uncertain event occurs, and resolutive when it comes to an end if the event occurs. Common law calls the same ideas a condition precedent and a condition subsequent.

Article 5.3.3 adds a rule that matters after selection: a party that prevents a condition from being met, contrary to good faith and fair dealing or the duty to cooperate, may not rely on its non-fulfilment. Do not lean on that principle. It helps only where the governing law or the contract adopts it, and proving bad faith is slow. Ask instead for terms that say what happens if a review is never run: a deadline, a deemed decision or a right to escalate.

Switch-off conditions deserve the same scrutiny, because they survive payment. A clawback tied to a rights warranty, a defect found later or a complaint about personal data can reverse money already received. List each one with the date it lapses.

When does the payment clock start, and what makes an invoice valid?

The clock usually starts at a defined event, such as receipt of a valid invoice after closing, and an invoice that misses a required item may not start it at all. Read the starting event, the period and the invoice requirements together, because each one moves the date.

U.S. federal procurement shows how precisely invoice validity can be defined. FAR 32.905 lists what a proper invoice must contain, including the contractor's name and address, the invoice date and number, the contract number, item descriptions, quantities and prices, payment terms and a contact for defective invoices, and it requires a billing office to return a defective invoice within 7 days with the reasons. Federal rules do not govern a private data license, but the discipline transfers: build the invoice checklist from your own contract before closing, not after a rejection.

Payment periods have legal ceilings in some places. In the EU, Article 3(5) of the Late Payment Directive (2011/7/EU) requires member states to ensure that a payment period fixed in a contract between businesses does not exceed 60 calendar days, unless expressly agreed otherwise and not grossly unfair to the creditor. That is a ceiling in one jurisdiction, not a promise in any deal; your signed terms set the period.

Sale-of-goods law also assumes inspection comes before payment. Article 58(3) of the UN Convention on Contracts for the International Sale of Goods says a buyer is not bound to pay until it has had an opportunity to examine the goods, unless the agreed delivery or payment procedures rule that out. A data license is not a sale of goods, but it borrows the logic: the acceptance review is the examination, and payment follows it.

Does your payment depend on someone else being paid first?

Check the payment clause for any link between your payment and an intermediary's receipts, because that link moves a risk you cannot see onto you. In a deal routed through an intermediary, the buyer pays the intermediary and the intermediary pays the supplier; whether the second payment waits for the first is a contract term, not an industry custom.

U.S. federal construction law shows the pattern in the open. Under 31 U.S.C. 3905, an agency's construction contract must require the prime contractor to include a clause in each subcontract obliging it to pay the subcontractor for satisfactory performance within 7 days out of the amounts the agency pays the prime contractor. The same section requires written notice, with the amount and the reasons, when the prime contractor withholds payment for a performance deficiency. That is a flow-through structure, written down, with notice duties attached.

A data license can go either way. Some terms make the supplier's payment independent of whether the buyer has paid the intermediary; others tie the two, openly or through phrases such as when received or to the extent collected. Ask the question in writing, quote the clause in your memo, and if payment is tied, ask who carries the buyer's credit risk and what happens if the buyer never pays.

The post-selection effort worksheet

Most of the work left after selection falls on the supplier, and it is small next to the work already done, but it decides whether the triggers the supplier controls happen on time. List each task with its owner and hours driver, then total the hours before committing anything beyond your own payroll.

At a glance

The post-selection effort worksheet

Illustrative: a 300-person freight brokerage hears that its load and claims records were selected. Its worksheet shows about 26 internal hours left: 6 hours to reconcile the selection with the signed scope, 8 hours to run and log the delivery, 5 hours of answers during the acceptance review, 3 hours to assemble the closing documents and 4 hours for finance to prepare a valid invoice and track the remittance. Every figure is invented to show the method.

  • Scope reconciliation: compare what was selected with the signed scope, field by field. Owner: deal lead. Hours driver: number of systems and fields.
  • Delivery run and log: export, transfer and record checksums. Owner: system owners. Hours driver: volume and number of systems.
  • Acceptance support: answer questions and fix defects inside the scope. Owner: system owners. Hours driver: defects raised.
  • Closing file: rights documents, approvals and the closing record. Owner: counsel or the deal lead. Hours driver: number of open conditions.
  • Invoice checklist: every content requirement in the contract, the right legal entity and verified bank details. Owner: finance. Hours driver: number of payment milestones.
  • Remittance tracking: match each payment to its invoice and note deductions. Owner: finance. Hours driver: number of payments.

Isn't selection the hard part, and the rest routine?

Often the rest is routine, but routine is not the same as certain. The fair version of the objection is that selection is the main filter: most datasets that fail, fail on fit, and a selected dataset in a well-run deal usually closes. Still, eligibility and indicative offers do not ensure selection, closing or any particular payout, and selection itself does not ensure the last two.

What keeps the remaining steps from being routine is that the conditions gather there. Acceptance can fail on a defect nobody saw in the sample, and closing can wait on a rights document. Rights documents are where buyers have learned caution: when MIT Media Lab researchers examined more than 1,800 text datasets (Nature Machine Intelligence, 2024), over 70% of those on widely used hosting sites had no license information, error rates topped 50%, and the correct licenses were often stricter than the labels.

So hold both views at once. Plan internal effort as if the deal will close, because it usually should. Plan outside commitments, such as hires, vendor contracts or loan covenants, only once closing is recorded.

The post-selection decision memo: plan, prepare or escalate

Close the review with a one-page memo that records which meaning of selected applies, which triggers remain and one of three decisions. Plan on the money when only the invoice and the payment period remain and the payment clause has no dependence on another party. Prepare, committing internal hours only, while delivery, acceptance or closing is still open. Escalate when a trigger is undefined, when payment depends on an intermediary being paid, or when a review has no deadline.

At a glance

The post-selection decision memo: plan, prepare or escalate

The memo covers one deal on one date, reports no study result and is not legal or accounting advice. Its next evidence is usually a document: a written acceptance, a closing record or a clause that answers a gap. Write the memo with these fields:

Checklist · 7 items

  1. The word selected as received: who said it, when and in which document.
  2. Meaning: shortlisted, chosen for a deal, accepted or closed, with the proof.
  3. Open triggers: each with its owner, its definition quoted from the terms and the next expected date.
  4. Dependence check: the payment clause quoted, and whether payment waits on another party.
  5. Reversal terms: clawbacks, set-off and holdbacks that survive payment, with their lapse dates.
  6. Effort committed and remaining, by owner, from the worksheet.
  7. Decision: plan, prepare or escalate, with the approver and the date.

0 of 7 ticked. Tick each item as you go.

Where selection, closing and payment are set when you license through SourceX

In the signed documents. SourceX's first step, a brief fit check on the company, needs no uploaded data to show whether it qualifies; it is not an offer, and it sets no payment. Each deal's signed agreement carries its exclusivity and term, and the company approves the scope and terms of that agreement and signs it before delivering any data.

SourceX describes its current selection, closing and payment steps on its how-it-works page and in its guide to selection and getting paid. Read those against your own documents, apply the trigger map to the signed terms, and treat the signed terms as the source wherever the two differ.

Frequently asked questions

Does selection mean my company will be paid?

Not by itself. Selection is a decision about fit; payment follows from events the signed terms define, usually delivery, acceptance, closing and a valid invoice. Ask which meaning of selected applies and which of those events are still open.

What is the difference between acceptance and closing in a data license?

Acceptance is the decision that a delivered dataset meets the agreed test. Closing is the event the terms use to complete the deal, often recorded in a notice, after which invoicing usually starts. Some deals combine the two, so read the definitions rather than assuming.

When does the payment period start after a dataset is selected?

From whatever event the signed terms name, often receipt of a valid invoice after closing, not from selection. Check the event, the number of days and the invoice requirements together, since a rejected invoice can push the date back.

Can a buyer delay payment by not finishing its review?

It can try where the terms are silent. Ask for a review deadline and a stated consequence, such as a deemed decision or an escalation right, rather than relying on general principles such as UNIDROIT Article 5.3.3, which help only where the governing law or contract adopts them.

Should a selected dataset appear in our forecast?

Report it by trigger status, not as income. A dataset with delivery, acceptance and closing still open supports planning internal effort; outside commitments should wait until closing is recorded and only the invoice and payment period remain.

Sources

  • UNIDROIT Principles 2016, Article 5.3.1 defines suspensive and resolutive conditions; Article 5.3.3 bars a party that prevents a condition in bad faith from relying on its non-fulfilment. Source
  • FAR 32.905 lists the contents of a proper invoice and requires a billing office to return a defective invoice within 7 days with the reasons. Source
  • Directive 2011/7/EU, Article 3(5): payment periods in contracts between businesses may not exceed 60 calendar days unless expressly agreed and not grossly unfair to the creditor. Source
  • CISG Article 58(3): a buyer is not bound to pay until it has had an opportunity to examine the goods, unless agreed delivery or payment procedures are inconsistent with that. Source
  • 31 U.S.C. 3905 requires federal construction subcontracts to oblige the prime contractor to pay subcontractors within 7 days out of agency payments, with written notice when payment is withheld. Source
  • The MIT Media Lab audit of 1,800+ text datasets (Nature Machine Intelligence, 2024) found license omission above 70% and error rates above 50% on popular hosting sites. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies