Lender Reporting Package

Executive summary

A lender reporting package is the set of financial statements, certificates, and schedules you owe your lenders on a defined calendar. It is a contractual deliverable, not a courtesy. Late or wrong reporting can be a default by itself, even when the business is performing well.

One point comes before everything else. Your own credit agreement defines exactly what you must deliver, when, in what form, and how every ratio is calculated. Nothing in this guide overrides that document. Terms such as EBITDA, Total Debt, and Fixed Charges mean what your agreement says they mean, and they often differ from the way you define them internally. This guide is operating guidance, not legal advice. Have counsel and your lender relationship contact confirm anything that is ambiguous.

Within that boundary, most of the work is operational. Turn the agreement into a reporting obligations register. Build the package from the same close that feeds the board pack. Compute each covenant on the agreement's definition, with a reconciliation to your internal numbers. Send it on time, with a short narrative that tells the lender what they would otherwise have to ask. Companies that do this rarely have a hard conversation with a lender that surprises them.

When to use this

Use this guide when:

• You have closed a new credit facility and need to stand up the reporting process.
• You are late, or nearly late, on a recurring lender deliverable.
• Your compliance certificate takes more than a day or two of senior finance time to produce.
• Headroom on a covenant is tightening and you want to give the lender a better view than a bare ratio.
• A sponsor, a new CFO, or a refinancing process is asking how lender reporting currently works.

If you do not yet have a view of covenant headroom in advance, read covenant compliance and headroom tracking alongside this one. That guide covers forecasting the ratios. This one covers delivering them.

Diagnostic questions

Answer these before changing anything. Most can be answered from the credit agreement and the last four packages you sent.

1. Where is the reporting section of the credit agreement, and has anyone in finance read it in full in the last year?
2. Is there a single register that lists every deliverable, its due date, its recipient, and its owner?
3. How many days after period end was each of the last four packages sent, relative to the contractual deadline?
4. Is each covenant calculated from a definition written into the agreement, or from a spreadsheet someone built from memory?
5. Can you reconcile the covenant EBITDA in the certificate to the EBITDA in the board pack, line by line?
6. Which adjustments or add-backs do you claim, and does the agreement explicitly permit each one, with any caps?
7. Who signs the compliance certificate, and what do they review before signing?
8. What happens when the monthly close slips: does the package slip too, or is there a fallback?
9. Does the lender receive the same numbers the board does, or two versions that differ?
10. Have any lender questions in the last two quarters been ones you could have answered in advance in the package?
11. Which covenants are tested only quarterly, and which reporting items are monthly or annual?
12. If a covenant breach were forecast for next quarter, who would call the lender, and when?

Reading the answers: if questions 1 and 2 are weak, the risk is a missed obligation. If questions 4 to 6 are weak, the risk is a miscalculated covenant. If questions 9 and 10 are weak, the risk is a trust problem, which is the harder one to repair.

The framework: four layers of a lender package

The common failure is to build only layers 2 and 3 and skip layers 1 and 4. Layer 1 prevents missed deadlines. Layer 4 is what makes a lender comfortable rather than merely informed.

Step-by-step process

1. Extract the reporting obligations. Read the reporting covenants, affirmative covenants, and definitions sections of the agreement and every amendment. List each deliverable: annual audited statements, quarterly and monthly unaudited statements, compliance certificates, budgets, borrowing base certificates if you have a revolver with one, insurance evidence, notices of specified events. Owner: CFO with counsel. Output: the obligations register (template below).
2. Confirm interpretation. For each ambiguous item, such as the definition of a period, the accounting basis, or what counts as a material event, get written confirmation from counsel or the agent. Do not assume. Output: a short interpretation log kept with the register.
3. Define each covenant formula as written. Copy the definition language into a calculation sheet next to the formula. Note the basis (trailing twelve months, quarterly annualized, and so on), the permitted adjustments, and any caps. Owner: FP&A. Output: a covenant calculation workbook.
4. Build the reconciliation. Create a bridge from your internal EBITDA to the covenant EBITDA, and from internal debt to the agreement's debt definition. Every difference gets a label and a source. Owner: FP&A. Output: one reconciliation page per covenant.
5. Set the production calendar. Work backward from each contractual due date. Show close complete, FP&A review, CFO review, officer sign-off, delivery, and a buffer. Owner: Controller. Output: a business-day calendar tied to the close (see the 10-day close plan).
6. Assemble the package from the closed ledger. Pull statements after the books are locked. Do not build from a draft close that will change. Owner: Controller.
7. Calculate, check, and review the certificate. FP&A prepares it, a second person recalculates every ratio independently, and the signing officer reads the definitions and the supporting schedules, not only the result. Owner: CFO. Output: a signed certificate and a reviewed support file.
8. Write the narrative. One page: what changed, why (see variance analysis narrative), what you expect next quarter, and anything you want to flag early. Owner: CFO.
9. Deliver and log. Send through the channel the agreement specifies. Keep proof of delivery and the exact files sent. Owner: Controller.
10. Debrief and forward-test. After each cycle, update the covenant forecast for the next test date and note any process slips. Owner: FP&A.

