# Covenant corrections referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/covenant-reporting-corrections-referral-brief-template
Last updated: 2026-11-04

A company introduction about covenant reporting corrections should fit on one page that the lender's credit operations head can forward without editing. It names the lender's size, the loan and portal systems involved, how many years of covenant tests exist, roughly how many tests needed a revised calculation, any dated access event, who owns the records and who can authorize a licensing discussion. It contains no borrower names, certificates, workbooks or figures from real files. Copy the blank template below, then compare it with the completed Illustrative brief.

This template belongs to the [covenant reporting corrections guide](/guides/workflow-covenant-reporting-corrections), which covers what to inventory before a loan administration migration. Here the job is narrower: writing the note that goes with the introduction.

## The blank brief: eight fields to copy

Fill each field after one conversation with the lender, using only facts a named person there can confirm. If nobody knows, write "unknown" and say who could check.

| Field | Write this | Leave this out |
|---|---|---|
| 1. Lender | Type of lender, full-time headcount at peak, country | Fund names, borrower names |
| 2. Facilities in scope | Loan types tested and the rough count of facilities under covenant tracking | Individual facilities or exposures |
| 3. Years of history | First and last year of covenant tests held, per system if they differ | Retention advice |
| 4. Correction share | The lender's own estimate of how often a test needed a revised calculation | Specific borrowers who failed |
| 5. Systems | Loan administration platform, client portal, analyst drive, email | Logins, exports, screenshots |
| 6. Access event | A documented date that changes access, and where it is written down | Pressure or soft deadlines |
| 7. Records owner | The role that keeps certificates, analyst files and threads | Opinions about the records' value |
| 8. Decision-maker | The executive who can approve a licensing discussion, and who advises | Promises about outcomes |

## How to fill the fields a covenant team will be asked about

**Correction share (field 4).** This is the line a reader at SourceX looks for first, because it separates a file of routine quarterly results from one that records judgment. A correction is any quarter where the first submitted result was later revised: an adjustment allowed or refused, an item reclassified, a ratio recomputed. Ask the person who runs testing for a rough proportion, such as "about one test in eight", and label it as the lender's own estimate.

**Years of history (field 3).** Ask for a start year per record class rather than one number for everything. The FDIC's examination manual notes that term loan agreements may carry restrictive covenants for the life of the loan, so a long-dated facility can produce a decade of quarterly tests; the lender's own working files for those years may be shorter or patchy. If the answer differs by class, write two dates. If a range is a guess, say so.

**Systems (field 5).** Name the system types and, if the lender is comfortable, the products. Someone in credit administration can usually name them quickly. If one record class lives only inside a messaging feature of a borrower-facing tool, flag it in a few words; that class often has the weakest export path, and only the lender's administrators can confirm what it produces.

**Access event (field 6).** Only a written date counts: a portal license end, a migration plan, a decommissioning schedule. If there is none, write "none known". The brief is not a place for urgency.

**Owner and decision-maker (fields 7 and 8).** These are rarely the same person. The [who-can-license decision tree](/questions/who-can-license-covenant-reporting-corrections-records) helps separate the person who keeps the records from the one who can say yes.

## The same brief completed for a fictional lender (Illustrative)

The values describe a fictional middle-market lender. They are **Illustrative**: no real lender, borrower or deal, and no figure is a forecast.

1. **Lender:** non-bank middle-market lender, about 400 full-time staff at peak, United States.
2. **Facilities in scope:** term loans and revolvers with quarterly and annual covenant tests; about 400 active facilities at peak, per the company's estimate.
3. **Years of history:** covenant tests and certificates from 2016 to present; analyst spreadsheets with saved versions from 2018.
4. **Correction share:** the company estimates one test in eight needed a revised calculation, most often after an add-back was capped under the credit agreement.
5. **Systems:** legacy loan administration platform being replaced; borrower document portal; shared analyst drive; email for clarification threads.
6. **Access event:** the document portal license ends six months after the new platform goes live, per the project plan.
7. **Records owner:** head of credit operations for certificates and test records; credit analysts' team lead for spreadsheets.
8. **Decision-maker:** CFO, advised by the chief credit officer on content and general counsel on credit agreement confidentiality.

**Open question to add at the end:** portal messages may not export with the documents they discuss. Can threads before 2020 still be matched to the test date they explain?

The open question is what makes the brief worth reading. It tells SourceX where the history is strong and where it may break, before anyone has seen a file. The [exception examples page](/guides/covenant-reporting-corrections-exception-examples) shows what one corrected quarter looks like when the thread survives.

## What the brief leaves out, and why

Everything above is metadata: counts, years, system types, roles and dates. Nothing in it identifies an obligor or reproduces a number from a submitted schedule. That is deliberate. Covenant files hold borrower financial information, and credit agreements usually restrict how it can be used or shared. Whether any of it can be licensed, and what must be removed or de-identified, is settled in SourceX's rights review with the lender, never by the partner.

Leave out, every time:

- borrower names, sponsor names, fund names and facility identifiers;
- certificates, schedules, spreadsheet extracts and portal screenshots;
- covenant thresholds or results from any real test;
- logins or exports, even if you have them as the consultant running the migration.

If you need wording for the covering email, the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) has it, and the [client opportunity brief generator](/tools/client-opportunity-brief-generator) can format the eight lines.

## Does the lender qualify before you send it?

Check these before the credit operations head forwards the brief:

- **Size and history.** The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact.
- **Location.** 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.
- **Your paperwork.** You have signed the Channel Partner Agreement. The first valid introduction within the 90-day window is credited when the company submits a verified application.
- **Unknowns stated.** Buyer interest, the rights result, the de-identification required and any offer stay unknown until SourceX reviews the opportunity.

SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. If the lender is a bank, the [commercial bankers page](/for/referral-program-for-commercial-bankers) covers how introductions usually reach its executives. The borrower-side reporting pack is described in the [compliance certificate template](/resources/covenant-compliance-certificate-template) and the [portfolio reporting resource](/resources/mcp/mcp-portfolio-reporting).

## 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 all eight fields and the open question are filled and the credit operations head is willing to forward the brief, [register as a partner](/register), confirm the lender on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://www.fdic.gov/resources/supervision-and-examinations/examination-policies-manual/section3-2.pdf
- https://refer.sourcex.si/rewards
