What a compliance package usually contains
Most credit agreements that include financial covenants require a periodic — usually quarterly — compliance package: the current period's financial statements, a completed calculation schedule showing each tested ratio against its threshold, and an officer's certificate confirming the figures are accurate and, typically, that no default has occurred.
None of these three pieces is complicated on its own. What makes the exercise error-prone is the cross-document work sitting underneath them — pulling the right figures from the right statements into the schedule, consistently, every single quarter, on a deadline that doesn't move.
Why preparation matters more than the math
The arithmetic behind a covenant ratio is usually simple — a division, sometimes a sum across four quarters. What determines whether a compliance package goes smoothly is whether the inputs feeding that arithmetic are correct, consistent with prior periods, and traceable back to something a lender could verify if they asked.
A finance team that assembles this package fresh each quarter, without a repeatable process, is relying on memory and attention to catch the same class of error every single time. A finance team with a routine catches most of that class of error automatically, simply because the routine doesn't depend on remembering what was done differently last quarter.
Confirm the reporting period and deadline
Before gathering anything, confirm exactly which period the certificate covers and when it's due — most credit agreements specify a fixed number of days after quarter-end or year-end, and missing that window is itself sometimes a technical default independent of the underlying financial performance.
If the agreement specifies a trailing-twelve-month test, confirm which four quarters that trailing period actually covers — a detail easy to get wrong once a fiscal year boundary is crossed.
Gather the current period's financial statements
Collect the income statement, balance sheet, and any supporting schedule — a debt amortization schedule, a fixed asset roll-forward — that the covenant calculation draws on. Use finalized, internally reviewed figures rather than a preliminary close that might still change.
Pull the calculation schedule from your credit agreement
Confirm exactly what your credit agreement requires — which ratios are tested, how each is defined, what add-backs are permitted, and what the specific threshold is for each. Don't assume this quarter's schedule matches last quarter's without checking, particularly if the agreement has been amended.
Extract each ratio's required inputs
Pull the specific figures each ratio needs — EBITDA components and permitted add-backs, total debt, interest expense, current assets and liabilities — from the financial statements gathered in step two. Use the same method used in prior quarters for each line item, so the resulting trend is actually comparable period over period.
Cross-check figures against bank records
Where the covenant schedule references cash flow or debt service actually paid, confirm the reported figures tie out to what the bank records actually show for the period. A gap here — a debt service payment accrued but not yet cleared, for instance — is usually a timing difference, but it's worth confirming rather than assuming.
Calculate each ratio and compare to threshold
Apply your credit agreement's specific formula to the extracted inputs, and compare the result against the threshold the agreement sets. Note the headroom — the gap between the actual ratio and the threshold — not just whether the test passes, since a shrinking cushion over several quarters is worth tracking even when every individual quarter passes.
| Covenant | Threshold vs. actual |
|---|---|
| Leverage ratio (max) | 3.50x threshold, 3.10x actual — 0.40x headroom |
| Interest coverage (min) | 2.00x threshold, 2.65x actual — 0.65x headroom |
Document any near-miss or discrepancy
For anything that doesn't tie out cleanly, or a ratio that lands closer to its threshold than usual, keep a short written explanation with supporting evidence — a bank confirmation, an invoice, a note on why an add-back applies this quarter. Having this ready before submission means a lender's question gets an immediate, evidenced answer.
Assemble and submit the package
Compile the financial statements, the completed calculation schedule, and the officer's certificate into whatever format your credit agreement specifies, and submit before the deadline confirmed in step one.
Keep a copy of the full package, including the underlying financial statements it was built from, in your own records — the next quarter's trailing calculation, and any future lender question, will draw on exactly this file.
A worked example, start to finish
A mid-sized manufacturer with a single term loan and a quarterly leverage covenant walks through these eight steps every quarter. Here's what one real cycle looked like, condensed.
The reporting period was confirmed as the fiscal quarter ending June 30, with a certificate due 45 days later per the credit agreement — step one, done in minutes by checking the agreement's own reporting covenant section. The finance team then gathered the finalized income statement, balance sheet, and a debt amortization schedule showing the term loan's scheduled principal for the period.
Pulling the calculation schedule confirmed the leverage covenant's definition hadn't changed since the prior quarter — no amendment on file — so the same EBITDA add-back categories applied. Extraction surfaced 24 inputs across the income statement and balance sheet, two of which were flagged: a legal settlement add-back that also appeared the prior quarter (worth confirming it was still genuinely one-time), and an interest expense figure that included a small facility fee the prior quarter's calculation had excluded.
| Step | Outcome this quarter |
|---|---|
| Inputs extracted | 24 figures, 2 flagged for review |
| Bank cross-check | 1 timing difference found (accrued vs. cleared interest), confirmed benign |
| Leverage ratio result | 3.10x actual against a 3.50x threshold — 0.40x headroom |
| Discrepancy documented | Facility fee inclusion corrected, noted in the package |
| Time from start to submission | 1 hour 40 minutes, second quarter using the same routine |
Correcting the interest expense figure to match the prior quarter's method — excluding the facility fee, consistent with how the credit agreement defines interest expense for covenant purposes — nudged the leverage ratio slightly, but the certificate that went out reflected the corrected, consistent figure rather than the first pass. That correction, caught before submission rather than during a lender's own review, is the entire point of steps four through seven.
A printable checklist
A short version of the eight steps, worth keeping next to your calculation schedule every quarter.
| Check | Done when |
|---|---|
| Period and deadline confirmed | Reporting period and submission date verified against the credit agreement |
| Statements gathered | Finalized income statement, balance sheet and supporting schedules collected |
| Schedule confirmed current | No unnoticed amendment to ratio definitions or thresholds |
| Inputs extracted consistently | Every figure uses the same method as the prior quarter |
| Bank cross-check complete | Reported cash flow and debt service tie to actual bank activity |
| Ratios calculated with headroom noted | Not just pass/fail — the margin against threshold is recorded |
| Discrepancies documented | Anything that didn't tie out cleanly has a written explanation |
| Package submitted on time | Financial statements, schedule and certificate sent before the deadline |
What happens after you submit
Submission isn't the end of the cycle — a lender's credit team typically re-performs at least the ratio calculations against the figures in the package, and larger facilities often include a spot-check against the underlying financial statements themselves. A discrepancy the lender finds that your own review missed is a materially worse outcome than the same discrepancy caught and explained in step seven.
Keep the full package — including the source financial statements it was built from, not just the final schedule — in an easily retrievable place. The next quarter's trailing calculation will reference this exact file, and so will any question that comes back from the lender's review, sometimes weeks after submission.
How much time each step actually takes
On a facility with one or two covenants, using software to match figures rather than retyping them by hand, the whole process — gathering statements, extracting inputs, cross-checking against bank records, and assembling the package — typically takes one to two hours once a routine is established.
Done entirely by hand on the same facility, the extraction and cross-checking steps alone can take the better part of a day, which is the main reason those steps so often get compressed under a tight deadline.
Common mistakes worth avoiding
Applying an add-back inconsistently — included one quarter, dropped the next, without a documented reason — produces a ratio trend that doesn't reflect the business and draws exactly the kind of scrutiny a clean package avoids.
Treating a passing ratio as the end of the analysis, without noting how much headroom remains, misses the early-warning value the whole exercise is supposed to provide — a ratio that passes by a shrinking margin every quarter is worth flagging internally well before it actually fails.
And waiting until close to the deadline to start compresses the time available to investigate a genuine discrepancy calmly, turning what should be a routine reconciliation into a scramble.
Preparing across more than one facility
A borrower with more than one facility needs to run this checklist once per facility, since different lenders often define similar-sounding ratios differently. Combining inputs before calculating risks masking a discrepancy specific to one facility with an unrelated figure from another.
Once each facility's package has been prepared independently, rolling the results into one internal summary for your own tracking is useful — just keep each facility's specific definitions and calculations traceable separately, since that's the level of detail a lender from either facility will actually ask about.
Doing this with software vs. by hand
Every step in this guide can be done manually with a spreadsheet and a careful eye, and many smaller borrowers do exactly that. What changes with the number of covenants and facilities isn't whether it's possible by hand — it's how long it reliably takes and how much a tired reviewer's attention degrades on the fifteenth line item compared to the first.
Software built specifically for matching financial statement figures to a calculation schedule removes exactly the part of the process where manual review is weakest: sustained, repetitive precision across dozens of line items where a single misread figure is easy to miss and consequential to get wrong.
That doesn't remove judgment from the process — deciding whether an add-back genuinely applies, interpreting a credit agreement's specific language, deciding how to handle a near-miss — stays with a person who understands the facility. What changes is how much of the routine, error-prone extraction work competes for that person's attention before the judgment calls even come up.
If this is your first compliance package ever
A first-time compliance package, with no prior quarter to compare against, understandably takes longer — there's no established baseline for how each add-back was calculated or which line items feed which ratio.
The eight steps in this guide apply the same way the first time as the twentieth. What's worth doing differently the first time is documenting the method used for each input as you go — which line item, which statement, which add-back category — so the second quarter's preparation has a clear baseline to match rather than starting from scratch again.
Who this guide is for
CFOs and controllers
Preparing a quarterly compliance package with confidence in the underlying figures.
Finance teams new to a covenant-bearing facility
A clear, repeatable process for a task that's easy to under-scope the first time.
Companies with multiple facilities
Coordinating compliance preparation across lenders and covenant packages.
Outside accountants supporting a client's certificate
A structured checklist to apply consistently across engagements.
A simple internal template
Formal certificate wording is set by the credit agreement, but the internal working document a finance team uses to get there doesn't need to be complicated — a single tab per covenant, tracking the same handful of columns every quarter, is usually enough.
| Column | What goes here |
|---|---|
| Quarter | The reporting period, e.g. Q2 2026 |
| Ratio and threshold | e.g. Leverage ratio, max 3.50x |
| Calculated result | This quarter's actual ratio |
| Headroom | Threshold minus (or divided by, depending on the ratio) actual |
| Add-backs applied | Each add-back category used, with a one-line reason |
| Flags this quarter | Anything that didn't tie out cleanly, with resolution |
| Source documents | Which statements the figures came from, filed where |
Kept up every quarter, this same sheet becomes the multi-year history a lender asks for at renewal — no separate reconstruction project, just an export of what was already being tracked.
Quarterly certificates vs. annual review
Most maintenance covenants are tested quarterly, but many credit agreements also layer on an annual requirement — audited financial statements, an annual compliance certificate covering the full fiscal year, sometimes a more detailed review than any single quarter requires on its own.
The eight steps in this guide apply to both, with one difference worth planning for: an annual package usually needs audited, not just internally reviewed, financial statements, which take longer to finalize than a quarterly close. Building extra lead time into the annual cycle — rather than assuming it moves at the same pace as a routine quarter — avoids a last-minute compression of the review steps that matter most.
A related detail worth flagging in advance: an auditor's year-end adjustment can shift a figure that already fed a quarterly certificate submitted months earlier — a reclassification between operating and non-operating expense, for instance. When that happens, it's worth a quick check on whether the adjustment is material enough to warrant a note to the lender, rather than leaving a quietly restated prior-quarter figure sitting unexplained in the file.
Many credit agreements are also more explicit about what the annual package requires than the quarterly one — a management discussion section, a budget-to-actual comparison, sometimes a formal auditor's letter addressed directly to the lender. Confirming the full annual requirement list well ahead of the deadline, not just assuming it's a bigger version of the usual quarterly package, avoids discovering a missing component the week submission is due.
Handing this off to someone else
A compliance process that lives only in one person's head is a real risk, and not a theoretical one — finance teams turn over, people go on leave, and the quarter someone is unexpectedly unavailable is exactly the quarter a deadline doesn't move to accommodate it. Building this eight-step process so a second person could pick it up mid-cycle is worth doing before it's needed, not after.
The single highest-leverage thing to hand off isn't the spreadsheet itself — it's the reasoning behind each recurring judgment call. Why this specific add-back category is used every quarter. Why last year's facility fee gets excluded from the interest expense calculation. Which line item on the income statement actually feeds which row of the schedule, when the two don't share an obvious label. None of this is visible from the final numbers alone, and all of it is exactly what a replacement preparer needs to avoid reinventing the process from scratch — or worse, reinventing it slightly differently, introducing an inconsistency the next lender review will catch.
A short written note attached to the calculation schedule — not a formal policy document, just a few sentences per recurring judgment call — closes most of this gap. The test worth applying: could someone with no prior context on this specific facility follow the note and arrive at the same figure a person who'd done it for years would? If not, the note needs one more sentence, not a longer document.
It's worth revisiting that note at least once a year even without a personnel change — a reasoning note written two facilities and three add-back categories ago can quietly drift out of date, and catching that drift during a calm annual review is far better than a successor discovering it mid-certificate under deadline pressure.
A second, lighter-weight option that works well for smaller finance teams: a brief recorded walkthrough of one full quarter's preparation, from opening the financial statements to submitting the finished package. A ten-minute recording captures the actual working process — which tabs get checked first, where a specific figure typically comes from — in a way a written procedure often struggles to convey as clearly.
Whichever format is used, the goal is the same: reduce the distance between “the person who knows this facility” and “whoever needs to prepare this quarter's certificate” to as close to zero as practical, so a single absence or departure never becomes the reason a deadline gets missed.
None of this requires expensive tooling or a formal knowledge-management platform — a shared folder with the calculation schedule, the reasoning note, and (optionally) a short recording is enough for most finance teams. What matters is that all three live somewhere a second person can actually find them without asking the first person where to look, since the whole point of the exercise is removing that single point of dependency. A quarterly reminder to glance at the folder and confirm nothing has silently gone stale costs a few minutes and catches drift long before a deadline forces the issue.
Treat this handoff material the same way the certificate itself is treated: version it, date it, and update it whenever the underlying facility or add-back policy actually changes, rather than letting it sit untouched until someone needs it and finds it out of date. A five-minute review at the start of each new facility year is usually enough to keep it current.