# Invoice rollout introduction email, annotated | SourceX

Canonical: https://refer.sourcex.si/resources/invoice-processing-rollout-introduction-email
Last updated: 2026-11-04

Send it only after the owner has opted in. The email names the record types the company described (rejected invoices with reasons, duplicate flags, mismatch resolutions), identifies the authorized contact, discloses your referral interest and asks only for a short conversation. Below is a draft with a subject line, three short paragraphs and one metadata-only ask, followed by a line-by-line annotation of why each sentence is there and what never goes into it.

It is part of the [invoice processing rollout guide for AP automation advisors](/guides/moment-invoice-processing-rollout-ap-automation-advisors). Most advisors send it straight after the closing block of the [rollout meeting agenda](/resources/invoice-processing-rollout-meeting-agenda).

## Three conditions before you open a draft

An introduction email closes a permission process. Check these first.

1. **The controller, CFO or owner said yes.** A nod in a steering meeting is not consent. If unsure, ask in one line: "Are you comfortable with me introducing you to SourceX?"
2. **You know who receives it.** The recipient must be able to authorize a licensing discussion, named with a title. The AP clerk who explained the workflow is not the right address, however helpful.
3. **Your partner agreement is signed.** The Channel Partner Agreement comes before any introduction is submitted.

Write in plain text that reads easily on a phone. No logos, attachments or tracking links. If you would be uneasy seeing it forwarded to the company's counsel, rewrite it until you would not.

## The draft

Illustrative. Adapt the bracketed parts; keep the order.

> **Subject:** Introduction: [Company] and SourceX, AP exception history before the rollout
>
> [Name], as discussed on [day], I'm introducing you to SourceX ahead of the move to [new AP tool]. You mentioned that [old ERP or capture tool] still holds rejected and held invoices with approver reasons, duplicate alerts and price-mismatch resolutions going back about [number] years.
>
> SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation and delivery. Nothing is shared by replying. For transparency: I am a SourceX referral partner, and if a qualifying license completes, SourceX may pay me a referral reward from its own funds. It is never deducted from anything the company receives.
>
> Would you be open to a 20-minute call with SourceX to describe what exists, roughly how much, and who owns it? No files are needed. [Your name]

## Annotation, line by line

| Line | Why it is there | What never goes in it |
|---|---|---|
| Subject | Names the company, SourceX and the moment, so the recipient can find it later | Dollar figures, "urgent", or the word "opportunity" on its own |
| "As discussed on [day]" | Shows the contact already agreed, so this is not cold outreach | A claim the owner agreed to more than a conversation |
| "Ahead of the move to [new AP tool]" | Ties timing to a documented event, the only legitimate urgency | An invented deadline or a guessed switch-off date |
| The record description | Repeats what the company said, in its terms: rejections with reasons, duplicates, mismatches, years | Supplier names, invoice amounts, quoted rejection reasons or screenshots |
| What SourceX does | One accurate sentence so the contact knows what they are being introduced to | Named buyers, promises of acceptance, or a value estimate |
| "Nothing is shared by replying" | Lowers the stakes and keeps discovery at metadata level | A request to send a sample or export |
| The disclosure | States your interest before any decision, in plain words | Reward amounts tied to this company, or wording that hides who pays |
| "Never deducted" | Answers the question every controller asks next | Any suggestion the reward reduces the company's payout |
| The ask | One action, sized small: a 20-minute description call | Access requests, logins or a second ask |

The middle paragraph carries the record description because it is what makes this company relevant. A rejected invoice records a human decision: in Dynamics 365 Finance, for example, the Workflow rejected status shows the reason the approver gave, and under three-way matching a price or quantity outside tolerance becomes a discrepancy that can require approval. You only need to say that such records exist, not what any of them contain.

## When the meeting answers were partial

Most real answers are mixed. Adjust one sentence rather than rewriting the email.

| What the company said | Change to the draft |
|---|---|
| Reasons are in approver emails, not the system | "Rejection reasons are partly recorded in the system and partly in approval emails." |
| Duplicate alerts sit with the capture vendor | Add: "The capture tool's subscription ends after cutover, so its history is time-bound." Use only a documented date. |
| A shared services provider runs AP | Add: "AP is run with [provider]; ownership of the history is to be confirmed." |
| Years covered are unknown | Replace the number with "several years, to be confirmed by [role]". |
| The owner wants counsel copied | Copy counsel and keep everything else unchanged |

If the [archive context checklist](/resources/invoice-processing-rollout-archive-context-checklist) marked items "at risk", say so factually in one clause. Do not turn it into pressure.

## What the recipient will be asked next

Set expectations honestly. SourceX will check fit: 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.

Demand for AP exception records, the rights review result, de-identification of supplier details and any offer all stay unknown until SourceX reviews the company. Partners never handle invoices or approval histories at any stage.

On your side, 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. The default reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap; Illustrative only, a $250,000 payout would mean a $62,500 reward. The [rewards page](/rewards) lists every condition. For a structured way to prepare, see the [introduction email builder](/tools/introduction-email-builder) and the [email preparation worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation); the [AP exception handling page](/data-types/accounts-payable-exception-handling-process) and the [back-office automation guide](/guides/ai-agents-back-office-automation-portfolio-companies) give context on why these records matter.

## 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 controller has opted in and you have a named recipient, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you send the email.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-invoice-workspace
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/three-way-matching-policies
