This page covers the record you keep for yourself. It is not legal, tax or ethics advice; the rules questions go to your own adviser or professional body.
What a referral log has to prove, and what it never needs
A finance advisor already holds the books. That is why a referral log drifts: the trial balance is one click away, so it ends up attached "for context". The log exists to answer four questions about your conduct, and none of them needs a figure.
- Did the CEO agree before SourceX heard the company's name? SourceX's screening guidance treats an introduction made behind the decision maker's back as a poor fit.
- Did you check your rules first, and with whom?
- Did you tell the CEO who may pay you, and on what basis?
- What did you send, and when? Section 2 of the terms decides credit from dated records, including written introduction evidence, and says a link click alone does not decide it.
SourceX's sample Channel Partner Agreement sets the same boundary from the other side. Section 3.3 reads: "Each introduction record must identify the company, domain, Partner, opportunity, introduction method and timestamps." Section 4.2 adds: "This Agreement gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." And SourceX's how-it-works page says partners need not export, upload or describe confidential records.
The client's benefit is the reverse of the advisor's temptation. A CEO who hears about a licensing option from their accountant should be able to trust that nothing from the books traveled with the idea, not even into the accountant's own referral file.
The minimal client referral log, field by field
Fourteen fields. Every entry comes from a public source, from the CEO's own words or from something you did yourself.
| Field | What goes in | Where the entry comes from | Never in this field |
|---|---|---|---|
| 1. Row ID | Your own code, such as R-014 | You | The client's account or engagement number |
| 2. Company and domain | Legal name and website domain | Public sources | Entity details known only from the books |
| 3. Your role | Engagement type and start year, such as fractional CFO since 2023 | The heading of your engagement letter | Scope, fees or findings |
| 4. CEO | Name and title | Public sources or the CEO's signature | Personal contact details beyond a work address |
| 5. Fit facts as stated | Peak full-time headcount band and years trading, attributed to the CEO | The CEO's own words | Figures from payroll you run, ledgers or returns you prepared |
| 6. Rules check | Date, the body or adviser consulted, who answered, a one-line result | Your adviser or professional body | The adviser's memo, which lives in its own file |
| 7. Firm approval | Approver and date, or sole practitioner | Your firm | Other clients' names |
| 8. Route | Paid, unpaid or out, with the date chosen | Your decision after field 6 | An estimated reward |
| 9. Disclosure | Date the CEO was told who may pay you and on what basis, and your message | You | Anything the CEO replied about the company's finances |
| 10. CEO's yes | Date and the CEO's words, quoted | The CEO's reply | Forwarded threads that carry figures |
| 11. Agreement | Date you signed the Channel Partner Agreement, which comes before any submission | Your partner account | Anything else |
| 12. Submission | Date, method (portal or email) and the text you sent | You | Attachments of any kind |
| 13. Dashboard | Stage words and reward status as shown, with the date read | Your SourceX dashboard | Your own guesses about the review |
| 14. Close | Declined, stop request, no reply, duplicate or completed, with the date and the CEO's words where given | The CEO or the dashboard | Reasons you inferred |
Field 5 is where most logs go wrong. You may know the exact headcount because you process payroll, but the log records only what the CEO said, as the CEO said it, because the CEO decides what the company discloses; gathering those answers in the first place is covered by the metadata-only finance intake. Field 8 stays a word, never a number: section 5 of the terms calls portal and calculator estimates projections, not promises, and a log with an estimate column has become a forecast, the trap described in describing referral economics without forecasting.
Nine kinds of file the log never holds
- General ledger or journal exports
- Trial balances and close packages
- Financial statements, draft or final
- Tax returns, workpapers and anything a return was built from
- Bank, card and loan statements
- Payroll registers and headcount reports you prepared
- Receivables and payables agings, and customer or vendor lists
- Screenshots of, or logins to, any client system
- Samples, counts or extracts of records pulled for SourceX
Three sources explain the ban from different angles. The FTC's guide to protecting personal information states its scale-down principle plainly: "Keep only what you need for your business." AICPA's Code, paraphrased from its own text, treats client information as confidential unless it is available to the public, and notes that laws on client confidentiality may be stricter than the Code. If you prepare the client's returns, the IRS describes section 7216 (paraphrased) as a criminal provision limiting a preparer's disclosure or use of tax return information outside return preparation without the taxpayer's consent, except where the regulations allow. A log that holds none of that information never has to answer any of those questions. Section 4.4 of the sample agreement points the same way: "Partner must not collect or retain supplier dataset copies through the referral program without separate written authorization."
Before saving a row, apply one test: could someone reading it learn anything about the client's money, people or customers that the client has not made public? If yes, cut the entry back to the CEO's words or remove it.
Two things may be attached: your own outgoing messages (the disclosure, the submission text), and the CEO's reply, trimmed to the reply itself.
Rules to check before the first row: role, independence and pay
Field 6 is filled before field 9, and the answer depends on which hat you wear.
| Your role with the company | What the rules check has to cover | Who answers |
|---|---|---|
| Outside accountant for tax or bookkeeping | Your board's or professional body's rules on referral pay and confidentiality, in the jurisdiction where you are licensed | Your board, society ethics line or counsel |
| Your firm audits, reviews or performs other attest work for the company | Independence as well as pay, before anyone raises the subject | Your firm's ethics partner or counsel |
| Fractional CFO holding an officer title at the company | Your duties to the company as its officer, alongside any professional rules | Your counsel, and the company's own policy |
| Employee of a firm | Firm policy and approval, then the professional layer | Your firm's approver and ethics contact |
Jurisdiction changes the answer, so field 6 names the jurisdiction whose rules were checked. California shows how specific a rule-maker can be. Its Board of Accountancy regulations, paraphrased, say that where a licensee may accept a commission, the written disclosure is given at or before the recommendation, signed and dated by the client, states the amount or basis and that no commission may be taken solely for referring a client to a third party, and is kept for five years. A disclosure your adviser says you need lives in its own file, with field 9 pointing to it.
If the answer is an unpaid route, field 8 says unpaid and field 6 records who confirmed it. SourceX's published terms do not cover a partner turning a reward down, so tell SourceX in writing and log its reply; the decision on how that is recorded rests with SourceX. The unpaid introduction path and the client disclosure draft give the wording. If your firm holds an attest relationship, start with keeping an introduction separate from an audit engagement, and where a sister firm in your network is involved, the sister-firm workflow.
One row before and after the cut (Illustrative)
Illustrative. A generic 200-person distributor and an invented advisor; dates are examples.
| Field | Before: what crept in | After the cut |
|---|---|---|
| Fit facts as stated | "212 staff per our October payroll run; revenue from the Q3 close pack" | CEO: "about 200 full-time at our peak in 2019, and 14 years trading" |
| Attachments | Q3 trial balance, receivables aging, a screenshot of the vendor list | None besides the CEO's yes, trimmed to the reply |
| Rules check | "Asked a colleague; sounded fine" | 14 Oct, state society ethics line, named adviser: unpaid route only |
| Route | "Paid; calculator estimate noted" | Unpaid; SourceX told in writing on 15 Oct, reply logged |
| Dashboard | "Looks promising" | Stage words as shown, read 2 Nov |
Every deleted item was something the advisor knew only because of the engagement. The corrected row still answers all four questions in the first section.
Access, retention and the CEO who says stop
Keep the log in your own systems, never in a client portal or a shared drive the client can see, and limit it to you and your firm's approver. The FTC guide's retention advice, paraphrased, is to write down what you keep, how you secure it, how long and how you dispose of it; put that policy in the log's header, with the period your firm or adviser sets.
When a CEO says stop, fill field 14 with the date and the CEO's words and send nothing more. Keep the minimal row: it is the record that you stopped. Delete stray notes about the company that live outside the log, since a clean log beside a cluttered inbox protects nobody.
Where a lean log falls short
- It does not make a referral permitted. The log records the rules check; it cannot substitute for one.
- Some rules require their own records. A signed disclosure or a firm approval form is kept as the rule-maker or your firm requires, beside the log.
- Mailboxes keep copies. Threads with figures may survive in email long after the log is clean.
- It is evidence, not a verdict. SourceX decides credit from dated records, including its own, and a well-kept log does not override them.
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.
Set up the fourteen fields before your first conversation, then register, check the company against who qualifies and read the program terms so the route you log matches the rules you follow; related workflows are in the guides hub.