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.
| Time | System | Record | Joining reference | Kept in an ERP-only export? |
|---|---|---|---|---|
| Mar 2, 09:14 | ERP | PO-4471 approved: 12,000 units of film | PO number | Yes |
| Mar 4, 16:02 | Supplier: resin shortage, 9,000 units now, price up 6% | PO number in subject, message ID | No | |
| Mar 4, 17:30 | Team chat | Planner: 9,000 covers two weeks; a second supplier needs requalification | None; mentions "the film order" | No |
| Mar 5, 08:45 | ERP | Change requested: quantity 9,000, price up 6%; order back to Draft | PO number, version | Yes, as new values only |
| Mar 5, 11:20 | CFO replies: approve, line-down risk outweighs the price | Reply in the same thread | No | |
| Mar 19, 14:05 | ERP | Product receipt: 9,000 units | PO line | Yes |
| Mar 21, 10:40 | Accounts payable | Invoice matched to the revised order and receipt; released | PO line, receipt | Yes |
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.
- When a purchase order, quote or invoice goes wrong, where does the conversation happen: email, chat, phone, a ticket?
- Do people put the order or document number in subject lines or tickets, by habit or by rule?
- How far back do the ERP's change history and the mailboxes go, and are they under the same retention policy?
- 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.
| Question | Usually answered by | What stays unknown until SourceX reviews it |
|---|---|---|
| Which systems hold the trigger, deliberation and rationale | Operations, finance or IT lead | Whether the joined records match current dataset demand |
| Whether references survive across systems | IT or ERP administrator | How much can be joined after preparation |
| Privacy and contract limits on email and chat | The company's counsel | The outcome of SourceX's rights review |
| Who can authorize a discussion | CEO, often the owner | Any 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.