This draft is part of the S/4HANA transition guide. Use it once the 25-minute meeting agenda has closed on "introduce now."
The S/4HANA email, ready to edit
Replace every brace from your meeting notes. Numbers in square brackets point to the margin notes below; delete them before sending.
Subject: [1] Exception history in {legacy_system} before retirement
Hi {first_name},
[2] Thank you for the session on {meeting_day}. Before {legacy_system} is retired, {retirement_reference}, a short follow-up. [3] We asked which exception decisions live in attachments and related workflows, and {ap_lead} and {quality_lead} named {process_list}, handled in SAP since {first_year}. [4] The transition scope covers {scope_answer}.
[5] SourceX licenses approved business data directly from companies for AI training and evaluation, and handles the agreement, rights review, data preparation, delivery and payout. Nothing leaves {company} unless you agree terms. [6] So you can weigh this properly: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX pays it separately, it never reduces what {company} would receive, and it is separate from our work on the transition.
[7] If you would like, I will introduce you. SourceX would begin with a description only: which processes, roughly how many years, which systems and repositories, and who can approve a discussion. [8] No documents, attachments or extracts. Reply "go ahead" or "not now."
{your_name}
SAPMargin notes for every line
| # | The line's job | What must stay out of it |
|---|---|---|
| 1 | Names the record layer and the event, so a forwarded email explains itself | "Opportunity", "monetize" or a figure |
| 2 | Links the timing to the company's own retirement decision | SAP's 2027 date presented as a deadline for the company |
| 3 | Repeats the meeting question word for word and credits the answer to named process owners | Document numbers, vendor names, amounts or your own assessment |
| 4 | Records what the load scope does with closed documents, as the migration lead stated it | Speculation about what the archive contains |
| 5 | One accurate sentence on what SourceX does | Claims about buyers, named AI labs, demand or pricing |
| 6 | Discloses your interest before any introduction, in plain words | "I may benefit" with no names, or the disclosure moved to a footer |
| 7 | Defines the first step as a description at metadata level | A request for exports, screenshots or repository access |
| 8 | Repeats the boundary and gives a two-word exit | Follow-up pressure, "limited window" or similar |
Line 2 deserves care. SAP supports Business Suite 7 core applications in mainstream maintenance through 2027, with optional extended maintenance from 2028 to 2030. That timeline explains why the company is moving; it is not the company's retirement date. Write the date or quarter the sponsor gave you, for example "planned for the quarter after go-live," or drop the reference.
Line 6 is plain on purpose. The FTC Endorsement Guides call for clear and conspicuous disclosure of a connection between an endorser and the seller that the audience would not expect and that could affect the weight they give a recommendation, and they treat the chance of payment as such a connection. Whether that framework reaches a private email is a matter for your advisers; writing it plainly removes the question.
Exception detail you leave for SourceX
An SAP integrator knows more about the client's exceptions than almost any outside party. The email uses almost none of it.
- No document identifiers. Invoice, purchase order and inspection lot numbers stay in SAP. The process name is enough.
- No attachment content. SAP's Generic Object Services let users attach PC documents to business objects; the email may say that approvals are "attached to the invoice," never what an approval says.
- No mechanics as proof. You may know that in SAP invoice verification a variance above the upper tolerance limit posts the invoice but blocks it for payment, with release as a separate step. Use that knowledge to ask good questions, not to describe this company's blocked invoices.
- No supplier or customer names. Attached documents often come from third parties, which is a rights review matter for SourceX and the company.
- No reward figures. The default reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, paid only after every condition in the terms is met. Quoting a number turns a disclosure into a pitch.
- No project leverage. Never link the introduction to change requests, rates or scope.
Rewrites by transition approach
Paragraph one changes most between clients. Use the row that matches what the sponsor said.
| What the meeting found | Replace sentence [4] with |
|---|---|
| New implementation, open items only | "The new system will carry open items; closed documents and their attachments stay in {legacy_system}." |
| System conversion | "The conversion carries documents forward; where attachments are stored after go-live is still being confirmed." |
| Selective data transition | "The selected scope covers {years} for {company_codes}; earlier years stay in {legacy_system}." |
| Older documents already archived | "Invoices before {year} are archived; {it_lead} is confirming whether attachments went with them." |
| Approvals mostly in email | Add to [3]: "Most approvals are recorded in email rather than on the document." |
Keep the replacement factual and attributed. If the sponsor wants a colleague to lead, address both and add one line naming who SourceX should contact. The introduction email builder helps assemble the placeholders, and the wealth advisor introduction email shows the same discipline in a different relationship.
Before you press send
Run four checks.
- 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.
- Agreement. Sign the Channel Partner Agreement before submitting any introduction.
- Recipient. The sponsor who opted in, with authority over the legacy system's content. Nobody from the client's wider project team.
- Open items. Anything the meeting left open goes to the archive context checklist, not into the email.
On "go ahead," submit the introduction through your partner account with the sponsor's details and your metadata notes, then step back; SourceX works with the company directly. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, one partner per company. On "not now," note the date and do not chase.
What remains unknown until SourceX reviews it: SourceX's current data needs for exception records, the rights review of attached third-party documents and any offer. If the sponsor asks how a reward works, point to the rewards page. 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. SAP partners with subsidiaries abroad will find more on SAP partner referrals.
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.
Before the draft goes to the sponsor, register as a partner, confirm the company on who qualifies and read the program terms, so your disclosure matches what you signed.