Skip to content

Covenant and lender reporting

The covenant file is only as good as the one person who builds it

When the wrong version goes to the people you answer to, it costs more than an internal mistake ever does. Here's how the file stops depending on one person and one night.

11 of 55

buyer companies named bank covenant or lender reporting as the trigger for looking for help, the second most common trigger we heard.

Source: 55 buyer companies quoted in MCC sales conversations, 2026.

“The file I prepare on a monthly basis, we give it to our bank for the covenant calculations.”
Controller, payments group, July 2026

Is this the wrong page?

No lender, no covenant test, no borrowing base? Then this isn't your page. The real problem is more likely the consolidation or the budget.

Why it gets worse, not better

Covenant deadlines don't move for anyone. The test dates are in the credit agreement, and the certificate goes out whether or not the person who builds it had a good month. A late or wrong number to a lender costs more than a late or wrong number to yourself.

What changes

The old way compared with The new way
The old wayThe new way
One person prepares the covenant file by hand every month.Covenant calculations pull straight from the same model as the rest of your reporting.
EBITDA add-backs live in someone's head, or in a side tab.Every add-back is defined once, documented, and applied the same way each period.
Nobody is completely sure which version went to the bank.One current file, with a history of what changed and who changed it.
Headroom gets discovered at quarter-end.Headroom forecast ahead of each test date, from the forecast you already run.

In their words

This is the one lane where we'd rather you trust the process than a quote. Before anything is signed, a controller can see the covenant calculation work on a slice of their own numbers. We haven't yet published a client story that's specifically about covenants, so here is what clients say about the reporting underneath it.

A dental group went from 18 clinics to 36, and the budget, the board reporting and the covenant scenarios kept up.

“MCC helped us implement Vena to streamline budgeting, reporting, and forecasting across our 25 clinics. Even in the first year of implementation, we significantly reduced the time and manual effort required for our annual budget process - replacing multiple Excel versions with a much more efficient workflow.”

Simon Dumais

VP Finance, Clareo

Read the full story
“As a CFO, I’ve addressed our reporting challenges by integrating Vena with our existing Sage Intacct software, despite its limitations in public reporting. Monte Carlos Consulting was instrumental, offering expert advice and tailored solutions that met our specific needs. They not only implemented the necessary enhancements but also trained our staff effectively.”

Tasha Flowers

CFO, Arora Engineers

Read Arora Engineers's story
“As CFO of GeoKinetics, I'm impressed with MCC's smooth implementation of Vena and Power BI dashboards. They've greatly enhanced our financial reporting efficiency, solving typical challenges faced by growing companies. Their expertise has truly transformed our reporting processes.”

Adam Dao

CFO, GeoKinetics

Read GeoKinetics's story

An entity structure of subsidiaries and consolidation, understood quickly

“Has a great understanding of financial reporting which made the transition as easy as possible. They quickly understood our entity structure of subsidiaries and consolidation as well as our business.”

Jay Abrahams

Accounting Systems Manager, Eagle Bank

Read Eagle Bank's story

Questions finance teams ask about covenant and lender reporting

What goes into a covenant compliance certificate?

Usually the covenant calculations for the period, such as leverage, interest or fixed charge cover and minimum liquidity, the figures behind them, a statement that no default has occurred, and an officer's signature. Your credit agreement defines every term, so the certificate follows its definitions, not your management accounts.

This is general information, not legal advice. Your credit agreement and your lawyer have the final word on what your certificate needs.

How is covenant EBITDA different from reported EBITDA?

Covenant EBITDA follows the credit agreement's definition. It often adds back items such as one-off costs, non-cash charges or pro forma earnings from acquisitions, sometimes with caps. Reported EBITDA follows your accounting. The gap between the two is where most lender questions start, so every add-back needs a clear, repeatable basis.

How often do lenders require covenant reporting?

It depends on the agreement. Quarterly covenant tests with a compliance certificate are common, often alongside monthly or quarterly financial statements and annual audited accounts. Asset-based lenders may want borrowing base reporting monthly or more often. The reporting section of your credit agreement is the only reliable answer.

How do you forecast covenant headroom before the test date?

Run the covenant calculation on your forecast, not just your actuals. When the forecast sits in the same model, with the same definitions and add-backs as the certificate, headroom for the next test dates is a report rather than a project. That gives you time to act, or to talk to the lender early.

What happens if you breach a covenant?

It depends on the agreement. A breach can be an event of default, which may let the lender charge fees, reprice, demand repayment, or require a waiver or amendment. Lenders generally respond better to early notice with a clear explanation and a plan than to a surprise on the certificate. Take legal advice on your specific facts.

What is in a monthly lender reporting package?

Typically the monthly income statement, balance sheet and cash flow, a comparison to budget or forecast, the operating metrics the lender asked for, and sometimes aged receivables and payables or a borrowing base. What matters most is consistency: the same numbers, the same definitions and the same format, every single month.

Last updated

Where this happens in how we work

Covenant reporting gets proven in the first real cycle, side by side with the file you send today, so you can see the numbers agree before the new one goes to the bank. Start with the proof of concept on your own data.

This fits if

Any of these sound familiar

  • You answer to a lender or a covenant test on a fixed schedule you don't control.
  • The compliance certificate is built by hand, by one person.
  • Add-backs were agreed in emails, not documented anywhere the model can use.
  • You find out your headroom at quarter-end, not before.

Probably not a fit if

  • Nobody on your side owns the numbers, and nobody will.
  • You need a fully custom design signed off before you see anything working.

Email me this page

Not ready to talk yet? Save this page for later, or send it to your CFO. One email, not a newsletter you didn't ask for.