From email to ERP: the decision context a single-system export leaves behind

Short answer

Usually the reason. A single-system export keeps what changed, who approved it and when. It loses why: the supplier email that explained a shortage, the chat where a planner weighed the options and the approver's written rationale. In a purchase-order exception, the ERP shows a quantity cut and a price rise; the email and chat show the decision. Partners who can describe, at metadata level, where both halves sit give an owner a more accurate picture before any introduction to SourceX.

Visual briefFull-size diagram
Swimlanes for email, chat, ERP and accounts payable show seven timestamped events in one purchase-order exception; the ERP and payables events are kept in an ERP-only export, while the supplier email, planner chat and CFO approval email are marked as lost.
Illustrative purchase-order exception. Four of seven events survive an ERP-only export; the three that explain the decision do not.

What decision context can be lost when only one business system is exported?

Three kinds, in most exceptions. The trigger: the outside event that started it, usually arriving by email or phone. The deliberation: options weighed, often in chat or a meeting. The rationale: the reason an approver gave, often a one-line email reply. Systems of record are built to store the outcome of a decision as structured fields. They are not built to store the conversation that produced it.

ERP systems do keep more than the final state. In Microsoft Dynamics 365 Supply Chain Management, for example, changing an approved purchase order under change management sends it back to Draft for re-approval, and each confirmation creates a journal with a snapshot of the confirmed order, so earlier versions can be viewed. Three-way matching then checks invoice prices against the purchase order and invoice quantities against product receipts. That is a well-documented trail of what happened. It still does not say why the buyer accepted a partial delivery at a higher price.

A joined purchase-order exception

Illustrative: a 450-person food packaging manufacturer, one purchase order, fictional timestamps and references. The last column is the question that matters.

TimeSystemRecordJoining referenceKept in an ERP-only export?
Mar 2, 09:14ERPPO-4471 approved: 12,000 units of filmPO numberYes
Mar 4, 16:02EmailSupplier: resin shortage, 9,000 units now, price up 6%PO number in subject, message IDNo
Mar 4, 17:30Team chatPlanner: 9,000 covers two weeks; a second supplier needs requalificationNone; mentions "the film order"No
Mar 5, 08:45ERPChange requested: quantity 9,000, price up 6%; order back to DraftPO number, versionYes, as new values only
Mar 5, 11:20EmailCFO replies: approve, line-down risk outweighs the priceReply in the same threadNo
Mar 19, 14:05ERPProduct receipt: 9,000 unitsPO lineYes
Mar 21, 10:40Accounts payableInvoice matched to the revised order and receipt; releasedPO line, receiptYes

Read the ERP rows alone and you learn that a quantity fell by a quarter, the price rose and someone re-approved it. Add the other three rows and you learn the cause (a resin shortage), the alternative rejected (requalifying a second supplier), the constraint (two weeks of production) and the rule the approver applied (line-down risk outweighs price). That cause, options, decision and outcome sequence is the context AI developers describe needing, and it is the part an ERP-only export removes.

Joining is possible only where references survive. Email systems carry identifiers that help: a Microsoft Graph message includes a conversationId and an internetMessageId in the standard Message-ID format. The chat row shows the usual weak point, a message that refers to "the film order" with no number at all. The guide to workflow context instead of isolated files covers the general idea; this page is about the specific loss at the system boundary. The Model Context Protocol explainer is useful background on why AI tools increasingly read across several systems at once.

Questions a partner can ask without seeing records

Stay at metadata level. These questions describe where context sits; they do not require opening a single record.

  1. When a purchase order, quote or invoice goes wrong, where does the conversation happen: email, chat, phone, a ticket?
  2. Do people put the order or document number in subject lines or tickets, by habit or by rule?
  3. How far back do the ERP's change history and the mailboxes go, and are they under the same retention policy?
  4. Who owns each system, and who could authorize a discussion about licensing records from more than one of them?

Exceptions in procurement and payables are where this shows up most clearly; see procurement and vendor workflows and accounts payable exception handling. Email-heavy companies should also read operational communications, and companies that write decisions down formally may hold decision records that close the gap without email at all. ERP partners will find the role-specific angle in recognizing cross-functional operating knowledge.

Who owns cross-system records, and what stays unknown?

The company owns its ERP, mailbox and chat records, but each carries different obligations. Mailboxes and chat contain employees' and suppliers' words, so privacy notices, employee policies and supplier contracts matter more than they do for ERP fields. Those are questions for the company's counsel. The person who can authorize a licensing discussion is the CEO (in an owner-run company, usually the owner), not the ERP administrator or the mailbox owner.

QuestionUsually answered byWhat stays unknown until SourceX reviews it
Which systems hold the trigger, deliberation and rationaleOperations, finance or IT leadWhether the joined records match current dataset demand
Whether references survive across systemsIT or ERP administratorHow much can be joined after preparation
Privacy and contract limits on email and chatThe company's counselThe outcome of SourceX's rights review
Who can authorize a discussionCEO, often the ownerAny offer, its terms and timing

Eligibility is on who qualifies: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Partners never request or handle raw records; SourceX manages agreement, rights review, data preparation, delivery and payout directly with the company.

On rewards, the company's compensation and the partner's reward are separate payments, both from SourceX. The default reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months pay 15%. It never reduces what the company receives. Illustrative only, not a promise of earnings: a $400,000 payout would mean a USD 70,000 reward (USD 50,000 plus 5%, which exceeds 15%). 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. Partners sign the Channel Partner Agreement before submitting introductions. More guides are in the guides hub.

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 a client's exceptions leave a trail across email, chat and the ERP that its owner could describe and may want to license, register as a partner, check the company against who qualifies, and read the program terms first.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

Is an ERP export worthless without the email?

No. It records what happened, in order, with approvers and timestamps, which is useful on its own. What it usually lacks is why: the alternatives considered and the reason a person gave. Whether a given archive is useful is decided in SourceX's review.

Do mailboxes have to be included for a company to qualify?

No. Many companies will not want to license email, and that is their decision with their counsel. The point is to describe honestly where the decision context sits, so nobody overstates what a single system holds.

How would anyone join email to ERP records?

Usually through a shared reference, such as a purchase order number in a subject line, plus timestamps and thread identifiers. That joining work, if a company proceeds, happens under its agreement with SourceX, not by the referral partner.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/p…
  3. learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/p…
  4. learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/a…
  5. learn.microsoft.com/en-us/graph/api/message-get

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment