This system map is part of the covenant reporting corrections guide. It is for loan systems consultants who need to tell a lender, before a migration or an introduction, whether its correction history can be reassembled from its systems or only from its people.
Where each covenant record lives
A covenant correction touches at least five places. The table maps the usual arrangement in a commercial lender; the owner column is who answers for the record day to day.
| System | Record | Linking key it carries | Owner |
|---|---|---|---|
| Document portal | Compliance certificate and supporting schedules, original and revised | Obligor name, upload date, sometimes facility | Loan servicing |
| Portal messaging or email | Clarification thread with the obligor's finance team | Obligor name, sometimes a document link | Relationship manager or analyst |
| Spreadsheet library or covenant module | Calculation spreadsheet, each version | Facility, test date, sometimes version | Credit analysts |
| Loan platform | Covenant definition, threshold, test record and result | Facility, covenant, test date | Credit administration |
| Credit approval system or loan file | Credit officer determination, waiver or amendment | Facility, date | Credit officers |
| Loan file | Audited statements and reconciliation to quarterly figures | Obligor name, fiscal year | Credit analysts |
Most lenders have some structure here. The question for a map is whether that structure carries the keys from one system to the next, or stops at each system's edge.
Four join keys: facility, covenant, test date, version
| Key | Strong in | Weak in | What it joins |
|---|---|---|---|
| Facility | Loan platform, spreadsheets, decisions | Portal (often borrower-level only) | Certificate to the facility it was tested against |
| Covenant | Loan platform test record | Spreadsheets with several tests on one tab; email | A calculation to the specific test it supports |
| Test date | Loan platform, spreadsheets | Decisions filed by facility and decision date | A decision to the quarter it resolved |
| Calculation version | Spreadsheet libraries that keep versions | Loan platform result field; portal | The result to the version it was based on |
The version key is the one most often missing. The loan platform stores "compliant" or "breach", not which calculation produced it. If the spreadsheet library overwrites files, the versions vanish. Where it keeps history, it can stand in for the missing key: SharePoint's version history lists each earlier version with the date and the user who saved it, so v1, v2 and v3 of a calculation can be dated and attributed even when the file name never changed. Ask which libraries hold the spreadsheets and whether versioning is on.
One correction joined across five systems (Illustrative)
A fictional 450-person commercial lender. One quarterly leverage test, rebuilt hop by hop.
| Hop | From | To | Key used | What the join proves |
|---|---|---|---|---|
| 1 | Portal: certificate uploaded April 18 | Loan platform: Q1 leverage test, facility 2 | Borrower plus test date, matched by the analyst | The certificate belongs to this test |
| 2 | Portal messaging: analyst query April 20 | Portal: revised schedule April 24 | Document link inside the thread | The revision answered the query |
| 3 | Revised schedule | Spreadsheet v2 and v3, facility 2, Q1 | Facility, test date, version | The lender recalculated rather than accepted |
| 4 | Spreadsheet v3 | Loan platform test record: compliant | Facility, covenant, test date | The stored result came from v3, not v2 |
| 5 | Loan platform result | Credit officer determination April 26 | Facility and date | The determination was authorized |
Hop 1 is the weak spot: the portal carried only the borrower and upload date, so the analyst made the match. It held here because the analyst recorded the test date in the spreadsheet. The step-by-step version of a case like this, with the numbers, is on the exception examples page.
Weak joins and what a migration does to them
| Record | Usual migration plan | What breaks |
|---|---|---|
| Certificates and schedules | Open facilities only | Closed facilities lose their test evidence; upload metadata may not export |
| Spreadsheet versions | Latest file only | Version key gone; results look unexplained |
| Clarification threads | Not migrated | Revisions lose their reason |
| Covenant test records | Migrated | Kept, but without a link to the version used |
| Decisions, waivers, amendments | Final status only | Filed by facility, no longer tied to the test date |
| Audited reconciliations | Left in the loan file | Not linked back to the quarter they confirmed |
For what a lender package typically contains, see the lender reporting package and the covenant compliance certificate template; for a covenant type that often produces disputed calculations, see restricted payments and sponsor dividends.
Questions for the credit operations head about joins
A lender with organized covenant monitoring can usually answer these quickly. Ask them at metadata level; none requires a file:
- Does the portal record the facility and test date with each upload, or only the borrower and date?
- Are spreadsheet versions kept, in which libraries, and with what version limit?
- Does the covenant test record store which calculation it was based on?
- Are waivers and amendments linked to the test date they affected?
- Could someone rebuild one past correction from certificate to sign-off without asking the analyst who did it?
Then record ownership and authority. The records are the lender's, but they contain borrower information under credit agreement confidentiality terms, and the threads name people: where EU law applies, the GDPR treats any information relating to an identifiable person as personal data. The executive who can authorize a licensing discussion and sign is the CEO, often supported by the CFO or chief credit officer; see the who-can-say-yes tree. Unknown until SourceX reviews it: buyer interest, the rights result, the de-identification required and any offer.
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Related record types are described in credit memos in commercial lending and on the industries hub.
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 a lender's four keys mostly hold and its old portal or platform has a switch-off date, register as a partner, check the lender against who qualifies and read the program terms before you introduce the credit operations head.