Templates

Reporting obligations register

Copy the due-date rule exactly as written. Some agreements count calendar days, some business days, and some key off fiscal quarter end rather than month end.

Covenant calculation sheet

EBITDA reconciliation bridge

Package contents checklist (adapt to your agreement)

• Cover note and one-page narrative.
• Income statement, balance sheet, and cash flow statement for the period and comparatives, on the basis the agreement requires.
• Compliance certificate signed by the authorized officer.
• Covenant calculation schedule and EBITDA and debt reconciliations.
• Forecast or budget, if required, with key assumptions.
• Borrowing base or collateral reporting, if your facility has one.
• Notice of any event the agreement requires you to notify.

Metrics and KPIs

Setting targets without invented benchmarks. The delivery target is contractual: the due date in your agreement, with an internal deadline that leaves a buffer. The headroom floor is also yours to set by method. Take the cushion at which you would have to call the lender, add the time it takes to take corrective action, and size the internal early-warning level above that. Your own trailing four quarters of results show how much the ratio typically moves in a quarter. Do not copy a number from another company's agreement, because definitions and levels differ.

Common mistakes

1. Working from a summary of the agreement. The summary in someone's head, or in the original term sheet, drifts from the signed document and its amendments. Work from the executed text.
2. Claiming an add-back the agreement does not permit. An internally reasonable adjustment is not a covenant adjustment. If the agreement does not list it, or caps it, the certificate must follow the agreement.
3. Two sets of numbers. If the lender package and the board pack show different EBITDA without a reconciliation, someone will ask why. Build the bridge once and include it.
4. Building from a draft close. A package assembled before the books are locked will be restated.
5. Signing without reading the definitions. The officer's signature is a representation. Reviewing only the final ratio is not review.
6. Silence before a miss. Lenders usually respond better to an early, specific conversation with a plan than to a certificate that shows a breach with no warning.
7. No second preparer. A ratio calculated by one person from one spreadsheet is a single point of failure.
8. Ignoring non-financial deliverables. Insurance certificates, notices, and budget submissions are in the agreement too, and missing one can matter as much as missing a ratio.

Worked example (illustrative)

The figures below are made up to show the method. They are not benchmarks and do not reflect any real agreement. The covenant levels are placeholders.

A manufacturer must test two covenants at quarter end on a trailing twelve month (TTM) basis: maximum net leverage of 3.75x and minimum fixed charge coverage of 1.20x. The agreement defines both, including a permitted restructuring add-back and a cap on cash netted against debt. Amounts in $ millions.

Covenant EBITDA

Net debt, as defined in the agreement

Net leverage = 21.7 ÷ 7.1 = 3.06x, against a maximum of 3.75x.

Headroom

• EBITDA at which leverage would reach 3.75x: 21.7 ÷ 3.75 = 5.79. EBITDA could fall from 7.1 to 5.79, a cushion of 1.31, which is 18.5% of covenant EBITDA, before the covenant is breached with debt unchanged.
• Debt capacity at current EBITDA: 3.75 × 7.1 = 26.6, less net debt of 21.7 = $4.9M of additional net debt.

Fixed charge coverage

Coverage = 4.6 ÷ 3.2 = 1.44x, against a minimum of 1.20x. The numerator could fall to 1.20 × 3.2 = 3.84, a cushion of 0.76 or 16.5%.

What the operator does with this. The binding covenant is fixed charge coverage, not leverage, because its cushion (16.5%) is smaller than the leverage cushion (18.5%). The narrative for the lender should lead with that, state what drives capex and scheduled principal next quarter, and show the forecast. The reconciliation page should show the $0.3M restructuring add-back with its support and the clause that permits it. If the add-back were disallowed, covenant EBITDA would be 6.8 and leverage 21.7 ÷ 6.8 = 3.19x, so the sensitivity is worth showing.

