This guide is for fractional CFOs, outsourced accounting firms and practice leaders. Wealth advisers working under Regulation S-P should start with their own compliance team, and what to ask about finance workflows themselves is covered in assessing finance workflows without sensitive records. This page is about where each answer comes from.
The access trap: when you already know the answer
Most introducers have to ask. A finance professional usually does not, because the answers sit in systems they log into every week: payroll shows the headcount, the ledger shows how far back the history runs, the chart of accounts shows which tools the company pays for. The fastest way to "check fit" is to look. That is the trap.
What you see in the books reached you because the client engaged you. The AICPA Code of Professional Conduct, for one, sets out a Confidential Client Information Rule (section 1.700.001) and defines confidential client information as any information obtained from the client that is not available to the public (our paraphrase of a search excerpt from the Code). A headcount read off a payroll report fits that description as well as a bank balance does. Tax work has its own rule: the IRS's Section 7216 information center describes a criminal provision barring tax return preparers from knowingly or recklessly disclosing or using tax return information for unauthorized purposes, and says a preparer generally needs the taxpayer's written consent first, unless an exception applies (our paraphrase of a search excerpt). Whether either applies to you, and how, is a question for your own counsel or ethics adviser.
SourceX's side asks for nothing from the books either. Its screening page frames five fit questions that are "answered from a conversation with the relationship holder, never from files, samples or logins." Section 4.2 of the sample Channel Partner Agreement says it "gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems." Nobody collects data for SourceX; a company that applies describes its own records to SourceX directly.
Your role is to carry an idea to the CEO, not to assess the company
Three people do three jobs. You carry an idea to the person who can decide. The CEO decides; SourceX's screening page says "opening a licensing discussion and signing for the company fall to the CEO." SourceX assesses fit, rights and demand in its own review.
The client's gain from your part is a clean, early view of an option, from someone it trusts, without its records moving anywhere. That gain disappears the moment the screening runs through the books, because the client can no longer tell where the advice ends and the referral begins.
The metadata-only finance intake
Eleven fields. Each one is answered by the CEO, or by someone the CEO names, in a conversation held for this purpose, and the last field records that.
| # | Field | Ask the CEO | Never fill it from | Why |
|---|---|---|---|---|
| 1 | Entity holding the records | Which company employs the team and keeps the records? | Entity charts in your engagement file | The answer must be the company's own statement |
| 2 | The decider | The CEO's name, and whether they want a conversation | Org charts in payroll or HR systems | The CEO decides under the program |
| 3 | Peak full-time headcount | The CEO's figure and the year it peaked, contractors excluded | Payroll registers, benefits counts, reports you prepared | A correct number from payroll is still engagement information |
| 4 | Years of company-created records | A rough start year for each record family | Ledger history, archive listings | An estimate is enough at this stage |
| 5 | Record families, in words | For example, "close checklists and approval trails since 2014" | Samples, screenshots, exports | Descriptions only |
| 6 | Systems, by category | For example, "an ERP, a ticketing tool, a document library" | Your admin access or a system list given to you for the engagement | Categories, never logins |
| 7 | Client-owned material | Does any of this belong to the company's own clients? | Customer contracts you have read | Rights are settled in SourceX's review with the company's counsel |
| 8 | Location and language of the records | Where the company is, and what language its records are in | Filings by jurisdiction | Geography follows SourceX's published sentence |
| 9 | Earlier contact with SourceX | Has the company ever applied, held an account or traded email with SourceX? | Your vendor master or the client's inbox | Section 3 makes earlier contact a duplicate |
| 10 | Your role and pay route | Your own answer, settled with your adviser before field 1 | Not applicable: this field is yours | The client should know who may pay you |
| 11 | Source line | "Said by [the CEO], [date], for this introduction" | Any line reading "from the books" | It proves where every answer came from |
Field 8 rests on one sentence, quoted as published: Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What never leaves the engagement: trial balances and ledger detail; payroll registers; bank and card statements; tax returns and workpapers; customer, vendor and price lists; receivable and payable agings; contracts; system exports, screenshots and logins. None of it is needed, and none of it is a partner's to send.
Method note. The eleven fields are this page's design, built from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening page, the sample Channel Partner Agreement, the AICPA Code and the IRS's Section 7216 page, all read on 2026-10-28. They are not SourceX rules or legal advice, and they leave demand, record quality and any payout to SourceX's review.
When the CEO's figure and the books disagree
Sooner or later the CEO will say "about 60 at our peak" when you remember payroll at 46, or "records since 2012" when you know the ledger was migrated in 2017. Do not correct the CEO from the books. A correction drawn from engagement data is a disclosure of engagement data, even when it is helpful.
What you can do is suggest the CEO check the company's own figures before it applies, because SourceX will ask the company directly. The full-time count is the one that matters most: introduced companies need 50 or more full-time employees at peak, with contractors left out. Record the CEO's figure in field 3 with the words "CEO's estimate" and leave the reconciling to the company.
Rules that follow your role and your license
The intake keeps records out of the referral. It does not settle whether you may take part, or be paid. Those questions follow the services you perform and where you are licensed, and only your own adviser can answer them. Raise at least these:
- Tax preparation. If you prepare the client's returns, ask how Section 7216 bears on anything you say or use, and what consent it requires.
- CPA licensure and attest work. Ask how the AICPA Code's confidentiality rule and your state board's rules bear on you; an audit or review client raises the independence questions covered in keeping an introduction separate from an audit engagement.
- Jurisdiction. Rules on commissions and referral fees differ by state and country; checking the applicable rules before accepting a reward sets out the questions.
- Your firm. Many firms require approval before staff take part in any referral program.
On the program's side, a firm can be the partner: the sample agreement's party block names the Partner as "an individual, or entity type and jurisdiction." The published terms do not say how a firm's account relates to the personal accounts of its people; SourceX decides that.
Paid or unpaid, the client approves the route
Once your adviser has answered, offer the CEO one of two routes in writing.
- Paid. Say who may pay you and on what basis before asking anything else. Section 4 of the terms lets you add, accurately, that the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation," so the company receives the same amount either way. Sign the SourceX Channel Partner Agreement before you submit.
- Unpaid. The published terms do not address a partner declining a reward. SourceX decides how that works, so ask in writing before you tell the client; the unpaid introduction path sets out the order.
Either way the company applies itself and describes its own records. If the CEO hesitates, stop.
One fractional CFO's intake, start to finish (Illustrative)
Illustrative. The firm, client and figures are invented, and nothing here implies an outcome.
A fractional CFO firm serves a 140-person engineering consultancy. A staff accountant offers to "pull headcount from payroll and the GL start date so we know if it's worth raising." The engagement partner declines and first settles the firm's own position with its ethics adviser, who recommends the unpaid route; the firm asks SourceX in writing how that works. At the next monthly meeting the partner asks the CEO whether a licensing conversation would interest the company.
| Field | Entry |
|---|---|
| Entity holding the records | The operating company, per the CEO |
| The decider | The CEO; wants a conversation |
| Peak full-time headcount | "About 150 in 2023," CEO's estimate, contractors excluded |
| Years of company-created records | Project files since 2009, CEO's estimate |
| Record families, in words | Project files, design review notes, QA checklists |
| Systems, by category | A project system and a document library |
| Client-owned material | Some drawings belong to clients, per the CEO |
| Earlier contact with SourceX | None, per the CEO |
| Your role and pay route | Fractional CFO; unpaid, SourceX's written reply on file |
| Source line | Said by the CEO, 14 October, for this introduction |
The company applies itself. The firm sends SourceX nothing beyond the introduction, and the partner's knowledge of the payroll count never appears anywhere.
Where a records-free intake still leaks
- Attachments ride along. A forwarded thread can carry last month's board pack. Write new messages; never forward.
- Notes outlive the moment. An engagement-system note saying "payroll 46, worth raising" is a record drawn from the books. Keep the intake separate from the client file.
- Helpful staff. Juniors with system access are the likeliest to "just check." Tell the team the rule before the first conversation.
- Ranges are still data. A revenue band or "roughly 40% gross margin" helps nobody's fit check and comes straight from the books. Leave financials out entirely.
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.
With your adviser's answer on file and the intake filled from the CEO's own words, register as a partner, set the company beside the published screening profile and read the program terms before the client applies. More finance-advisor workflows sit in the guides hub.