# Loan condition export missing context | SourceX

Canonical: https://refer.sourcex.si/guides/credit-condition-to-cure-missing-context
Last updated: 2026-11-04

A single-system credit-condition-to-cure export loses the story around the decision. A Salesforce Financial Services Cloud export can show a checklist item and its approval steps, but not the evidence file itself, the servicing outcome, or a cure recorded under a related borrower's account. Read alone, a condition the lender cured on time can look rejected and still open. The missing context lives in the document store, in servicing and in the links between related accounts.

This page belongs to the guide for [bankers introducing a client opportunity](/guides/commercial-banker-introduce-client-opportunity), for cases where the company being introduced is itself a lender. It reads one fictional condition twice: first as the CRM export shows it, then with the surrounding records restored.

## Before: the condition as the Salesforce FSC export shows it

Illustrative. A fictional 280-person commercial equipment lessor funds a press line installed at a borrower's leased plant. The approval carries a post-closing condition: a landlord waiver, so the lessor can reach the equipment if the borrower defaults. A reviewer receives a Salesforce FSC export of document checklist items, filtered to the borrower's account. Every value is invented.

| Field in the export | Value |
|---|---|
| Account | Borrower holding company |
| Checklist item | Landlord waiver, due day 45 |
| Created | Day 0, from the opportunity |
| Status history | Submitted day 22, rejected day 26 |
| Rejection note | "Waiver unsigned by landlord" |
| Current status | Rejected |
| Loan application | Original application number |

### What a reader concludes from the export alone

1. The lessor asked for a landlord waiver at closing.
2. The borrower sent an unsigned draft, and the lessor rightly rejected it.
3. Nothing was approved afterward; the item is still rejected, well past its due date.
4. Conclusion: the lessor funded a $1.6 million press line and never secured access to it. A control failure.

Each fact is accurate. The conclusion is wrong.

## After: the same condition with its context restored

Restore two more systems, and the relationship between two accounts, and a different sequence appears. Same fictional lessor, same invented values.

- **Day 30, CRM.** The deal is rebooked from the holding company to its operating affiliate, which holds the plant lease. A new checklist item for the waiver is created on the affiliate's account. The original item stays where it was.
- **Day 41, Box.** A signed waiver arrives in the loan folder as version 2 of the same file; the unsigned draft remains as version 1.
- **Day 42, CRM.** The new checklist item on the affiliate's account is approved by the credit analyst.
- **Day 44, servicing.** The condition is marked satisfied against the loan, now booked to the affiliate.

Now the reader concludes the opposite: the lessor caught an unsigned waiver, followed the lease to the right entity, obtained a signed copy and recorded the cure a day before the deadline.

Salesforce's documentation explains how the first reading happens. A checklist item created from an opportunity is associated with that opportunity's account and loan application, and later changes to the opportunity's account or loan application do not update those associations automatically. So when a deal moves entities, the original item can be stranded, and an export filtered to one account cannot see the replacement. Financial Services Cloud can record the link between the two accounts through its AccountAccountRelation object; if the lessor recorded it, a reviewer can follow the cure. If not, the link lives in a closer's memory.

Box adds a second dependency. It keeps prior file versions up to a plan limit (for example 50 on Business plans and 100 on Enterprise), so the unsigned draft is probably still beside the signed waiver. That pair, rejected and accepted, is the evidence of judgment. Salesforce's document tracking supports exactly this pattern, routing uploads through an approval process and accepting new versions of rejected documents, but the file contents live in the document store, not the CRM export.

## What the CRM export drops, and which team holds it

| Lost context | CRM export alone shows | Where it lives | Usual owner |
|---|---|---|---|
| The condition was cured | Rejected, past due | Servicing condition record | Servicing manager |
| What the borrower actually sent | A status and a note | Document store, by version | Records manager or IT |
| The unsigned draft beside the signed waiver | Nothing | Box version history, if not rolled off | Records manager |
| The deal moved to an affiliate | Nothing on this account | Opportunity history and the affiliate's account | CRM admin |
| Who approved the cure | Nothing on this account | Approval on the affiliate's checklist item | Credit analyst or closer |
| Why the affiliate was the right party | Nothing | Lease and entity records in the credit file | Credit officer |
| The cure date against the deadline | Nothing | Servicing, day 44 against day 45 | Servicing manager |

| Question a reviewer asks | CRM export answers it? | Connected history answers it? |
|---|---|---|
| Was the condition cured? | Looks like no | Yes, day 44 |
| What was wrong with the first submission? | Yes, unsigned | Yes, and the signed version exists |
| Which entity supplied the cure? | No | The operating affiliate |
| Who decided? | Only the rejection | Credit analyst, day 42 |
| Was there a control failure? | Looks like one | No |

Two patterns stand out. The context that reverses the conclusion sits in servicing and on another account, not in a missing field. And whether a reviewer can find it depends on habits: recording account relationships, naming folders by loan number, keeping file versions. For how each key carries across the chain, see the companion [record-chain guide](/guides/credit-condition-to-cure-record-linkage); the [completeness checklist](/resources/credit-condition-to-cure-completeness-checklist) marks those habits pass, partial or fail.

## Why the reasoning is what makes the records useful

A servicing export that says "satisfied, day 44" is a fact. The connected history is a worked decision: what was asked, what came back, why it was rejected, how the team found the right entity, and who signed off. Decisions recorded with their reasoning are the kind of context described in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training), and the same discipline appears in a [data audit](/proof/what-is-a-data-audit).

A partner never sees any of these records. Ask the lender's CRM admin and servicing manager three questions at metadata level: what happens to open checklist items when a deal is rebooked, whether account relationships are recorded, and whether servicing keeps each status change or only the latest. For the covenant side of cures, see [equity cure rights](/questions/equity-cure-right).

The lender's CEO authorizes a licensing discussion, often with the CFO or chief credit officer sponsoring it internally. The company should have 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. Borrower privacy obligations, redaction, which years matter and the company's payment stay open until SourceX reviews them. The companion [metadata packet](/resources/credit-condition-to-cure-metadata-packet) shows what the partner can record in the meantime.

## 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 lender can say where a cure is recorded when the borrower entity changes, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the sponsor.

## Sources

- https://refer.sourcex.si/terms
- https://developer.salesforce.com/docs/atlas.en-us.financial_services_cloud_admin_guide.meta/financial_services_cloud_admin_guide/user_create_dci.htm
- https://help.salesforce.com/s/articleView?id=sf.admin_doc_mgmt_overview.htm&language=en_US&type=5
- https://developer.salesforce.com/docs/atlas.en-us.financial_services_cloud_object_reference.meta/financial_services_cloud_object_reference/fsc_sforce_api_objects_accountaccountrelation.htm
- https://support.box.com/hc/en-us/articles/360043693454-Adjusting-the-Number-of-File-Versions-to-Preserve