Every figure above was recomputed by script and ties: 6.8 + 0.3 = 7.1; 18.0 + 4.5 + 1.2 = 23.7; 23.7 − 2.0 = 21.7; 7.1 − 1.9 − 0.6 = 4.6; 1.4 + 1.8 = 3.2.

AI prompt assistance

AI can speed up the preparation work. It cannot read your agreement authoritatively, and it should never be the final reviewer of a certificate. Supply your own extracts and verify against the executed document.

1. Build the obligations register.

Below is the text of the reporting and affirmative covenants section of our credit agreement. List every deliverable as a table with: description, frequency, due date rule quoted exactly, recipient, and the section number. Do not interpret ambiguous wording; mark it "ambiguous" and quote it.

Check: read the source sections yourself against the table, and send anything marked ambiguous to counsel.

2. Draft the reconciliation bridge.

Here is our internal EBITDA by line and the EBITDA definition from the credit agreement. Produce a bridge from internal EBITDA to covenant EBITDA, listing each adjustment, whether the definition appears to permit it, and the clause that you relied on. Flag every adjustment where the definition is unclear or a cap might apply.

Check: confirm each clause reference is real by reading it, and have counsel or the lender confirm any flagged item.

3. Draft the lender narrative.

Using this period's variance commentary and covenant results, write a one-page note to our lender: what changed, covenant results and headroom, next quarter expectations, and risks. Use plain language. Do not add any numbers that are not in the inputs.

Check: tie every number to the package, and have the CFO approve before sending.

4. Review the certificate for internal consistency.

Here are the compliance certificate calculations and the financial statements. Recompute each ratio and list any input that does not tie to the statements. Show each calculation.

Check: independently recompute at least one ratio by hand.

Implementation guide

Governance: the CFO owns the relationship and the narrative, the Controller owns the calendar and delivery, FP&A owns calculations, and the authorized officer owns the signature. Review the obligations register at each month-end close and again whenever the agreement is amended.

Downloadable assets

The obligations register, covenant calculation sheet, EBITDA bridge, and package checklist above are designed to be copied into a spreadsheet. The covenant headroom calculator can test the headroom arithmetic once you have entered the definitions from your own agreement.

Related resources

• Covenant compliance and headroom tracking: forecasting ratios ahead of the test date.
• Management reporting playbook: the internal reporting the lender package should be consistent with.
• Board reporting pack template: the board view of the same numbers.
• Variance analysis narrative: writing the explanation behind the numbers.
• Board reporting hub: all reporting guides in one place.

Frequently asked questions

What goes in a lender reporting package?

The contents are set by your credit agreement. Typically that means periodic financial statements, a signed compliance certificate with covenant calculations, and any schedules or notices the agreement names, such as a budget or borrowing base. Read the reporting section of the executed agreement and every amendment, and list each item with its due date.

Who defines how covenants are calculated?

Your credit agreement defines every covenant ratio, including what counts as EBITDA, debt, and fixed charges. Internal definitions often differ, so build a reconciliation between the two. If any definition is unclear, ask counsel or your lender contact in writing rather than relying on assumption.

How early should you tell a lender about a possible covenant breach?

As early as you can support with a specific forecast and a plan. This guide does not give legal advice, so check what your agreement says about notice and cure rights with counsel. Operationally, a lender hearing about a tight quarter before the certificate arrives is usually in a better position to work with you.

How do you measure covenant headroom?

Headroom is how far the underlying metric can move before the covenant is breached. For a leverage covenant, divide net debt by the maximum ratio to find the minimum EBITDA, then compare it to actual EBITDA. Measure it on the next test date's forecast as well as the current period.

Should the lender package match the board pack?

The underlying numbers should come from the same closed ledger, and any difference should be explained in a reconciliation. Covenant EBITDA often differs from board-pack adjusted EBITDA because the agreement limits add-backs. Show the bridge so no reader has to ask.

How this works in a System of Performance

A lender package fails at the seams: the covenant definition lives in a PDF, the inputs sit in the ERP, the add-back support is in email, and the headroom forecast is in a separate workbook. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see how your own reporting obligations hold up, bring it to us as a launch partner.