# Refer a client whose data rights need review | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-refer-a-client-whose-data-rights-need-legal-review
Last updated: 2026-11-04

Refer a client whose rights to its records are unclear the way you would refer any client, with two additions. The rights question goes to the company's own counsel and to the rights check SourceX runs while it qualifies a company, before any records are shared; you offer no view on it. Your own question, whether you may take part and be paid, goes to your board, society, employer or counsel. A one-page counsel handoff note, written from the CEO's own words, keeps the two questions apart and every contract out of your hands.

It is written for fractional CFOs, outsourced controllers and accounting practice leaders whose client has said "I'm not sure we're allowed to." Nothing here is legal advice about the client's records or conduct advice about you.

## Two legal questions that never share a lawyer

An introduction with unclear rights carries two questions that sound alike and are not. The company asks whether it may license its records. You ask whether you may introduce it, and whether you may accept SourceX's reward for doing so.

| Question | Whose question | Who answers it | What you contribute |
|---|---|---|---|
| Can the company license these records for AI training? | The company's | Its counsel, then SourceX's rights check | The handoff note, nothing more |
| Which records are in scope, and on what terms? | The company's | The CEO, in the company's signed agreements with SourceX | Nothing |
| May you take part in the introduction? | Yours | Your board, society, employer or counsel | Your facts: role, services, license, location |
| May you accept a reward, and what must you disclose? | Yours | The same adviser, reading your rules | SourceX's published reward facts |

SourceX's own conditions show why the company's question is real. Its screening page treats a company as holding the rights when it "owns the material, or can license it without breaching client confidentiality, employee privacy or third-party contracts". Its how-it-works page adds what a supplier confirms: lawful collection of personal data, no earlier AI-training license, and no data created or altered with AI for the sale. Each is a reading of the company's own documents, none is yours to make, and the sample Channel Partner Agreement grants a partner no data rights.

What the client gains from you is not an opinion. It gains a question worth asking, SourceX's published conditions so its counsel starts with the right documents, and a route SourceX opens with "A few questions, no files", sharing no records at that stage.

## Rights doubts as a CEO voices them, and where each one goes

Clients rarely say "we have a third-party contract problem." They say things like the sentences below. Each touches one published condition and has one owner.

| What the CEO says (Illustrative) | Published condition it touches | Who answers | Your next move |
|---|---|---|---|
| "Our customer contracts have confidentiality clauses." | Licensing without breaching client confidentiality | Company counsel, then SourceX's rights check | Note it in block D; read nothing |
| "Some of these are really our clients' files." | Client-owned material is usually not a fit | The CEO first, then SourceX | Note which records the CEO calls the company's own |
| "Support tickets carry staff names and messages." | Employee privacy | Company counsel | Note the system and record type only |
| "Our app collected customer personal data." | Personal data collected lawfully | Company counsel | Note it; never describe the data |
| "Half of it came with a business we bought." | Third-party contracts, the purchase agreement among them | Company counsel | Note the year and system; skip the deal terms |
| "Our hosting vendor's terms may limit what we take out." | Third-party contracts | Company counsel | Note the vendor as the CEO named it |
| "We licensed some of this to an AI developer last year." | Never before licensed for AI training | Nobody: that data is out | Say so; other records go to SourceX's review |
| "Parts were drafted with an AI tool." | Not created or altered with AI for the sale | The CEO, with counsel if unsure | Note it |

Two rows end differently. No closer legal reading brings back data already licensed for AI training, because the supplier confirms it never was. And client-owned material is among the screening page's usual poor fits, so the second row often narrows the talk to what the company created itself.

## The counsel handoff note

The note is one page. The CEO owns it, edits it and decides whether counsel ever sees it. You may offer the blank structure and fill the blocks that public facts and the CEO's words can fill. Nothing in it comes from a ledger, a file share, a contract or a system you can log into for the client.

| Block | What goes in | Who writes it | Never in it |
|---|---|---|---|
| A. Request | That the CEO asked for the note, the date and the reason, in one line | You, from the CEO's words | Your own view of the opportunity |
| B. What SourceX publishes | The rights conditions from the screening and how-it-works pages, quoted, with the date you checked | You | A paraphrase presented as SourceX's position, or any outcome |
| C. The records | Record type, system, years covered and who created them | The CEO | Samples, counts pulled from systems, screenshots |
| D. The doubt | Contract clauses, staff data, customer data, an acquisition, a vendor | The CEO | Your reading of any contract |
| E. Questions for counsel | One question per doubt, drawn from block B | The CEO, with your help on wording | Answers, or a guess at what counsel will say |
| F. Your role and any pay | Who may pay you, on what basis, that the company is paid the same either way, and where your own rules check stands | You | A claim of independence you have not checked |
| G. The CEO's decision | Apply now while counsel reads, counsel first, or not now | The CEO | A deadline you set to protect your credit |

Block E is where advisers overreach. It holds questions, never answers. The questions SourceX's published conditions raise, in plain words:

1. Which agreements or notices govern each record type the CEO listed in block C?
2. Do any of them limit how the company may reuse those records?
3. Was personal data in the records collected lawfully, and under which notice?
4. Has any of this data been licensed for AI training before?
5. Did the company create these records, or receive them from clients, a seller or a vendor?
6. Could the company give the confirmations SourceX lists if it signed today?

Block F answers counsel's question about you. Section 4 of the terms reads: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." So the company receives the same amount whether or not you are paid. If your adviser has not answered, block F says pending, never cleared.

Block G belongs to the CEO. SourceX runs its rights check during qualification, and only the signed Dataset Deal Confirmation fixes the dataset, payout, rights and deadlines, so some CEOs apply first and let both reviews run; others want counsel's view before any form.

## Your participation, independence and pay rules, by role

Unclear client rights do not change your rules. They tempt you to do more, and doing more is where restrictions bite. Three facts decide which rules reach you: the services you or your firm perform for this client, where you are licensed, and who employs you.

| Your position | Ask about this before you say a word | Who answers |
|---|---|---|
| Your firm audits or reviews the client's statements | Independence, and whether any part in an introduction is open to you | Your firm's independence function or ethics adviser |
| Licensed CPA giving tax or advisory services | Commission and referral-fee rules where you are licensed, and the disclosure they require | Your state board, society or counsel |
| Fractional CFO placed through a firm | The firm's policy on outside referrals and fees | Your firm, in writing |
| Outsourced controller with system access | Whether anything you know came through that access; if it did, it stays there | You, then your engagement partner |
| Unlicensed finance consultant | Confidentiality and conflict clauses in your engagement letter | Your own counsel |

Only the rule-maker's own text counts, and rule-makers differ. The AICPA's Code of Professional Conduct has a section numbered 1.520, Commissions and Referral Fees. California's Board of Accountancy, answering consumer questions, allows commission-based pay only in limited cases and adds that "a licensee still is prohibited from accepting any fee or commission solely for referral of a client to a third party." How either applies to you is your adviser's call. Audit clients start with [the engagement separation map](/guides/how-to-keep-a-data-introduction-separate-from-an-audit-engagement); commission rules by service are in [the applicable-rules checklist](/guides/before-an-accountant-accepts-a-referral-reward-check-the-applicable-rules), and the client's wording in [the reviewed client disclosure](/guides/the-client-disclosure-a-finance-advisor-should-review-before-referring).

## A paid route and an unpaid route, both approved by the CEO

Both routes begin in the same place: the CEO wants the conversation, holds the note and knows who may pay you.

**Paid.** You hold an approved partner account, signed the Channel Partner Agreement before submitting, and your adviser has answered on the reward. You submit; the company applies itself and describes its own records. SourceX credits the earliest valid introduction of the company, and only if the company files a verified application within 90 days of that recorded introduction; dated records settle it, never a click.

**Unpaid.** If your rules rule out a reward, or you would rather take none, the company can apply on its own with the note in hand and no partner named. If you still want to make the introduction yourself while taking nothing, write to SourceX first: the published terms say nothing about a declined reward, so its handling is SourceX's decision. [The unpaid introduction path](/guides/the-unpaid-introduction-path-for-a-finance-professional) sets out that order.

The company's compensation is identical either way, and on both routes the sample agreement bars a partner from committing SourceX to prices, licenses or payouts, so the note promises the client no term.

## A claims administrator's note before counsel reads it (Illustrative)

Illustrative, with a generic company and invented facts. A 230-person third-party claims administrator is run by its owner as CEO. At a quarterly review she tells her fractional CFO that the company keeps eleven years of adjuster notes and settlement letters in one claims system, then adds: "Our carrier contracts have confidentiality language, and I don't know if this is ours to license."

| Block | As filled |
|---|---|
| A. Request | The CEO asked on 14 October, after the quarterly review, for a note her outside counsel could read |
| B. What SourceX publishes | The rights conditions, quoted from the screening and how-it-works pages, checked 28 October |
| C. The records | Adjuster notes and settlement letters, one claims system, eleven years, written by the company's own staff, in the CEO's description |
| D. The doubt | Carrier contracts carry confidentiality language; some files name claimants |
| E. Questions for counsel | Six, drawn from block B, none answered |
| F. Your role and any pay | "SourceX may pay me if you license data; you would receive the same amount either way. My own adviser has not yet answered on the reward." |
| G. The CEO's decision | Blank until she decides |

The CFO opened no carrier contract, counted no files, asked for no sample and never called the records licensable. Three weeks later the CEO writes that counsel wants SourceX's own questions first, and asks to apply. Once the CFO's adviser has answered, she submits, and the company describes its records to SourceX itself.

## Where a counsel handoff note falls short

- **Counsel may take months.** The 90-day attribution window does not pause for legal review. Never hurry a CEO to protect your credit; if the window passes, it passes.
- **The note is not a rights review.** Only the signed Confirmation fixes what is licensed.
- **Earlier contact.** If the company has already exchanged email with SourceX, section 3 of the terms treats it as a duplicate, credited to no later partner.
- **Control.** In a wind-down, a receivership or a bankruptcy, the CEO may not be enough: whoever controls the estate decides, and the same caution applies to a deadlocked 50/50 ownership.
- **No outcome data.** Nobody has published how often a company with a flagged rights question goes on to license its records.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the CEO holds the note, wants the conversation and knows who may pay you, [register](/register), compare the company with [who qualifies](/who-qualifies) and read the [program terms](/terms) on credit and duplicates before anything is submitted; more finance-advisor workflows sit in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.dca.ca.gov/cba/consumers/enforcement-faqs.shtml
- https://pub.aicpa.org/codeofconduct/ethicsresources/et-cod.pdf
