# Credit condition to cure record chain | SourceX

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

A lender connects credit-condition-to-cure records by carrying one key, normally the loan number, from the approval condition through the document request, each submitted evidence file and the reviewer's decision, to the satisfied, waived or open flag in loan servicing. Most hand-offs link cleanly. The chain breaks where evidence arrives from someone other than the borrower, such as a guarantor or parent company, and is filed under that party's name with no loan number attached.

This guide is part of the page for [bankers introducing a client opportunity](/guides/commercial-banker-introduce-client-opportunity), which applies when the company being introduced is itself a lender with its own credit team. Here the job is to follow one condition link by link and name what holds each link together.

## Five links from condition to cure

A credit approval sets conditions: an insurance certificate naming the lender as loss payee, a lien search, updated financial statements. Each condition then travels through five links before anyone can say it was cured.

1. **Condition to request.** The approved condition becomes a request for a specific document, assigned to the borrower or the relationship team.
2. **Request to evidence file.** Someone uploads a file; it lands in a document store.
3. **Evidence file to decision.** A credit analyst or closer accepts or rejects it, with a reason.
4. **Rejected file to replacement.** A new version arrives and goes through the same review.
5. **Decision to servicing flag.** Servicing records the condition as satisfied, waived or extended.

In the stack used here, links 1, 3 and 4 run in a CRM (Salesforce Financial Services Cloud, where the request is a document checklist item), link 2 lands in Box, and link 5 is in the loan servicing system. Salesforce's document tracking runs uploaded files through an approval process, and customers upload new versions of rejected documents, so the decision and the resubmission can both survive as records.

A link is strong when a structured key crosses it: an ID one system writes into another, or a loan number staff are required to enter. It is weak when the key is a name or a typed note. It is broken when only a person remembers it.

## Step, record, key and system: one condition traced (Illustrative)

A fictional 320-person equipment finance company approves a $2.4 million equipment line for a manufacturing borrower. The post-closing condition is an insurance certificate naming the lender. The borrower's parent company, which is the loan's guarantor and buys insurance for the whole group, supplies the certificate. All days, names and amounts are invented.

| Day | Step | Record | Key that crosses the link | System | Link strength |
|---|---|---|---|---|---|
| 0 | Condition set | Approval with insurance condition | Loan application and borrower account | CRM | Strong |
| 0 | Request created | Document checklist item from the opportunity | Borrower account and loan application | CRM | Strong |
| 12 | First submission | Certificate version 1, sent by the guarantor's broker | Folder named for the guarantor | Box | Weak: no loan number on the folder |
| 14 | Rejection | Item rejected: borrower not listed as named insured | Checklist item ID and approval history | CRM | Strong |
| 19 | Resubmission | Certificate version 2, same guarantor folder | Same file, new version | Box | Weak until the folder is linked |
| 20 | Acceptance | Item approved by the credit analyst | Checklist item ID | CRM | Strong |
| 21 | Cure recorded | Condition marked satisfied | Loan number | Loan servicing | Strong |

Read down the key column and the weak point is the document store. The request, decision and cure all carry the borrower's account or loan number. The two certificate versions carry only the guarantor's name. A reviewer starting from the loan number finds a request, a rejection, an approval and a cure, and no file to show what was judged.

## Where the chain breaks, and how a lender repairs it

**The file link (the weak link in the graphic).** The repair is a filing rule: the loan number in every folder or file name, or a metadata field on the file, whoever sends it. Where that rule exists, the link turns strong from the year it began.

**The account link.** In the CRM, the guarantor may have its own account. Financial Services Cloud can record a relationship between two accounts through the AccountAccountRelation object, which lets a reviewer move from the borrower to the party that supplied the evidence. A related problem arises when a deal is rebooked: Salesforce's documentation says a checklist item created from an opportunity keeps the account and loan application it was created with, and later changes to the opportunity do not update those associations automatically.

**The version link.** Box keeps prior versions up to a plan limit (for example 50 on Business plans and 100 on Enterprise, with admins able to adjust within those limits). If version 1 rolls off, the rejection reason points to a file nobody can open.

**The servicing link.** Some servicing systems keep only the latest status. A condition extended twice and then satisfied may show only "satisfied" with the final date.

| Weak link | Repair the lender may already have | Question that reveals it |
|---|---|---|
| Evidence filed under a guarantor | Loan number required in every folder or file name | "If a guarantor sends the certificate, where is it filed?" |
| Guarantor not linked to borrower | Account relationships recorded in the CRM | "Can your CRM show which guarantor accounts back which borrowers?" |
| Request stranded after rebooking | Open items re-associated when a deal changes entity | "When a deal moves to another entity, what happens to its open checklist items?" |
| First version rolled off | Version limit raised, or rejected files retained separately | "Could you open the first certificate a borrower sent in 2022?" |
| Status overwritten | Condition history with each change dated | "Does servicing show every extension, or only the final status?" |

## The questions that tell you whether the chain exists

A partner does not build this timeline and never handles a borrower file. Ask the lender's credit administration or operations owner three things, and write down the answers in their words:

- "For a condition from two years ago, could your team show who requested it, every file submitted, every decision and the date servicing marked it cured?"
- "Which identifier would you search on in each system?"
- "What changes when the evidence comes from a guarantor or parent rather than the borrower?"

An answer like "loan number on every folder since 2020, guarantor relationships recorded since 2022" tells SourceX which years read as joined chains. "We would have to ask the closer" is also useful, and honest. The companion [metadata packet](/resources/credit-condition-to-cure-metadata-packet) records the counts and owners, the [completeness checklist](/resources/credit-condition-to-cure-completeness-checklist) marks each break, and the [missing-context comparison](/guides/credit-condition-to-cure-missing-context) shows what a single export gets wrong.

## Who sponsors a lender introduction

The lender's CEO authorizes a licensing discussion and signs; the CFO or chief credit officer may sponsor it internally, and the CRM admin and records manager supply the facts. 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.

Every record in this chain describes a borrower, so rights, borrower privacy obligations and redaction stay open until SourceX reviews them with the company. For the covenant side of cures, see [equity cure rights](/questions/equity-cure-right); for lenders changing hands, [equipment finance company acquisitions](/guides/equipment-finance-company-acquisition); for the tools themselves, the [Salesforce](/systems/salesforce) and [Box retention](/systems/box-retention-policy-export) pages.

## 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's credit administration owner can name the key in each system and say where a guarantor's evidence is filed, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing their 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
