Covenant Reporting That Survives a Lender's Second Look

The email from the relationship manager is short: “Can you send this quarter’s covenant certificate, and can we get the leverage ratio calc behind it this time.” That last clause is the one that causes the scramble. Someone pulls last quarter’s spreadsheet, someone else pulls this quarter’s, and the two EBITDA add-back lines do not quite match because a formula got tweaked in between. Now you are explaining a discrepancy that was never supposed to exist.

Covenant reporting sounds simple: calculate a ratio, compare it to a threshold, send a certificate. What actually makes it hard is that the ratio has to be the same ratio every single quarter, computed the same way, tied to numbers a credit analyst can independently check. Drift into that process is invisible until someone downstream asks a question you cannot answer on the spot.

Where covenant packs quietly go wrong

The usual failure is not fraud, it is entropy. Leverage and coverage ratios get defined once in a credit agreement and then re-implemented every quarter in a live spreadsheet, by whoever happens to own the file that period. Add-backs shift, a rounding convention changes, someone fixes what looks like an error without checking the prior period. None of it is dishonest. All of it produces a number that does not reconcile to the one in last quarter’s board pack, which is exactly the kind of inconsistency a lender’s credit team is trained to notice.

What a defensible covenant number requires

Rexfin’s approach starts from a simple constraint: a ratio like leverage or interest coverage is defined once, as a canonical calculation, and every place it shows up (the covenant certificate, the board pack, a monthly variance review) pulls the identical math against the identical figures. There is no second implementation to drift.

Every operand behind that ratio traces back to a source-verified figure in your books. If the bank’s credit team questions the debt balance or the EBITDA add-back, the answer is not “let me check with accounting”: it is a click that opens the underlying ledger line. That trace-to-source behavior is what turns a certificate into something a lender can actually rely on rather than take on faith.

A material-variance filter also does quiet work here: it surfaces only the covenant-relevant lines that moved enough to matter, instead of forcing you to eyeball a full P&L for anything that might affect the ratio. And a red-flag monitor catches ratio drift early: a covenant heading toward its threshold shows up as a signal weeks before the formal test date, not as a surprise on the certificate deadline.

Showing headroom over time

Lenders renewing a facility want more than one quarter’s snapshot: they want to see the ratio holding steady, or improving, across several periods. A multi-year trend view that pivots the same canonical calculation across every filed period gives you that history without re-deriving it by hand each renewal cycle, and every year in it still drills to its source.

What this does not solve

None of this decides which covenants matter or how your credit agreement defines EBITDA, that is a legal and negotiated question, and getting the add-back definitions right in the first place is still your job. What the calculation engine guarantees is that once the definition is right, it stays right every quarter, and every number behind it is traceable. That is a smaller promise than “covenant compliance handled,” but it is the one that actually holds up when a bank asks for the calc behind the number.

If you are assembling the full package a bank expects (not just the ratio but the supporting statements), see the bank financing pack. And if covenant numbers are feeding the same board reporting cycle you run every month, the quarter-end flash report is where that overlap usually shows up first.

For more on how finance teams are using Rexfin day to day, see the finance team use cases hub.