# Finance stack redesign intro email | SourceX

Canonical: https://refer.sourcex.si/resources/finance-stack-redesign-introduction-email
Last updated: 2026-11-04

Write to the owner or CEO, not to yourself as their finance lead, in three short paragraphs: which reconciliation types the team says keep the original variance and the approved fix, who decides and what SourceX does, and a written disclosure of your referral interest with a metadata-only ask. The draft below is ready to adapt; the annotation explains every sentence and lists what never goes in, from vendor names to sample workpapers.

This page is part of the [hub guide on reconciliation history](/guides/moment-finance-stack-redesign-fractional-cfos). It usually follows the 20-minute owner conversation, which has its own agenda linked at the end of this page.

## Conditions to meet before sending

A fractional CFO sits inside the client's finance function, which makes the introduction easy to make and easy to get wrong. Four conditions come first.

1. **Your engagement allows it.** Check your engagement letter and any professional rules that apply to you. If either restricts referral arrangements, resolve that before writing.
2. **The owner opted in after disclosure.** They agreed to an introduction knowing you may receive a reward. The email repeats that disclosure in writing.
3. **You are not the decision-maker.** Even if you sign checks for the company, the recipient is the CEO (in an owner-run company, the owner), who can authorize a licensing discussion.
4. **The partner agreement is signed.** The Channel Partner Agreement comes before any introduction is submitted.

The facts in the email should come from the controller and AP lead, as they described them in the meeting. Where you know the answer yourself from leading the project, phrase it the same way: as a description, not a figure taken from the ledger.

## The email

Illustrative. Bracketed placeholders are filled only with what the team described.

> **Subject:** Introduction: [Company] and SourceX, reconciliation history before the system change
>
> Hi [Owner name],
>
> As we plan the move from [old ledger] to [new ERP], the team confirmed that [vendor statement and three-way match] exceptions since about [year] keep the original variance, the investigation notes, the approval and the correcting entry, while [bank reconciliations] are signed off without commentary. The current plan carries [opening balances and open items] forward, and the old system stays readable until [date the company agreed].
>
> You can decide whether that history is worth a conversation with SourceX, which licenses approved business data directly from companies for AI training and evaluation and handles the agreement, rights review, data preparation, delivery and payout. I have not sent, copied or shared any ledger, workpaper or vendor file.
>
> As I mentioned when we spoke, I am a SourceX referral partner. If a qualifying license completes, SourceX may pay me a reward from its own funds; it never reduces what [Company] is paid. Would a 20-minute call with SourceX about which reconciliation types, which years and who controls them be useful before the old system closes?
>
> [Your name]

## Annotation: the reason for every sentence

Each row is one sentence. The right column is what to keep out.

| Sentence | What it does | Never include |
|---|---|---|
| Subject line | Names both parties and the record type in plain words | "Opportunity", amounts, or "data sale" |
| "As we plan the move from [old ledger] to [new ERP]..." | Grounds the email in the project the owner already approved | Implementation problems or budget figures |
| "...[vendor statement and three-way match] exceptions since about [year] keep the original variance, the investigation notes, the approval and the correcting entry..." | Answers the core question by naming reconciliation types and the four-part sequence | A specific variance, vendor, invoice number or amount |
| "...while [bank reconciliations] are signed off without commentary." | Shows you separated strong history from weak, which builds trust | Any judgment that the weak records are worthless |
| "The current plan carries [opening balances and open items] forward..." | Explains why the question is timely, using the company's own plan | Pressure, or a deadline the company did not set |
| "...the old system stays readable until [date the company agreed]." | Gives the real event that closes the choice | An estimated date |
| "You can decide whether..." | Hands the decision to the right person | Any statement that the company qualifies or will be paid |
| "...SourceX, which licenses approved business data..." | One accurate sentence about SourceX | Claims about buyers, pricing or demand |
| "I have not sent, copied or shared any ledger..." | Confirms the records stayed with the company | Anything suggesting you hold a sample |
| "As I mentioned when we spoke, I am a SourceX referral partner..." | Puts the earlier spoken disclosure in writing | The reward formula, or any hint that the company funds it |
| "Would a 20-minute call... before the old system closes?" | A small, metadata-only ask tied to the company's own date | A request for exports, logins, trial balances or workpapers |

### Why the email names the four-part sequence

A corrected reconciliation can look clean afterward, because a correction is often recorded as a new event. In NetSuite, for example, changing the amount of a previously reconciled transaction makes it unreconciled, and someone reconciles that statement period again. The variance, the investigation and the approval are what explain the correction, and they live in notes, attachments and approval logs. Naming all four tells the owner, and later SourceX, that the team checked for the reasoning, not just the result.

## Rewrites: risky sentences and their safe versions

Fractional CFOs know the numbers, which makes it tempting to use them. These rewrites keep the email at metadata level.

| Risky draft | Why it is a problem | Safe version |
|---|---|---|
| "We found a $1,840 variance with a vendor that shows exactly this." | Discloses a transaction and a counterparty | "Corrected exceptions keep the variance, notes, approval and entry." |
| "There are 4,312 exceptions in the AP module." | A count pulled from the ledger rather than given for sharing | "Several thousand exceptions over about [number] years, per the controller." |
| "This could be worth a lot to the right buyer." | An expectation nobody can stand behind | Leave it out |
| "I've attached the reconciliation summary." | Moves company records outside without authority | Leave it out; the company shares directly with SourceX if it applies |
| "SourceX's supplier payout would go to us." | Confuses the company's vendor payouts with SourceX's term | Leave the term out of the email entirely |

The last row is worth a note. SourceX's Actual Supplier Payout is what SourceX pays the referred company and is used only to calculate a reward; it has nothing to do with the company's own vendor payments. Keeping it out of the email avoids the confusion.

For other openings, the [introduction email builder](/tools/introduction-email-builder) helps, and the [email preparation worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) collects the facts first. The [finance tech stack inventory template](/resources/finance-tech-stack-inventory-template) is a good way to confirm the old and new system names.

## Recipient, fit and what remains for SourceX

Check fit before you send: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. 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. Cross-border clients often raise this; the [fractional CFO guide for U.S. companies from abroad](/guides/fractional-cfo-for-us-companies-from-abroad) covers that setting.

| Topic | What the email can say | What stays unknown until SourceX reviews it |
|---|---|---|
| Records | Reconciliation types and whether each keeps its reasoning | Whether buyers want those record types |
| Control | That the company holds them, or which third party does | The rights review, including vendor confidentiality |
| Authority | The CEO, or the owner who runs the company | What must be de-identified |
| Money | That any reward is funded separately by SourceX | Any offer to the company and any reward to you |

Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. There is no cap per referred company.](/rewards) confirms it never reduces the company's payment. The [20-minute meeting agenda](/resources/finance-stack-redesign-meeting-agenda) covers the conversation that comes before this email. If the archive dates are still unclear, finish the [finance stack redesign archive context checklist](/resources/finance-stack-redesign-archive-context-checklist) first. For the wider advisory picture, see [fractional CFO AI services](/guides/fractional-cfo-ai-services).

## 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.

If the owner has opted in and the draft names only reconciliation types and dates the team gave you, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you send it.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1552329.html
