This resource belongs to the guide for bankers introducing a client opportunity, for cases where the client being introduced is itself a lender. Fill in the companion metadata packet first; the scorecard then tests how much of that trail holds together.
Scoring: two, one or zero per check
Ask each question of the person named in the "who answers" column. Mark what you hear:
- Pass, 2 points. The habit or field exists, and the owner can name the year it began.
- Partial, 1 point. It exists for some years, some products or some teams, or depends on a closer's memory.
- Fail, 0 points. It does not exist, or nobody can say. Unknown is scored as fail until someone confirms otherwise.
Six checks give 12 points. Write one sentence per check that is not a pass, naming the years or products it affects. Those sentences are what you hand to SourceX.
Six checks on the condition trail
| # | Check | Metadata question | Who answers | Pass | Partial | Fail |
|---|---|---|---|---|---|---|
| 1 | Coverage | Since when can a closed condition be found in each system? | Credit administration head | Five or more years in CRM, document store and loan system | Years exist but one system starts later, or tracking was in spreadsheets | Under two years, or unknown |
| 2 | Loan number key | Does the same loan number appear in all three systems? | CRM admin and records manager | Same loan number on checklist items, folders and servicing | Mapped through one documented lookup | Folders named by borrower only |
| 3 | Dated steps | Are upload, decision and satisfaction each dated? | Servicing manager | All three dated and kept | Decision and satisfaction dated, uploads not | The loan system shows only the last change |
| 4 | Versions kept | Is a rejected file kept beside the accepted one? | Records manager | Versioning on, limit known and adequate | Versioning on, limit unknown | Each upload overwrote the last |
| 5 | Outcome recorded | Is every condition closed as satisfied, waived or extended, with a reason? | Credit administration head | Outcome and reason required | Outcome recorded, reason optional | Conditions can silently drop off |
| 6 | Related borrower | When a parent or sister entity supplies evidence, or a deal is rebooked, is the link recorded? | CRM admin | Account relationships recorded and checklist items re-associated | One of the two, or only for some products | Not recorded |
What the vendor documentation says about checks 2, 4 and 6
Check 4 has a concrete setting behind it. Box keeps a plan-dependent number of prior file versions (for example 50 on Business plans, 100 on Enterprise and unlimited on Enterprise Plus), and admins can adjust it within plan limits. The records manager can read that setting without opening a file. Salesforce's document tracking routes uploads through an approval process, and customers upload new versions of rejected documents, so where the lender used it, the rejection can survive in the CRM even if the file version rolled off.
Check 6 also has a documented cause, covered next.
The related-borrower test
Ask the CRM admin one question: "When a deal moves from a holding company to an operating affiliate before its conditions are cured, what happens to the open checklist items?"
Salesforce's documentation explains why the answer matters. A document checklist item created from an opportunity is associated with that opportunity's account and loan application, but later changes to the opportunity's account or loan application do not update those associations automatically. So the evidence request can stay on one account while satisfaction is recorded against another. Financial Services Cloud can record a relationship between two accounts through the AccountAccountRelation object. Whether the lender used it, and from when, decides the mark.
- Pass. "We re-associate open items on rebooking, and we record account relationships between parents, affiliates and obligors since 2021." The trail holds from 2021.
- Partial. "We record parent-affiliate relationships, but nobody moves open items." Related-entity cures can be reconnected, with effort.
- Fail. "The closer would know." The chain exists only in memory for any condition that crossed entities.
None of these rules a lender out. Each tells SourceX how much reconnection a review would need.
A scored lender (Illustrative)
A fictional 230-person specialty finance company lending to franchise operators, scored in a call with its head of credit administration, CRM admin and servicing manager. Every answer is invented.
| # | Check | Answer heard | Mark | Points |
|---|---|---|---|---|
| 1 | Coverage | CRM since 2022, document store since 2016, servicing since 2013 | Partial | 1 |
| 2 | Loan number key | Loan number on folders since 2019, borrower names before | Partial | 1 |
| 3 | Dated steps | Upload, decision and satisfaction all dated in history | Pass | 2 |
| 4 | Versions kept | Versioning on; the records manager confirmed the limit has never been reached | Pass | 2 |
| 5 | Outcome recorded | Waivers need a reason since 2022; extensions do not | Partial | 1 |
| 6 | Related borrower | Franchisee affiliates common; no account relationships recorded | Fail | 0 |
| All | Total | Six checks scored | Sum | 7 of 12 |
The sentence that goes into the introduction: "Condition trail joinable by loan number from 2019 with dated steps and kept versions; waiver reasons from 2022; affiliate cures not linked in the CRM." That sentence lets SourceX scope a review. The score just helps you remember it.
For the general practice of judging records before anyone reads them, see what a data audit is. The record-chain guide follows one condition key by key, and the missing-context comparison shows how a related-borrower cure can look like a failure in a single export.
Who answers each check, and who signs off
The checks name the owners: credit administration for coverage and outcomes, the CRM admin for keys and related borrowers, the records manager for versions, the servicing manager for dates. Above them, the CFO or chief credit officer may sponsor the introduction, but the person who can authorize a licensing discussion is the CEO. If the lender is about to replace its servicing system, the ERP replacement handoff checklist explains why the timing matters; bankers already running a commercial loan annual review should keep that work separate from any introduction.
Confirm the company baseline: 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. The company fit checker covers the same points.
Every record here describes a borrower. Borrower agreements, privacy obligations, redaction, which years a buyer wants and what the lender would be paid stay unknown until SourceX reviews them with the company. Partners never ask for or handle loan files, checklist items or servicing records.
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.
When the scorecard gives you one accurate sentence about the lender's condition trail and a sponsor who wants to talk, register as a partner, check who qualifies and read the program terms before you introduce them.