Article map
Financing agreements create obligations long after drawdown: covenant tests, compliance certificates, management accounts, audited statements, utilisation notices, interest elections, rating notifications, insurance evidence and restrictions on acquisitions, dividends or security. These duties may differ by facility, lender and borrower even within one group.
A missed information undertaking can trigger fees, reservation of rights or default risk even when the financial covenant itself is healthy. Treasury therefore needs a controlled calendar that translates legal text into executable tasks, calculation definitions, evidence and approvals.
This article explains how a TMS can manage those obligations while preserving legal interpretation and the relationship between source numbers, certificate and lender communication.
1. Create an obligation register from executed documents
Every requirement should be captured with its source clause, applicability, frequency, trigger and consequence. Summaries are useful, but users must be able to return to the executed document and amendment in force.
The operating boundary should define:
- facility, borrower, guarantor and lender group
- obligation type, clause reference and plain-language description
- fixed date, recurring frequency or event-driven trigger
- submission channel, notice period and authorised signatory
- breach consequence, cure right and escalation owner
The register should be effective-dated so that waivers and amendments change future obligations without erasing the prior legal position.
2. Define covenant calculations as governed data products
Covenant terms may differ from accounting or management-reporting definitions. EBITDA, net debt, cash, permitted acquisition and exceptional item adjustments should be implemented exactly as agreed for that instrument.
The governed data record should capture:
- formula, numerator, denominator and testing period
- permitted, prohibited and discretionary adjustments
- entity perimeter and currency translation
- source accounts, consolidation logic and manual inputs
- headroom, threshold, cure and forecast methodology
The TMS should not assume that one corporate leverage ratio can be used for every facility. Similar labels can conceal materially different definitions.
3. Run a preparation, review and submission workflow
The compliance cycle should begin early enough to collect data, calculate, challenge, approve and obtain signatures before the contractual deadline. The workflow should separate preparer, reviewer and authorised signatory.
The end-to-end workflow should make visible:
- automatic task creation from the obligation calendar
- data collection and calculation with version lock
- finance, treasury, legal and management review as required
- certificate generation from approved values
- submission evidence, lender acknowledgement and query tracking
A certificate is not complete when it is emailed. The process should retain proof of delivery and any lender response or follow-up.
4. Control judgement, waiver and breach scenarios
Forecast or actual pressure should trigger early escalation. Treasury should not wait for a failed certificate date before engaging management and advisers. Waiver discussions, cure actions and lender consent must remain controlled and confidential.
The control architecture should address:
- early-warning threshold above the legal limit
- approval and evidence for covenant adjustments
- legal review of potential breach and notification duties
- waiver, amendment or equity-cure milestones
- restricted access to sensitive lender strategy and communications
The TMS should distinguish forecast concern, calculation dispute, actual breach and waived breach. Combining them in one red status can mislead management and auditors.
5. Connect compliance to debt, forecast and corporate action
The obligation register should interact with debt schedules, liquidity forecasts and planned transactions. A dividend, acquisition or new security may require consent even when no recurring deadline is near.
The TMS configuration should support:
- instrument and facility terms
- forecast covenant headroom by scenario
- planned borrowing, repayment, acquisition and distribution events
- consent, notification and negative-pledge rules
- document and approval dependencies before corporate action
This connection turns compliance from a retrospective reporting task into a decision control applied before commitments are made.
6. Measure completeness, timeliness and headroom
Metrics should cover both administrative obligations and financial risk. A portfolio can have strong covenant headroom while still accumulating overdue reports and unacknowledged submissions.
Management reporting should measure:
- obligations due, completed, overdue and awaiting acknowledgement
- days of lead time consumed by preparation and approval
- covenant headroom actual and forecast by facility
- manual adjustments, late data and lender queries
- waivers, consents and temporary conditions outstanding
The dashboard should identify the contractual borrower and responsible owner, not only aggregate to the group level.
7. Validate the calendar periodically and after change
Executed amendments, new utilisation, refinancing and corporate events can change obligations. Treasury should perform periodic legal and operational validation of the register.
The implementation plan should sequence:
- reconcile active facilities to executed documents
- review amendment, waiver and side-letter effects
- confirm lender contacts and submission channels
- test upcoming tasks and certificate templates
- retire obligations only after legal confirmation and final evidence
A compliance calendar is reliable only when it remains aligned to the current document set, not the terms originally entered at deal close.
Management questions before approval
Before management approves debt compliance calendar, the discussion should test the boundary described by create an obligation register from executed documents, the reliability of formula, numerator, denominator and testing period, and whether early-warning threshold above the legal limit remains effective when an exception occurs. It should also ask how obligations due, completed, overdue and awaiting acknowledgement will reveal whether the decision delivered its intended treasury result.
- Are all active financing documents represented?
- Does every obligation retain a clause reference?
- Are event-driven as well as recurring duties captured?
- Are covenant formulas instrument-specific and versioned?
- Are manual adjustments approved and evidenced?
- Does workflow allow time for review and signature?
The TMS record should connect those answers to run a preparation, review and submission workflow and to the action 'reconcile active facilities to executed documents'. Where judgement changes the normal route for debt compliance calendar, the evidence, approver, effective date and next review should remain visible beside instrument and facility terms.
Evidence a controlled TMS should retain
The operating record for debt compliance calendar should show how formula, numerator, denominator and testing period became an approved action under control judgement, waiver and breach scenarios. It should retain source identity, calculation or transformation, workflow status, exception treatment and approval, together with the downstream result represented by instrument and facility terms.
- early-warning threshold above the legal limit
- approval and evidence for covenant adjustments
- legal review of potential breach and notification duties
- instrument and facility terms
- forecast covenant headroom by scenario
- planned borrowing, repayment, acquisition and distribution events
Version history for formula, numerator, denominator and testing period should preserve the information used when the decision was taken, even if later correction changes the current view. Comparing that history with obligations due, completed, overdue and awaiting acknowledgement and the practical outcome in 'two leverage ratios with the same name' allows management to evaluate process discipline and decision quality without hindsight rewriting.
Operating decision record
The decision record for debt compliance calendar should identify the event, the data cut supporting define covenant calculations as governed data products, the assumptions applied and the policy or mandate that governed the choice. It should compare the selected action with a realistic alternative, identify the accountable owner and approver, and state when 'retire obligations only after legal confirmation and final evidence' or another change will require reassessment. A decision not to proceed with 'reconcile active facilities to executed documents' should document the tolerance relied upon with the same discipline as an executed treasury action.
Continuity depends on linking that conclusion to document and approval dependencies before corporate action and to later evidence of waivers, consents and temporary conditions outstanding. Reviewers can then distinguish whether the original decision was reasonable on the information available from whether the eventual outcome in 'two leverage ratios with the same name' happened to be favourable or adverse.
Review cadence and change triggers
Routine review of debt compliance calendar should follow the cadence implied by automatic task creation from the obligation calendar, while an immediate refresh should occur when headroom, threshold, cure and forecast methodology, breach consequence, cure right and escalation owner or a material system configuration changes. The reviewer should compare the current position with the last approved analysis and test whether restricted access to sensitive lender strategy and communications and related limits remain valid.
A trigger may confirm that the existing create an obligation register from executed documents design remains suitable; it does not always require a new transaction or configuration change. Continued reliance should nevertheless become a dated conclusion, supported by forecast covenant headroom by scenario and reported through days of lead time consumed by preparation and approval. Any debt compliance calendar exception should carry an owner, interim treatment, escalation point and evidence of closure within the same TMS process.
Practical illustration: two leverage ratios with the same name
A group has a bank facility and a private placement, both containing a “net leverage ratio.” Treasury calculates one management ratio and assumes it demonstrates compliance with both. The private placement excludes cash held in certain subsidiaries and limits restructuring add-backs differently.
The TMS stores separate formula versions and source adjustments for each instrument. Forecast testing shows that the private placement has materially lower headroom, triggering earlier management action. Certificates are generated from the instrument-specific approved calculations and submitted through separate workflows.
The group avoids a false-compliance conclusion because the calendar controls definitions as carefully as due dates.
Implementation checklist
A treasury team preparing to operationalise this topic should be able to answer yes to the following questions:
- Are all active financing documents represented?
- Does every obligation retain a clause reference?
- Are event-driven as well as recurring duties captured?
- Are covenant formulas instrument-specific and versioned?
- Are manual adjustments approved and evidenced?
- Does workflow allow time for review and signature?
- Is delivery and lender acknowledgement retained?
- Are early-warning thresholds above legal limits?
- Do planned corporate actions trigger consent review?
- Is the register revalidated after amendment or waiver?
Common design failures
Debt compliance fails when organisations manage dates without legal definitions or calculate ratios without controlling the submission obligation.
- copying one covenant formula across facilities
- tracking only financial tests and ignoring information undertakings
- using a certificate spreadsheet disconnected from source data
- assuming email transmission proves contractual delivery
- waiting for actual breach before escalating forecast pressure
- allowing waivers to remain outside the effective-dated obligation register
A robust calendar makes every duty visible, gives calculations the same governance as reporting numbers and preserves evidence of what the lender received.
Closing perspective
Debt compliance is a continuing operating responsibility. The risk lies in definitions, triggers, evidence and decisions as much as in the date printed on a certificate.
A TMS can translate financing documents into a governed calendar linked to debt, forecast and corporate actions, improving both control and management foresight.
Frequently asked questions
What should a debt compliance calendar include?
Include recurring and event-driven covenants, certificates, information undertakings, notices, elections, consents, document references, owners, deadlines, approvals, submissions and acknowledgements.
Can one covenant calculation be reused across all facilities?
Only if the executed definitions are genuinely identical. Similar ratio names often have different entity perimeters, adjustments, cash definitions and testing rules.
How can a TMS help with lender reporting?
It can schedule obligations, source approved data, execute instrument-specific calculations, manage review and signature, generate certificates and retain submission and lender-response evidence.