Credit-condition-to-cure metadata packet: a fill-in template and sample for lender introductions

Short answer

A referral partner can collect the shape of a lender's credit-condition-to-cure trail without reading a borrower file: which systems hold the approval condition, the submitted evidence and the satisfaction flag; the date range and rough count in each; the key that joins them; who administers each system; and what nobody knows yet. The packet below is that list as a fill-in template, followed by a sample filled for a fictional lender. Nothing in it names a borrower or shows a document.

Visual briefFull-size diagram
A metadata packet fills in field by field, systems, date range, condition count, join key, owners and unknowns, while a locked stack of borrower files beside it stays closed.
Illustrative packet for a fictional equipment finance company. Counts and years are invented.

This resource belongs to the guide for bankers introducing a client opportunity. It applies when the company being introduced is itself a lender, such as a specialty finance company or an equipment lessor with its own credit team.

The packet template: seven blocks, each answerable in conversation

Each block has a purpose. Together they let SourceX judge whether a review is worth scheduling without anyone moving a record.

BlockFields to recordWhy SourceX needs it
1. Sponsor and scopeLender type, loan products in scope, sponsor's roleShows who can authorize a licensing discussion and what the records cover
2. SystemsCRM, document store, servicing system, any spreadsheet used for trackingShows where each step of the trail lives
3. Record typesCondition, checklist item, evidence file, approval history, servicing statusShows which steps are captured as records at all
4. Volume and rangeYears retrievable per system; approximate conditions per yearShows depth, without a sample
5. Join keysIdentifier used in each system and since whenShows whether a condition can be followed end to end
6. OwnersAdmin owner per system; who reviews conditionsShows who would answer SourceX's questions
7. Unknowns and constraintsOpen questions; borrower agreement and privacy notice exist (yes or no)Keeps the packet honest and flags rights questions for review

Block 7 records only that borrower agreements and privacy notices exist. Whether any record may be licensed is a rights and privacy question SourceX reviews with the lender, not something a partner judges.

Sample packet from a fictional equipment lender (Illustrative)

A fictional 340-person equipment finance company, filled in during a 40-minute call with its head of credit administration and its CRM admin. Every value is invented.

BlockFieldEntry
1Lender type and productsEquipment loans and leases to mid-size manufacturers and contractors
1SponsorChief credit officer, with the CFO informed
2CRMSalesforce Financial Services Cloud since 2019
2Document storeBox, one folder per loan, since 2017
2ServicingLoan servicing platform since 2014, condition and tickler records
2Side trackingCloser spreadsheet for post-closing conditions, 2014 to 2019
3Record typesApproval conditions, document checklist items with approval history, evidence files with versions, servicing condition status
4Years retrievableCRM 2019 onward; Box 2017 onward; servicing 2014 onward
4VolumeAbout 2,500 conditions a year; roughly 60% post-closing
5Join key in CRMAccount and loan application on each checklist item
5Join key in BoxLoan number in folder name since 2018; borrower name before
5Join key in servicingLoan number
5Related-entity linksAccount relationships recorded for guarantors since 2021
6OwnersCRM admin; records manager for Box; servicing manager
6Condition reviewersCredit analysts and closers
7Box version limitUnknown; records manager to confirm the plan setting
7Approval history exportUnknown until the CRM admin checks
7Rebooked dealsUnknown whether checklist items move when a deal changes entity
7Borrower agreements and privacy noticeExist; terms not reviewed

Read it as a reviewer would. The strongest years are 2019 onward, when all three systems exist and Box folders use loan numbers. 2014 to 2018 depends on a closer spreadsheet. The open questions are specific enough for SourceX to ask the right person.

Fields that never go in the packet

The packet's value depends on what it leaves out. If a field below comes up in conversation, do not write it down.

Never recordRecord instead
Borrower names, guarantor names or entity details"Account relationships recorded since 2021"
Loan numbers, amounts or rates"About 2,500 conditions a year"
Any document, screenshot or redacted sampleRecord types and the system that holds them
Rejection reasons for a particular condition"Rejection notes kept in approval history"
Logins, API tokens or export filesThe admin owner's role
Personal contact details beyond a business emailThe owner's title

Why three fields matter more than the rest

Join key in CRM. Salesforce's documentation says 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 "account and loan application" is the honest entry, and "what happens on rebooking" belongs in the unknowns until someone checks.

Approval history. Salesforce's document tracking runs uploaded files through an approval process, and customers upload new versions of rejected documents. If the lender used that feature, the rejection and its reason can survive. Record whether it was used and since when, not what any rejection said.

Box version limit. Box keeps a plan-dependent number of prior versions (for example 50 on Business plans, 100 on Enterprise, unlimited on Enterprise Plus), and admins can adjust it within those limits. That setting decides whether a first, rejected submission still sits beside the accepted one. The records manager can read it from the admin console; nobody needs to open a file.

Collecting the packet in one call

Ask the sponsor to bring the CRM admin and the records manager. Go block by block and read each field as a question. Where a number is uncertain, write a range and mark it as an estimate. Where nobody knows, write "unknown" and the name of the role who would. Close by reading the unknowns back so the lender can correct them.

For per-system starting points, the Salesforce inventory template covers CRM fields, and the Outlook inventory template helps where conditions are chased by email. The companion pages go deeper: the record-chain guide traces one condition through each key, the completeness checklist scores the gaps, and the missing-context comparison shows what a single export gets wrong.

Before introducing, confirm the basics: 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. For the covenant side of cures, see equity cure rights; for how a review of records is framed, see what a data audit is.

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 lender's sponsor has filled in the packet and wants to talk, register as a partner, check who qualifies and read the program terms before you send the introduction.

  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

Who fills in the packet?

The lender's own credit administration or operations owner, with the CRM admin and records manager supplying counts. The partner asks the questions and writes down the answers; the partner does not log into anything.

Can the packet include a sample condition with the borrower's name removed?

No. Even a redacted condition is borrower content. The packet describes record types, counts, years, keys and owners. SourceX looks at content only under a signed agreement with the company.

What if the lender cannot give counts?

Use ranges or orders of magnitude, such as about 3,000 conditions a year, and mark them as estimates. An honest estimate is more useful than a precise number nobody can stand behind.

Sources

  1. refer.sourcex.si/terms
  2. developer.salesforce.com/docs/atlas.en-us.financial_services_cloud_ad…
  3. help.salesforce.com/s/articleView
  4. support.box.com/hc/en-us/articles/360043693454-Adjusting-the…

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