# Covenant reporting correction: a worked case | SourceX

Canonical: https://refer.sourcex.si/guides/covenant-reporting-corrections-exception-examples
Last updated: 2026-11-04

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.

This worked case is part of the [covenant reporting corrections guide](/guides/workflow-covenant-reporting-corrections). 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

| Version | Prepared by | Funded debt | EBITDA used | Leverage | Status |
|---|---|---|---|---|---|
| v1, as submitted | Manufacturer's controller | $35.7M | $8.4M | 4.25x | Fails the 4.00x test |
| v2, borrower's correction | Manufacturer's CFO, after the lender's query | $35.7M | $9.3M, adding back $0.9M | 3.84x | Passes, if the full add-back is allowed |
| v3, lender's calculation | Credit analyst, reviewed by the credit officer | $35.7M | $9.24M, add-back capped at $0.84M | 3.86x | Passes; $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

| Day | What happened | Who decided | Record | Where it lives |
|---|---|---|---|---|
| 0 | Certificate arrives showing 4.25x; covenant record flagged as a potential breach | Credit analyst | Certificate and schedule; flag on the covenant test | Document portal; loan platform |
| 2 | Analyst asks why EBITDA fell; CFO replies that a $0.9M consolidation cost was left out | Manufacturer's CFO | Clarification thread | Portal messaging |
| 6 | Revised schedule and invoice summary uploaded; analyst checks the EBITDA definition and finds the 10% cap | Credit analyst | Revised schedule; analyst's working notes | Document portal; workbook |
| 8 | v3 saved with the capped add-back and a note citing the definition; officer signs off as compliant at 3.86x, no waiver needed | Credit officer | Calculation workbook v3; sign-off | Workbook library; loan platform |
| Next quarter | Certificate accepted on first submission; audited statements later reconcile with the quarterly figures | Credit analyst | Next test record; reconciliation note | Loan 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](/questions/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](/questions/who-can-license-covenant-reporting-corrections-records) 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](/guides/covenant-reporting-corrections-records-across-systems) shows the keys that hold this chain together, and the [covenant compliance certificate template](/resources/covenant-compliance-certificate-template), [portfolio variance reporting](/resources/mcp/mcp-portfolio-variance-reporting) and the [private credit portfolio monitoring page](/for/private-credit-portfolio-monitoring-borrower) give the surrounding context. A comparable exception chain in another sector is described for [logistics exceptions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions).

## 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](/register), check the lender against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the credit operations head.

## Sources

- https://refer.sourcex.si/terms
- https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/how-versioning-works-in-lists-and-libraries
- https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint
