Answers / Corporate Treasury

Walk me through the covenant compliance certificate process and why the credit agreement's EBITDA definition matters so much.

A core Corporate Treasury interview question — asked in analyst and associate interviews across IB, PE, and the Big 4.

THE SHORT ANSWER

Periodically (usually quarterly) the borrower delivers a compliance certificate to lenders certifying the financial covenants — typically leverage, interest cover, sometimes capex — with the supporting calculation. The make-or-break detail is that you must use the credit agreement's defined 'EBITDA', not reported EBITDA: the definition specifies permitted add-backs (one-offs, restructuring costs, run-rate/pro-forma synergies, sometimes uncapped) and adjustments, so 'covenant EBITDA' can differ materially from statutory EBITDA. Treasury models headroom on that defined basis, watches the permitted add-back caps, and forecasts forward to flag a potential breach early. Getting the definition wrong — or assuming reported numbers — can mean falsely certifying compliance or missing an approaching breach, both serious. So the credit agreement definitions, not the accounts, govern.

WHAT INTERVIEWERS LISTEN FOR

  • Periodic certificate certifying covenants with calculations
  • Use the agreement's defined EBITDA, not reported
  • Add-backs/adjustments defined and sometimes capped
  • Forecast headroom forward to flag breaches early

COMMON MISTAKES

  • Using statutory EBITDA for covenants
  • Ignoring defined add-back caps
  • No forward-looking breach monitoring

Reading isn't the same as answering under pressure.

Interviewers don't hand you the model answer — you deliver yours on a clock. Practice this and 1,000+ questions with AI feedback on every answer.

TRY QUICKFIRE →Or train full Corporate Treasury case simulations →

RELATED QUESTIONS