Covenant reporting corrections across systems: a map of portal, spreadsheet and loan platform records and their join keys

Short answer

Four keys join a covenant reporting correction across systems: the facility, the covenant, the test date and the calculation version. When the borrower's certificate in the document portal, the clarification thread, each spreadsheet version, the covenant test record in the loan platform and the credit officer's decision all carry those keys, a correction can be rebuilt end to end. When the portal knows only the borrower and the upload date, the join depends on someone remembering. One joined Illustrative case is laid out below.

Visual briefFull-size diagram
Five system nodes in a row, document portal, portal messaging, spreadsheet library, loan platform and loan file, each drop a key chip down a spoke into one joined Q1 leverage test record; the portal's chip is marked weak because it carries only the borrower and upload date.
Illustrative: four keys join a covenant correction across five systems. A spoke that carries only the borrower and upload date is where joins fail.

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.

SystemRecordLinking key it carriesOwner
Document portalCompliance certificate and supporting schedules, original and revisedObligor name, upload date, sometimes facilityLoan servicing
Portal messaging or emailClarification thread with the obligor's finance teamObligor name, sometimes a document linkRelationship manager or analyst
Spreadsheet library or covenant moduleCalculation spreadsheet, each versionFacility, test date, sometimes versionCredit analysts
Loan platformCovenant definition, threshold, test record and resultFacility, covenant, test dateCredit administration
Credit approval system or loan fileCredit officer determination, waiver or amendmentFacility, dateCredit officers
Loan fileAudited statements and reconciliation to quarterly figuresObligor name, fiscal yearCredit 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

KeyStrong inWeak inWhat it joins
FacilityLoan platform, spreadsheets, decisionsPortal (often borrower-level only)Certificate to the facility it was tested against
CovenantLoan platform test recordSpreadsheets with several tests on one tab; emailA calculation to the specific test it supports
Test dateLoan platform, spreadsheetsDecisions filed by facility and decision dateA decision to the quarter it resolved
Calculation versionSpreadsheet libraries that keep versionsLoan platform result field; portalThe 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.

HopFromToKey usedWhat the join proves
1Portal: certificate uploaded April 18Loan platform: Q1 leverage test, facility 2Borrower plus test date, matched by the analystThe certificate belongs to this test
2Portal messaging: analyst query April 20Portal: revised schedule April 24Document link inside the threadThe revision answered the query
3Revised scheduleSpreadsheet v2 and v3, facility 2, Q1Facility, test date, versionThe lender recalculated rather than accepted
4Spreadsheet v3Loan platform test record: compliantFacility, covenant, test dateThe stored result came from v3, not v2
5Loan platform resultCredit officer determination April 26Facility and dateThe 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

RecordUsual migration planWhat breaks
Certificates and schedulesOpen facilities onlyClosed facilities lose their test evidence; upload metadata may not export
Spreadsheet versionsLatest file onlyVersion key gone; results look unexplained
Clarification threadsNot migratedRevisions lose their reason
Covenant test recordsMigratedKept, but without a link to the version used
Decisions, waivers, amendmentsFinal status onlyFiled by facility, no longer tied to the test date
Audited reconciliationsLeft in the loan fileNot 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:

  1. Does the portal record the facility and test date with each upload, or only the borrower and date?
  2. Are spreadsheet versions kept, in which libraries, and with what version limit?
  3. Does the covenant test record store which calculation it was based on?
  4. Are waivers and amendments linked to the test date they affected?
  5. 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.

  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

What if the lender tracks covenants only in spreadsheets?

The map still works, with the spreadsheet library standing in for the loan platform's covenant module. The join keys then depend on file naming and folder structure, so ask how files are named and whether versions are kept.

Is the document portal usually the lender's or a vendor's?

Usually a vendor-hosted service under the lender's account. The documents are the lender's records, but what can be exported, with which metadata, depends on the portal and its contract. The lender's administrators should confirm it.

Does a partner need to see the files to judge the joins?

No. Ask the credit operations head whether one past correction could be rebuilt from certificate to sign-off, and which keys they would use. That answer is the metadata SourceX needs.

Sources

  1. refer.sourcex.si/terms
  2. support.microsoft.com/en-us/sharepoint/documents-and-library/resto…
  3. eur-lex.europa.eu/eli/reg/2016/679/oj/eng

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