Covenant reporting correction, worked step by step: one leverage test, three calculation versions

Short answer

The records that explain a covenant reporting correction are the calculation versions themselves, plus the thread between them and the signed decision at the end. In the Illustrative case below, a borrower's quarterly certificate fails a 4.00x leverage test at 4.25x, the manufacturer's CFO corrects it to 3.84x with an add-back, and the lender's analyst caps the add-back under the credit agreement to reach 3.86x. Five dated records in four places show what went wrong, who decided and why the outcome holds.

Visual briefFull-size diagram
A vertical case timeline: on day 0 the certificate shows 4.25x against a 4.00x maximum and the path branches; day 2 a clarification thread, day 6 a revised schedule at 3.84x, day 8 the analyst's capped version at 3.86x and the credit officer's sign-off, each with its record.
Illustrative quarter at a fictional commercial finance company: three versions and one thread explain a result the final number alone hides.

This worked case is part of the covenant reporting corrections guide. It is written for loan systems consultants who want to recognize, inside a lender, the kind of file that makes a correction explainable rather than just recorded.

The quarter that failed, then passed twice (Illustrative)

A fictional 260-person commercial finance company monitors a loan to a mid-sized manufacturer. The credit agreement sets a maximum total leverage of 4.00x, funded debt to EBITDA. It allows plant consolidation costs to be added back to EBITDA, capped at 10% of EBITDA before the add-back. All figures are fictional.

The manufacturer is consolidating two plants this year. Its controller prepares the quarterly compliance certificate without the consolidation costs. The controller's signed certificate, uploaded to the lender's portal, is where the case starts.

Three calculation versions side by side

VersionPrepared byFunded debtEBITDA usedLeverageStatus
v1, as submittedManufacturer's controller$35.7M$8.4M4.25xFails the 4.00x test
v2, borrower's correctionManufacturer's CFO, after the lender's query$35.7M$9.3M, adding back $0.9M3.84xPasses, if the full add-back is allowed
v3, lender's calculationCredit analyst, reviewed by the credit officer$35.7M$9.24M, add-back capped at $0.84M3.86xPasses; $0.06M of the add-back disallowed

The arithmetic is simple once laid out: 10% of $8.4M is $0.84M, so only that much of the $0.9M cost counts. The interesting part is not the math but the reading of the definition, and that reading lives in the analyst's note, not in the result field.

Day by day: who decided what, and where it was recorded

DayWhat happenedWho decidedRecordWhere it lives
0Certificate arrives showing 4.25x; covenant record flagged as a potential breachCredit analystCertificate and schedule; flag on the covenant testDocument portal; loan platform
2Analyst asks why EBITDA fell; CFO replies that a $0.9M consolidation cost was left outManufacturer's CFOClarification threadPortal messaging
6Revised schedule and invoice summary uploaded; analyst checks the EBITDA definition and finds the 10% capCredit analystRevised schedule; analyst's working notesDocument portal; workbook
8v3 saved with the capped add-back and a note citing the definition; officer signs off as compliant at 3.86x, no waiver neededCredit officerCalculation workbook v3; sign-offWorkbook library; loan platform
Next quarterCertificate accepted on first submission; audited statements later reconcile with the quarterly figuresCredit analystNext test record; reconciliation noteLoan platform; loan file

Each row lands in a different place, which is why the case is fragile. Five entries, four homes, three people deciding and eight days end to end: nothing in that spread holds the pieces together unless someone deliberately keeps them in one file.

The calculation versions are the most fragile part. Where analysts save their spreadsheets in a SharePoint library, version history lists each earlier version with the date and the user who saved it, which is exactly the trail from v1 to v3. Restoring an old version adds a copy as the newest one instead of deleting what came after, so the sequence survives a mistaken edit. But a library keeps only up to a set maximum number of versions and deletes the oldest when it reaches that limit, so a busy file can lose its first submission without anyone deciding to delete it.

Why the sequence is better evidence than the final number

The final record says "compliant, 3.86x". Taken alone, it suggests an uneventful quarter. The sequence says something far more useful: a first submission failed, the manufacturer proposed a fix, the lender tested that fix against the agreement's definition, accepted most of it, disallowed a specific amount and documented why, without a waiver.

Lose a piece and the meaning changes. Without the thread, v3 looks like an unexplained override of the manufacturer's figure. Without v1, the file shows a quarter that passed and hides the one that nearly did not. Without the officer's sign-off, nobody can show the determination was authorized. A file that shows why a figure was accepted protects the lender later, when the same add-back comes up again next year or someone asks why no waiver was needed. A correction file is the record of a lender applying a definition to a disputed figure. How one-time items are treated in covenant EBITDA generally is covered in does one-time income count in covenant EBITDA.

Recognizing a similar correction at a lender client

You will not see a workbook, and you should not ask to. These signals in an ordinary conversation with the credit operations head tell you whether the lender has cases like this:

  • Add-back caps and permitted adjustments in its standard credit agreements, which create disputes worth documenting.
  • Analysts who save a new workbook version rather than overwrite, and a library that keeps versions.
  • Portal messaging used for borrower queries, rather than personal email.
  • Covenant test records that store status plus the calculation they were based on.
  • A share of tests needing revision each year; even a rough figure, such as one in ten, is useful.
  • A loan platform or portal migration with only final results planned to move.

Then qualify at metadata level: which record types exist, in which systems, for how many years and borrowers; who owns them; who can authorize a licensing discussion, which is the CEO, often with the CFO or chief credit officer preparing the case. The lender's working records contain borrower information, so credit agreement confidentiality terms decide what can be used; the who-can-say-yes tree sets out that path. Unknown until SourceX reviews it: buyer interest, the rights result, de-identification 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. The records across systems map shows the keys that hold this chain together, and the covenant compliance certificate template, portfolio variance reporting and the private credit portfolio monitoring page give the surrounding context. A comparable exception chain in another sector is described for logistics exceptions.

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 client keeps superseded calculation versions with their threads and sign-offs, 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

Would a lender ever want to discuss a near-breach like this?

Sometimes. A correction that was questioned, checked against the credit agreement and signed off shows disciplined credit monitoring. The partner only asks whether such files exist; the lender decides whether any discussion makes sense.

Are the borrower's financials part of what could be licensed?

That is for the lender's counsel and SourceX's rights review. Credit agreements usually carry confidentiality terms over borrower information, so borrower identities and figures may need to be removed or de-identified, or the records excluded.

Does the case only work for leverage covenants?

No. Fixed charge coverage, minimum liquidity and borrowing base tests produce the same pattern: a submitted figure, a query, a revised schedule, the lender's own calculation and a decision.

Sources

  1. refer.sourcex.si/terms
  2. support.microsoft.com/en-us/sharepoint/lists/documents-and-library…
  3. support.microsoft.com/en-us/sharepoint/documents-and-library/resto…

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