One certificate, several source documents
Ask a CFO what actually goes into a quarterly covenant compliance certificate, and the honest answer is a stack of documents that were never designed to talk to each other — the income statement, the balance sheet, a cash flow statement or its components, and often the company's own bank records, all feeding a calculation schedule with its own row-by-row logic defined by the credit agreement.
Each of those figures should tie out to something verifiable. In practice, tying them out means someone pulling numbers by hand from PDFs and spreadsheets into the schedule, trusting that nothing shifted between the source and the copy — a trust that holds most quarters, and produces a costly surprise the quarter it doesn't.
This page describes how the source documents behind a compliance certificate are read and matched to the calculation schedule that depends on them — not to compute your covenant ratios, but to confirm the inputs feeding that computation are correct before the certificate goes out.
Why this isn't a simple copy-paste
A covenant calculation schedule asks for specific line items — EBITDA before certain add-backs, total funded debt, interest expense, sometimes a trailing-twelve-month figure built from several quarters. Financial statements report numbers in their own structure, which rarely maps one-to-one onto what the schedule asks for.
Multiply that translation step by every quarter, every facility, and every add-back that has to be reconstructed consistently period over period, and the twenty-minute exercise on a simple facility becomes a recurring task that's easy to rush — right up until an inconsistency between two quarters draws a lender's question nobody wants to spend a week answering.
What a financial covenant actually requires
A financial covenant is a contractual condition in a credit agreement requiring the borrower to maintain, or achieve, a specific financial metric — a maximum leverage ratio, a minimum debt service coverage ratio, a minimum interest coverage ratio. The lender uses these metrics as an early-warning system, a way to see financial deterioration before it becomes a payment default.
The specific covenants, their thresholds, and exactly how each ratio is defined all come from the credit agreement itself — no two agreements define EBITDA identically, and a definition that includes certain add-backs in one facility may exclude them in another. That variation is precisely why matching source figures to the schedule your agreement actually specifies matters more than applying a generic formula.
Maintenance covenants vs. incurrence covenants
A maintenance covenant is tested on a fixed schedule regardless of what the borrower does — typically every quarter, whether the business took any relevant action or not. An incurrence covenant, by contrast, is only tested when the borrower takes a specific action the credit agreement flags — incurring new debt, paying a dividend, making an acquisition.
| Type | When it's tested |
|---|---|
| Maintenance covenant | Every period, on a fixed schedule, regardless of borrower activity |
| Incurrence covenant | Only when the borrower takes a specific flagged action |
Knowing which type applies to a given covenant changes when a calculation actually needs to be run — a maintenance covenant needs the full schedule every quarter without exception, while an incurrence covenant only needs it the quarter a relevant transaction is on the table.
The ratios lenders actually track
| Ratio | What it measures |
|---|---|
| Leverage ratio (Debt-to-EBITDA) | Total debt relative to earnings before interest, tax, depreciation and amortization |
| Debt Service Coverage Ratio (DSCR) | Cash flow available for debt service relative to total debt service due |
| Interest Coverage Ratio (ICR) | EBITDA relative to interest expense |
| Fixed Charge Coverage Ratio (FCCR) | Cash available after capex and taxes relative to interest, scheduled principal and other fixed charges |
| Current ratio | Current assets relative to current liabilities |
Each of these ratios draws on figures scattered across an income statement, a balance sheet and sometimes a debt schedule — exactly the kind of cross-document assembly that goes wrong quietly when done by hand under a filing deadline.
What gets read
| Data | Source |
|---|---|
| Revenue, EBITDA components, interest expense | Income statement |
| Total debt, current assets, current liabilities | Balance sheet |
| Cash movements, debt service payments | Bank records |
| Scheduled principal and interest | Debt or amortization schedule |
A field that can't be read with confidence — a total obscured by a footnote reference, a figure split across two lines — is flagged rather than filled in with a best guess, so review focuses on the handful of numbers that genuinely need a second look.
How it works
Upload financial statements and bank records
For the reporting period the compliance certificate covers.
Each document is read
Line items, totals and dates extracted from both sides.
Figures matched to the calculation schedule
Each input mapped to the row it feeds, with cross-document ties confirmed.
Gaps flagged, not guessed
A figure that doesn't tie out between sources is marked for review.
Exported
Excel, CSV or JSON, with every matched figure traceable to its source document.
A quarter, reconciled
A mid-market borrower with a single term loan and a quarterly leverage covenant uploads its income statement, balance sheet and business checking account statement for the quarter.
| Result | Count |
|---|---|
| Figures matched with high confidence | 22 |
| Flagged for quick confirmation | 2 |
| Cross-document tie confirmed | 5 |
| Genuine discrepancy found | 1 |
The one genuine discrepancy turns out to be an interest payment posted to the bank account a day after quarter-end but accrued in the prior period on the income statement — a timing difference, not an error, resolved with a short note before the certificate is finalized rather than discovered as an unexplained gap during a lender review.
Tracking headroom, not just pass or fail
Once thresholds from the credit agreement are entered, each period's matched figures are shown against the covenant threshold, with the gap — the headroom or cushion — visible directly rather than buried in a spreadsheet formula nobody checks until the ratio actually trips.
A leverage ratio sitting comfortably under its cap one quarter and drifting closer the next is exactly the kind of trend that's easy to miss looking at one certificate at a time, and easy to catch looking at the trend across several quarters side by side.
When more than one facility is in place
A borrower with a term loan and a revolving credit facility, or a company that has layered on additional debt over time, often faces more than one covenant package — sometimes from the same lender, sometimes from different ones, each with its own definitions and thresholds.
Each facility's schedule is matched independently, using the specific definitions that facility's agreement calls for, then rolled into one consolidated view — a ratio never gets conflated across facilities that define it differently, even when the underlying financials are the same.
Handling a near-miss with method
A calculated ratio that lands close to its threshold, or a figure that doesn't tie out cleanly between the financials and the bank records, gets flagged rather than smoothed over. The first step is confirming whether the gap is a timing difference — a payment accrued in one period and cleared in the next — or a genuine discrepancy that needs correcting before the certificate goes out.
A calculation that would breach a threshold, or come close enough to warrant a conversation, is exactly the kind of finding worth raising with your finance team and lender proactively — the credit agreement's cure period provisions exist precisely for situations caught and addressed before the deadline, not after.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| Figures retyped from PDFs into the schedule each quarter | Every figure matched automatically from the source document |
| A discrepancy discovered at the lender's review | A discrepancy flagged before the certificate is submitted |
| Headroom tracked, if at all, in a separate memory or note | Headroom tracked automatically against each threshold |
| Redone from scratch for a second facility | Same method applies regardless of facility count |
From one facility to a full credit stack
A single term loan with one leverage covenant is a manageable manual exercise, if tedious. A company with a syndicated facility, several tranches, and multiple covenant tests each quarter turns the same exercise into a job that consumes days of finance-team time every reporting cycle.
Reading and matching each facility's schedule the same way regardless of complexity keeps the effort per figure flat as the credit stack grows — what changes is only how many figures need a human look, which a well-tuned matching process keeps small.
Who uses this
CFOs and controllers
A verified set of inputs for the compliance certificate, without a manual reconciliation each quarter.
Finance teams under multiple facilities
The same matching method applied across every lender and covenant package.
Borrowers approaching a covenant threshold
Headroom tracked and visible in advance, not discovered at the deadline.
Outside accountants preparing certificates
A verified record ready before the client relationship even needs to ask.
Edge cases worth knowing
A trailing-twelve-month calculation, common for covenants tested on a rolling basis rather than a single quarter, draws on four quarters' worth of statements rather than one — each period is matched individually, then rolled into the trailing figure the schedule actually needs.
An add-back specific to one credit agreement — a one-time restructuring charge, a non-cash expense — needs to be identified in the source financials and applied consistently every period it's claimed, since an add-back used inconsistently from quarter to quarter is exactly the kind of detail a lender's review is built to catch.
Why a traceable number beats a rounded one
A compliance certificate that shows only final ratios, without the reasoning behind each figure, is easy to trust until a lender asks why a specific line item was calculated the way it was. Reconstructing that reasoning later means going back to the original statements and starting over.
Keeping the source document attached to every matched figure — statement date, page reference, confidence level — turns that reconstruction from a scramble into a detail already sitting in the data, ready the moment a lender asks.
What this doesn't do
Doesn't calculate your covenant ratios
It matches the inputs your schedule needs — applying your credit agreement's specific ratio definitions stays your calculation.
Doesn't interpret your credit agreement
Covenant definitions, thresholds and cure provisions come from your specific agreement — read by you or your counsel, not by this tool.
Doesn't submit anything to your lender
It surfaces a matched, traceable set of figures. Submitting the certificate stays your step.
Doesn't give financial or legal advice
Any question about compliance, waivers or cure rights belongs with your lender, counsel or CFO.
What it does fits in one sentence: turn a stack of financial statements and bank records into matched, traceable figures, so the question “does every number in this certificate tie back to something real” has an answer before a lender has to ask.
Security and privacy
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For financial statements and bank data that reveal the full shape of a company's finances, that matters — details are on the security page.