Project finance implementations are among the most complex in commercial banking — not because the technology is hard, but because the domain is deep and specialised. DSCR, DSRA, TRA waterfall, covenant testing, DCCO extensions — these are not generic loan concepts with different labels. They are distinct mechanisms that behave differently in edge cases, and those edge cases are precisely what most UAT plans omit.
DSCR: The Ratio Everyone Tests Wrong
DSCR (Debt Service Coverage Ratio) is the primary financial covenant in project finance. It is computed as CFADS (Cash Flow Available for Debt Service) divided by Debt Service for the period. Most UAT plans test that DSCR is computed and displayed. Almost none test the covenant breach workflow — what happens when DSCR falls below the floor.
When DSCR breaches the covenant level (typically 1.20x), the system must generate a breach notification to the MLRO and credit team within prescribed timelines, trigger the distribution lock-up (no cash to sponsors), start the 30-day cure period clock, and escalate to EoD if uncured. That is five distinct system behaviours that all follow from a single DSCR computation. One test case ("DSCR computed correctly") covers none of them.
DSCR semi-annual covenant test — breach at 1.18x (below 1.20x floor), 30-day cure period, lender notification within 5 business days. Distribution lock-up trigger — DSCR below threshold, sponsor distributions blocked. Debt service partial payment shortfall — DSRA drawdown activated.
DSRA: The Reserve Account Nobody Tests End-to-End
The Debt Service Reserve Account must be funded at financial close (typically 6 months of debt service), maintained at minimum balance throughout the loan life, drawn when revenues are insufficient for debt service, and replenished within 90 days of a drawdown. That is a complete lifecycle — establishment, maintenance, drawdown, and cure — and most UAT plans test only the establishment step.
The drawdown scenario is particularly important: revenues fall short, DSRA is drawn, balance drops below minimum, sponsor is obligated to top up within 90 days. If they don't, it triggers an Event of Default. The system must track all of this — balance monitoring, cure period clock, EoD trigger — automatically.
DSRA establishment and minimum balance at financial close. DSRA drawdown — revenue insufficient for debt service, 90-day cure period, EoD trigger if unreplenished. Annual auditor certificate confirming DSRA minimum balance.
TRA Waterfall: Order Matters
The Trust and Retention Account waterfall defines the priority of payments from project revenues: O&M costs first, then debt service, then DSRA top-up, then major maintenance reserve, then sponsor distributions. The waterfall is contractual and must be enforced by the system — any distribution to sponsors before DSRA is at minimum is a breach of the facility agreement.
UAT plans for project finance systems frequently test each waterfall step in isolation. They rarely test the sequence — particularly what happens when revenues are insufficient to fund all steps, and the system must correctly prioritise and partially fund higher-priority items before lower-priority ones receive nothing.
Cash waterfall — payment priority O&M → debt service → DSRA → MMRA → distribution. DSRA top-up priority — no sponsor distribution until DSRA at minimum balance confirmed.
The DCCO Extension — A Purely Indian Scenario
India's RBI permits infrastructure project DCCO (Date of Commencement of Commercial Operations) extensions of up to 2 years without triggering NPA classification, provided interest is being serviced. This is a significant concession — and a significant compliance test. The system must track the original DCCO, the revised DCCO, confirm interest service throughout the extension, protect asset classification, and report the revision to RBI. Most project finance systems implemented in India do not test this scenario at all.