1---2name: draft-credit-compliance-cert3task_id: banking-finance/draft-credit-compliance-cert4description: Prepares a quarterly covenant compliance package consisting of a compliance memo, a calculation workbook, and an officer-certifiable certificate, including independent verification of the borrower's preliminary figures.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-credit-compliance-cert8---910# Skill: Quarterly Compliance Certificate Preparation — Complete Covenant Package1112## 1. Subject-matter triage13- Treat this as a quarterly compliance package with three coordinated outputs: a memo, a calculation workbook, and a certificate.14- Start by locating the operative credit-agreement definitions, covenant tests, reporting deadlines, and any specified calculation methodology.15- Determine whether the period is a full quarter, stub period, or otherwise non-standard; the annualization method must follow the agreement, not generic practice.16- Identify every covenant and certificate representation that is implicated by the quarter-end financials before drafting any narrative.17- If multiple borrower-prepared schedules or management worksheets are attached, enumerate them and reconcile each against source financials before using any figure.1819## 2. Failure modes the skill is correcting20- Producing a narrative memo or simplified certificate without the required calculation workbook.21- Using the borrower’s preliminary numbers without independent recalculation from the source financials.22- Applying the wrong annualization method for a partial period or stub quarter.23- Omitting debt components that the agreement treats as debt, including contingent, accrued, or lease-related items.24- Ignoring covenant-specific addback caps, time limits, or cumulative trackers.25- Failing to surface the deadline for delivery or the consequences of late delivery.26- Certifying no default when the calculations disclose a breach, potential breach, or unresolved assumption.27- Treating exclusions or deductions as permissible without locating the specific contractual language that authorizes them.2829## 3. Legal frameworks / domain conventions that apply30- Read the debt, EBITDA, fixed-charge, and coverage definitions as integrated contractual terms; each defined term may cross-reference other definitions, schedules, or exhibits.31- Use the agreement’s own accounting conventions, including any expressly required treatment of GAAP, lease accounting, accrued obligations, and contingent liabilities.32- Apply any express limitation periods, forward-looking windows, or trailing periods exactly as written.33- Test each covenant against the correct threshold and measurement date, using conservative assumptions where the agreement leaves room for interpretation.34- Verify whether the certificate must be delivered within a fixed post-quarter window and whether failure to do so is an independent default.35- If the certificate requires a no-default statement, tie that statement to the outcome of the covenant analysis and any known carve-outs or disclosure qualifiers.36- Where the agreement incorporates statutory or regulatory concepts by reference, cite them only if they are actually needed to explain the calculation methodology or reporting obligation; otherwise keep the analysis contract-specific.37- For New York law-governed credit documents, construe the agreement according to ordinary contractual principles, with each defined term controlling its own calculation field.3839## 4. Analytical scaffolds401. **Source inventory**41 - List the agreement excerpts, financial statements, management schedules, and any borrower worksheet that will be tested.42 - Identify which document controls each term, threshold, and deadline.432. **Debt build**44 - Recalculate total debt from the balance sheet and footnotes.45 - Include all items the agreement treats as debt or debt-like obligations, and exclude only items clearly outside the definition.46 - Reconcile any debt rollforward, lease liability, or contingent exposure item separately.473. **EBITDA build**48 - Start from the agreement’s base measure and rebuild the permitted adjustments.49 - Remove any item that is not affirmatively permitted by the definition.50 - Test each addback against its own conditions, carryforward rules, and any cumulative or annual cap.514. **Periodization / annualization**52 - If the period is not a full fiscal year, apply the agreement’s required trailing or annualized methodology.53 - State the rationale for the methodology used and the effect on each covenant metric.545. **Covenant tests**55 - Compute each leverage, coverage, or fixed-charge ratio using the corrected inputs.56 - Compare each result to the contractual threshold and identify headroom or shortfall using the agreement’s own measurement convention.576. **Cap and usage tracking**58 - Track every capped adjustment in a separate ledger showing current-period usage, cumulative usage, and remaining capacity.59 - Tie each tracked amount back to the exact contractual cap it consumes.607. **Worksheet audit**61 - Compare the borrower’s preliminary schedule line by line against the recalculated output.62 - Flag any unsupported inclusion, omission, formula error, sign error, or timing mismatch.638. **Certificate consistency**64 - Ensure the certificate, memo, and workbook all state the same covenant outcome and assumptions.65 - If any assumption is judgmental, disclose it consistently across all deliverables.669. **Downside check**67 - Run a conservative sensitivity view that shows the effect of disallowing disputed addbacks or reclassifying borderline items.68 - Use the downside view to test whether the certificate remains supportable.6910. **Deadline check**70 - Measure the delivery date from the quarter end using the agreement’s reporting window.71 - Flag any timing risk, including the need for lender notice if a late or corrective filing is anticipated.7273## 5. Vertical / structural / temporal relationships74- Separate the analysis by reporting period, covenant type, and source document so each row traces to a single control term.75- Distinguish present-quarter items from cumulative amounts that roll across quarters or fiscal periods.76- Keep current-period addbacks distinct from lifetime or rolling caps; do not mix the periods in a single line.77- Where one definition feeds another, preserve the dependency chain explicitly so the workbook can be audited from input to final ratio.78- If the agreement uses multiple measurement dates or test points, analyze each one separately rather than averaging across periods.7980## 6. Output structure conventions81- **Compliance memo (.docx):** concise narrative explaining the source documents reviewed, methodology used, assumptions made, calculation issues found, covenant outcomes, reporting deadline, and any certification caveats.82- **Calculation workbook (.xlsx):** include clear tabs for EBITDA reconciliation, debt calculation, each covenant test, sensitivity analysis, and capped-item tracking; formulas should trace from source inputs to final ratios.83- **Compliance certificate (.docx):** use an officer-certifiable form that states the tested period, the covenant results, the delivery basis, and any required qualification or reservation language.84- Present all calculations conservatively and label every assumption that affects covenant headroom.85- If more than one covenant, addback, or debt component is implicated, enumerate each item before analysis and carry each through to a discrete worksheet row.86- End the memo with specific recommended actions, each tied to a responsible role and a filing or delivery milestone.87- Before finalizing, confirm by name that the memo, workbook, and certificate are all complete, non-empty, and mutually consistent.