Sanction schedule + compliance certificate → PASS / WATCH / BREACH — bank loan covenant tracking software in under 30 seconds per facility.
| Covenant | Direction | Threshold |
|---|---|---|
| DSCR | Floor (≥) | 1.25x |
| Debt / EBITDA | Cap (≤) | 3.00x |
| Interest Coverage | Floor (≥) | 2.50x |
| Current Ratio | Floor (≥) | 1.20x |
| TOL / TNW | Cap (≤) | 2.00x |
Manual bank loan covenant tracking breaks at scale. A treasury analyst at a mid-market borrower must test five financial ratios per facility, every quarter — and the process relies entirely on reading dense annexures in sanction letters and transcribing actuals from CFO-certified certificates by hand.
Indian lenders require a CFO-certified compliance certificate within 45 days of quarter-end. Missing that window constitutes a procedural default under the loan agreement — independent of whether any financial ratio has been breached. For a company tracking four facilities from two lenders, the calendar pressure is constant and the consequences of lateness are immediate.
Sanction letters are multi-annexure documents where covenant tables appear in Annexure III or later. A DSCR floor of 1.25x can sit inside a 40-page PDF between loan pricing grids and drawdown conditions. Reading the wrong annexure or misreading 1.25x as 1.52x produces a headroom figure that misleads management for the entire quarter until the lender's credit team runs its own test.
When a company carries three or four facilities from different lenders, each with its own threshold set and testing frequency, the manual approach creates a silent risk: a DSCR of 1.10x against a floor of 1.25x goes undetected until the lender raises it. By that point the 30-day cure period may be partially consumed, and the risk of accelerated repayment or facility cancellation is real.
A ratio within 10% of its breach threshold is a management call to action — reduce debt, accelerate receivables collection, or seek a temporary waiver — but spreadsheet-based covenant tracking rarely surfaces this proximity alert. The first signal a finance team gets is the breach itself, not the 30-to-45-day warning window that automated WATCH classification provides.
The time a finance analyst spends per facility, per quarter, on manual covenant compliance tracking — reading annexures, transcribing thresholds, cross-referencing certificates, building ratio tables, and drafting exception summaries. Under Ind AS 1, Paragraph 25, any undetected breach that has not been waived by the balance sheet date requires immediate reclassification of long-term debt as current, materially affecting the going-concern assessment.
Financial covenant compliance sits at the intersection of loan contract law, Indian accounting standards, and RBI prudential norms. Four regulatory anchors govern the consequences of a missed or late breach disclosure for a mid-market Indian borrower.
When a covenant breach has occurred and no waiver has been signed by the balance sheet date, management must reclassify the long-term loan as a current liability. Under Ind AS 1 paragraph 25, this assessment is mandatory; a failure to reclassify produces a material misstatement in the balance sheet that the statutory auditor must address under SA 570.
ICAI SA 570 (Going Concern) requires the statutory auditor to evaluate management’s assessment of covenant compliance and any breach scenarios. A breach without a signed waiver or a credible cure plan can produce an emphasis-of-matter paragraph or, in more severe cases, a qualified opinion on the financial statements — a material reputational and financing risk for listed and unlisted companies alike.
RBI’s Master Direction on Stress Asset Classification requires lenders to classify accounts as Special Mention Accounts (SMA-0, SMA-1, SMA-2) when covenant breaches are detected. A borrower who identifies a breach internally and discloses it proactively within the cure period has substantially better renegotiation leverage than one the lender classifies unilaterally based on its own covenant monitoring.
For listed entities, SEBI’s Listing Obligations and Disclosure Requirements Regulation 30 requires prompt disclosure of material events, which includes a covenant breach that could affect the company’s debt classification or lender relationships. Delays in covenant detection translate directly into delayed stock-exchange disclosures, increasing regulatory and investor-relations risk for CFOs of listed mid-market companies.
For a mid-market company without a dedicated treasury team, the practical failure mode is not outright fraud but delayed detection. Automating the extraction, computation, and classification of every covenant — across all facilities, every quarter — is the only way to guarantee the 30-to-45-day advance warning needed to take corrective action before the lender’s credit team acts first.
Seven deterministic passes from sanction schedule and compliance certificate to PASS / WATCH / BREACH classification — in under 30 seconds per facility, with a structured headroom table and timestamped exception log every controller can audit and reproduce.
Ingests the sanction letter PDF or covenant schedule XLSX and extracts all five covenant thresholds — dscr_threshold, debt_to_ebitda_threshold, interest_coverage_threshold, current_ratio_threshold, tol_tnw_threshold — along with facility ID, lender name, sanction amount, testing frequency, and cure period days. Direction (floor vs cap) is inferred from the covenant name and confirmed against the printed sign.
Ingests the CFO-certified quarterly compliance certificate and extracts the key financial line items: ebitda, debt_service, total_debt, interest_expense, current_assets, current_liabilities, total_outside_liabilities, tangible_net_worth, quarter_ended, and the CFO’s certified actuals for all five ratios.
Validates that the facility_id on the compliance certificate matches the facility_id from the sanction schedule (exact match, case-insensitive). A mismatch raises a Facility ID Mismatch FAIL exception and suspends ratio computation for that facility until the user confirms or corrects the document pairing — preventing a clean PASS on misaligned documents.
Computes each ratio independently from the certificate’s raw financial figures: DSCR = EBITDA ÷ Debt Service, Debt/EBITDA = Total Debt ÷ EBITDA, Interest Coverage = EBITDA ÷ Interest Expense, Current Ratio = Current Assets ÷ Current Liabilities, TOL/TNW = Total Outside Liabilities ÷ Tangible Net Worth. Cross-checks each recomputed value against the CFO-certified actual; any arithmetic discrepancy > 0.05 raises a Ratio Recomputation Mismatch WARNING.
Compares each computed actual against its sanction-letter threshold. Headroom is computed as (Actual − Threshold) for floor covenants and (Threshold − Actual) for cap covenants. Any ratio within 10% of its breach point is classified WATCH; any ratio past its threshold is classified BREACH; all others are PASS. The WATCH band for DSCR ≥ 1.25x spans 1.125x to 1.25x; for Debt/EBITDA ≤ 3.00x it spans 2.70x to 3.00x.
Any BREACH classification raises a FAIL exception with a lender-notification flag, records the applicable cure period (30 days in the standard Acme Bank demo), and displays the headroom as a negative value — for example, TOL/TNW headroom of −0.18x when actual is 2.18x against a 2.00x cap. The exception export includes a breach summary the CFO can attach to lender correspondence.
Compares the certificate’s quarter_ended date against its upload timestamp; if received outside the 45-day window, records a procedural default flag in the audit trail alongside the ratio results. All seven steps produce a timestamped Excel compliance pack — facility ID, borrower, lender, five thresholds, five actuals, five headroom values, and a PASS / WATCH / BREACH status column — directly usable as the statutory audit workpaper for Ind AS 1 going-concern assessments.
The workflow ships with a battery of synthetic test scenarios that exercise every failure mode encountered in real-world covenant data. Each scenario produces a deterministic outcome an auditor or controller can verify in seconds.
The workflow ships with two consolidated sample files covering a single testing period — quarter ended 31 Mar 2026 — across a 60-facility portfolio. Forty-eight facilities reconcile cleanly; twelve plant the workflow’s own exception classes.
facility_id. Each row carries borrower, lender (Acme Bank Ltd · Acme Commercial Bank · Acme Finance), sanction amount, and all five sanctioned thresholds plus testing frequency and cure period.
Standard thresholds per row: DSCR ≥ 1.25x, Debt/EBITDA ≤ 3.00x, Interest Coverage ≥ 2.50x, Current Ratio ≥ 1.20x, TOL/TNW ≤ 2.00x. Cure period 30 days; testing frequency Quarterly.
facility_id with the schedule. Each block lists raw EBITDA, debt service, total debt, interest expense, current assets/liabilities, TOL, TNW and certified actuals.
The twelve exceptions span: 2 DSCR breaches, 2 leverage WATCH rows (Debt/EBITDA 2.70x–3.00x band), 2 TOL/TNW breaches, 1 Interest Coverage breach, 1 Current Ratio breach, 2 late certificates, 1 ratio-recomputation mismatch, and 1 facility-ID mismatch.
All five ratios cleared thresholds with comfortable headroom. EBITDA ₹18.5 Cr vs debt service ₹13.2 Cr; recomputed DSCR 1.402x agrees with certified 1.40x within 0.05. Zero exceptions raised.
DSCR breach: EBITDA ₹14.2 Cr vs debt service ₹12.9 Cr = 1.10x, 12% below the 1.25x floor. Interest Coverage at 2.29x is 8.4% below its 2.50x floor — classified WATCH. FAIL exception raised with lender-notification flag and 30-day cure-period countdown.
A quarterly covenant compliance tracking process that takes a finance analyst one to two days per facility — reading annexures, transcribing thresholds, building ratio tables, and drafting exception summaries — completes in under 30 seconds per facility with this workflow. The five-ratio computation is deterministic: given the same sanction schedule and compliance certificate inputs, the PASS / WATCH / BREACH classification and headroom figures are identical on every run.
The 10% WATCH band surfaces any ratio within striking distance of its threshold 30–45 days before a BREACH would materialise. That window gives the CFO and treasury team time to reduce debt, accelerate receivables collection, or seek a temporary waiver — before the lender’s credit team classifies the account as SMA-0 under RBI Master Direction on Stress Asset Classification.
Every session produces a timestamped Excel compliance pack — five thresholds, five actuals, five headroom values, and a status column — plus a structured exception log. The artifact maps directly to the statutory audit workpaper file for Ind AS 1 paragraph 25 going-concern assessments and can be submitted to the lender’s relationship manager as supporting documentation, replacing a manually assembled spreadsheet.
The PASS / WATCH / BREACH classification is fully deterministic: given the same sanction schedule and certificate inputs, the workflow produces identical results on every run, regardless of which analyst runs it or which quarter is being tested. This eliminates the across-analyst variance that is the primary source of disputes under ICAI SA 500 (Audit Evidence) when auditors reconstruct the client’s covenant testing workpapers.
Questions treasury controllers and statutory auditors ask most often before deploying automated covenant compliance tracking.
Upload two files for the testing period: the Sanction Covenants schedule (.xlsx, one row per facility with the sanctioned thresholds) and the Compliance Certificate register (.pdf, the CFO-certified quarterly actuals). Cadel classifies each automatically and matches every certificate to its facility on facility_id, so you can drop them together without pre-labelling files.
Five standard Indian term-loan covenants: DSCR = EBITDA ÷ Total Debt Service; Debt/EBITDA = Total Debt ÷ EBITDA; Interest Coverage = EBITDA ÷ Interest Expense; Current Ratio = Current Assets ÷ Current Liabilities; and TOL/TNW = Total Outside Liabilities ÷ Tangible Net Worth. Thresholds and direction (floor vs cap) are read directly from the sanction schedule, so no manual re-keying is required for any facility.
A covenant is classified WATCH when the actual ratio is within 10% of the breach threshold but has not yet crossed it. For a floor such as DSCR ≥ 1.25x, the WATCH band is any reading between 1.125x and 1.25x; for a cap such as Debt/EBITDA ≤ 3.00x, it is between 2.70x and 3.00x. WATCH does not constitute a default but prompts management to notify the lender proactively — standard practice under most RBI-regulated loan documentation and best practice under Ind AS 1 paragraph 25 going-concern disclosures.
Each facility runs eight validation checks. Covenant breaches (DSCR, Debt/EBITDA, Interest Coverage, Current Ratio, TOL/TNW) and facility-ID mismatches are raised as FAIL exceptions; a certified ratio that disagrees with the recomputed value by more than 0.05, or a certificate filed beyond the 45-day post-quarter window, is raised as a WARNING. Every exception names the rule that tripped and links to the source row, supporting the statutory auditor’s review under ICAI SA 500 (Audit Evidence).
Cadel raises a FAIL exception and flags that a lender notification is required within the cure period from the sanction letter (30 days in the demo). It does not send correspondence to the lender directly; notification remains the borrower’s legal obligation under the loan agreement. The exception appears with a due-date countdown, and the Excel export includes a breach summary the CFO can attach to lender communication — satisfying the proactive disclosure expected under SEBI LODR Regulation 30 for listed entities.
Yes. The sample portfolio is 60 facilities across the Acme group and three lenders (Acme Bank Ltd, Acme Commercial Bank, Acme Finance) in a single quarter. Each facility is identified by the facility_id field and tracked independently, so the Dashboard shows covenant status per facility. Cross-facility borrowing-base constraints or intercreditor agreement covenants are not yet automated and would require a custom workflow configuration.
The workflow is document-driven: it ingests the covenant schedule and the certificate register, both standard exports from any ERP or manual close process, with no direct API integration. Controllers using Tally Prime, SAP S/4HANA, or Oracle NetSuite export their quarterly financials, certify the actuals in the standard CFO format, and upload to Cadel — the extraction engine reads the figures regardless of source system.
No. Your documents are processed only to produce this workflow’s covenant results and are not used to train any model. All uploaded sanction schedules and compliance certificates are treated as confidential borrower financial data and are processed in an isolated session.