What is a covenant reporting correction?
Covenant reporting looks mechanical: each quarter the borrower sends a compliance certificate and supporting schedules, and the lender compares the result with a threshold in the credit agreement. The OCC notes that banks typically have borrowers certify covenant compliance in writing, and that examiners review a bank's systems for obtaining borrower information and monitoring covenant compliance.
The hard cases are corrections, where a permitted adjustment, a disputed add-back or a definitional question changes the calculation after the first submission. Those cases record how a lender read a definition, what evidence it asked for and what it accepted. The OCC's commercial real estate handbook stresses that covenant definitions of income and expenses should be clearly defined, and the receivables handbook warns that failing to document the reasons for waivers can weaken covenants. A correction file is that documentation. The borrower's side of the same moment is covered in options before a covenant breach; this page is about the lender's records.
What should be inventoried before a loan administration migration affects covenant reporting corrections history?
Inventory by record class, with years covered, borrower count, owning system and the real access deadline for each. The deadline is the date the old loan platform or document portal is switched off or its license lapses, which is often months after cutover. Most migrations bring over open facilities, current covenant settings and the final result of each test; superseded calculation workbooks and portal message threads are the usual casualties.
Here is an Illustrative register for a fictional 450-person commercial lender with about 600 facilities under covenant tracking. Each cell is metadata.
| Record class | System today | Years held | Owner | Migration plan |
|---|---|---|---|---|
| Covenant definitions, thresholds and add-back caps by facility | Old loan platform fields, credit agreement PDFs | 10 | Credit administration | Current settings only |
| Borrower compliance certificates and schedules | Document portal | 8 | Loan servicing | Open facilities only |
| Analyst calculation workbooks, all versions | SharePoint library | 7 | Credit analysts | Latest file only |
| Clarification threads with borrowers | Portal messaging, email | 6 | Relationship managers | Not migrated |
| Compliance determinations, waivers and amendments | Old loan platform, legal files | 10 | Credit officers | Final status only |
| Test results per quarter | Old loan platform | 10 | Credit administration | Migrated |
Microsoft documents a default of 500 major versions with no expiration for new SharePoint libraries, and says changing the organization default does not change existing libraries, so two libraries in the same lender can keep very different histories. Ask whether version history moves with each workbook, or only the latest file.
Four questions complete the inventory:
- Are superseded calculation versions kept, or overwritten by the final one?
- Roughly how many covenant tests a year needed a revised calculation?
- Are waivers and amendments linked to the specific test date they affected?
- When are the old platform and portal switched off, and what happens to message threads?
Do not recommend keeping anything the lender's retention policy and agreements do not allow. A partner gathers the answers, never the workbooks.
Work through one quarter the migration would flatten
An Illustrative leverage test shows the stakes. The borrower's first certificate fails the maximum; its corrected schedule adds back a one-time cost and passes; the lender's analyst caps the add-back under the credit agreement and the test still passes, by a narrower margin. Three calculation versions and a thread explain the outcome. After a final-results migration, the new platform shows one passing quarter. The step-by-step case is on the exception examples page linked below; questions about which items count, such as one-time income in covenant EBITDA, show why the versions matter.
Ask the credit operations head about coverage and rights
The head of credit operations or credit administration knows where certificates, workbooks and threads live and what the migration will carry. Authority to discuss licensing usually sits with the COO, chief credit officer or general counsel. Ownership needs care: the working records are the lender's own, but they contain borrower financial information, and credit agreement confidentiality terms and the lender's privacy commitments decide what can be used and what must be removed or de-identified. SourceX's rights review settles it; see why data rights matter.
The introduced company needs 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. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application.
Unknown until SourceX reviews it: buyer interest in covenant corrections, the rights result, the de-identification required and any offer. Related pages: the covenant compliance certificate template, the lender reporting package, restricted payments and sponsor dividends, the referral program for commercial bankers and the industries hub.
Go deeper on covenant reporting corrections
- Covenant reporting corrections referral brief template: a fill-in brief with metadata fields only and one completed Illustrative example.
- Covenant reporting corrections exception examples: one disputed quarter worked step by step.
- Covenant reporting corrections records across systems: a system map of platform, portal and workbook records and the keys that join them.
- Who can license covenant reporting corrections records: a decision tree from record owner to authorized signer.
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 the lender still holds superseded calculation versions with their threads and the old portal has a switch-off date, register as a partner, check the lender against who qualifies, and read the program terms and reward rules before you introduce the executive who can authorize the discussion.