InsightsCase Studies
Management ConsultingExecution Mandate

Loan Asset Certification and Fund Monitoring for an Infrastructure Finance Company

Certification of a portfolio of approximately INR 7,300 Crore, with fund monitoring of approximately INR 400 Crore, delivered as method rather than as judgment

By Portfolio Certification & Fund Monitoring•September 2026•6 MIN READ
Client & Engagement
Infrastructure finance company requiring independent certification across a lending and investment portfolio
Industry Sector
Sustainable Energy and Power Value Chain Financing
Jurisdiction & Geography
India
Practice Leadership
Portfolio Certification & Fund Monitoring
Mandate Performance Metrics
Certification ScopeINR 7,300 CrLoan asset certification mandate
Fund MonitoringINR 400 CrDisbursed funds tested for end use
TraceabilityAsset LevelEvery asset retraceable to its own evidence
Method StandardRepeatableStandardised across the asset population for reuse

Executive Mandate Summary

An infrastructure finance company required independent certification of loan assets across a portfolio of approximately INR 7,300 Crore, fund monitoring of approximately INR 400 Crore in disbursed funds, and portfolio-level due diligence. At this scale, the binding constraint is method, not analytical capability. The engagement was designed as a standardised review applied consistently across the asset population, with evidence retained under each asset's own reference so that any single asset could be defended months later by someone who was not part of the original team. Exceptions were classified by type and severity against an agreed taxonomy and escalated in priority order.

Key Transaction & Governance Challenges

  • •
    A portfolio of INR 7,300 Crore cannot be certified credibly by exercising judgment asset by asset. Two reviewers reach different conclusions on similar assets, the basis of each conclusion is unrecorded, and the certification becomes indefensible the moment any single asset is questioned.
  • •
    The method must accommodate variation across asset types without losing comparability. A checklist that works for a power project must also work for a logistics asset, or the population-level certification loses its consistency.
  • •
    The basis for each asset must be retained and retrievable, because certification supports institutional decisions and potentially external reliance. A certification that cannot be evidenced at asset level is a liability rather than an asset.
  • •
    Tracing end use against sanctioned purpose requires reaching past utilisation certificates to the underlying application of funds. It is the control most institutions specify in policy and least reliably evidence in practice.
  • •
    At this volume, an unclassified exception list is functionally the same as no exception list, because the institution cannot sequence its response. Exceptions must arrive pre-classified and pre-prioritised.
  • •
    The method must be transferable to the next cycle and the next team. An approach that depends on the original reviewers' institutional memory cannot sustain a recurring certification mandate.

Northrop Execution Architecture & Methodology

1
Review methodology defined against certification requirements, asset-level checklist built, exception taxonomy and severity classification agreed with the institution. The method was designed before any asset was touched.
2
Method applied to a pilot asset population, calibrated for heterogeneity across asset types. Checklist refined before full rollout, so that teams that began the population review were working from a tested approach rather than from a draft.
3
Asset-level review across the certified population against an identical checklist: sanction terms, documentation completeness, security creation and perfection, conformity between sanction and disbursement, current status. Fund utilisation tested against sanctioned purpose within the monitoring scope.
4
Portfolio-level analysis of concentration by borrower, group, sector and geography, and asset quality distribution. Exceptions classified by type and severity against the agreed taxonomy and escalated in priority order. Certification support pack assembled.

The question behind the mandate

How do you certify a portfolio of this size so that any single asset in it can be defended on its own evidence, months later, by someone who was not there?

At this scale the binding constraint is not analytical capability. It is method. A portfolio of approximately INR 7,300 Crore cannot be certified credibly by exercising judgment asset by asset, because judgment does not replicate: two reviewers reach different conclusions on similar assets, the basis of each conclusion is unrecorded, and the certification as a whole becomes indefensible the moment any single asset is questioned. The engagement was therefore designed as a standardised review applied consistently across the asset population, with the evidence for each asset retained under its own reference.

The analytical spine

Four workstreams ran across the mandate. The first three operated at asset level; the fourth aggregated them into a position the institution could act on.

Each asset was reviewed against a defined checklist covering sanction terms, documentation completeness, security creation and perfection, conformity between sanction and disbursement, and current status. The checklist was identical across assets, which is what makes the population comparable and the certification defensible. Disbursed funds within the monitoring scope were tested for utilisation against sanctioned purpose, tracing application to project or business use. Above the asset level, the portfolio was analysed for concentration by borrower, group, sector and geography, and for asset quality distribution, because portfolio-level risk is not the sum of asset-level risk and correlated exposure can produce loss patterns no individual review would predict. Exceptions were classified by type and severity against an agreed taxonomy and escalated on that basis rather than as an undifferentiated list.

What made the difference

Three disciplines separated this engagement from certification work that collapses when a single asset is questioned.

First, method before volume. The review approach was defined and piloted before rollout. Teams that begin reviewing immediately produce a large volume of inconsistent work, and inconsistency at this scale cannot be corrected retrospectively without redoing the population.

Second, defensible asset by asset. Certification was designed to be tested at the level of a single asset, because that is how it will be challenged. Aggregate assurance collapses the moment one asset is questioned and the basis for it cannot be produced.

Third, exceptions built for action. Exceptions were classified and prioritised against an agreed taxonomy, so the institution received a sequenced response rather than a list. This is the difference between a report that is read and one that is implemented.

Consider this work if you are facing

A loan asset portfolio requiring independent certification with external or board-level reliance. Disbursed funds where end use against sanctioned purpose has not been independently tested. A portfolio large enough that manual judgment produces inconsistent conclusions. Concentration or correlated sector exposure that asset-level review would not surface. A prior certification exercise that could not be evidenced when a single asset was questioned. A recurring certification cycle where each round currently starts from scratch. Regulatory, lender consortium or investor pressure for independent portfolio verification.

Verifiable Institutional Outcomes & Value Realized

  • Every asset in the certified population retraceable to its own evidence, independently of the original team. The certification designed to be tested at the level of a single asset, because that is how it will be challenged.
  • Disbursed funds within the INR 400 Crore monitoring scope tested for application against sanctioned purpose, producing a verified position on whether the institution's end-use discipline is operating in practice or only in policy.
  • Exceptions classified and prioritised against an agreed taxonomy, so the institution received a sequenced response rather than an undifferentiated list. The difference between a report that is read and one that is implemented.
  • Documented review method handed over for reuse, so that the second certification cycle costs less than the first and does not start from scratch.
Portfolio Certification & Fund Monitoring

Portfolio Certification & Fund Monitoring

Founder and Managing Director
Private Mandate Advisory Desk

Facing a Similar High-Stakes Transaction or Turnaround?

Northrop partners execute buy-side due diligence, fraud forensics, and financial restructuring with strict board confidentiality and unmatched technical rigor across Indian jurisdictions.

Next Documented MandateManagement Consulting

Case Study: Ghost Trainees and Unverified Placements in a Skill Development NGO

A skill development NGO reported that 1,200 youth had been trained and 840 placed in jobs under a programme funded through a ₹1.4 crore CSR contribution. The reported 70% placement rate prompted an independent review of beneficiary records, training delivery, placement claims and programme expenditure. Northrop Management Private Limited conducted a forensic verification covering beneficiary deduplication, attendance records, direct beneficiary calls, employer confirmations, offer letters, salary claims and the underlying financial trail.

View Full Mandate Record