Securitisation Under RBI Master Direction 2021: PTC Issuance End-to-End

Securitisation is back. Indian NBFCs are running into liability-side constraints — borrowing rates moved, deposit-funded competition intensified, and the path to scaling assets-under-management without bloated balance-sheet leverage runs through the securitisation market. The RBI Master Direction on Securitisation of Standard Assets (September 24, 2021) is the regulatory framework that governs every PTC issuance, and operationalising it is non-trivial.

This post is for treasury, structuring, and platform-engineering teams at NBFCs (and increasingly, banks and SFBs) standing up their first PTC issuance — or their tenth, where the pain points have only gotten more visible.

What the 2021 Master Direction actually requires

The 2021 framework consolidated three years of post-IL&FS regulatory thinking. Headline rules that matter for implementation:

• MRR (Minimum Retention Requirement): the originator retains a minimum economic interest in the pool — typically 5-10% of the pool, depending on structure. This survives the entire issuance lifecycle.
• MHP (Minimum Holding Period): loans must be on the originator’s book for a minimum period before being securitised — typically 3 months for retail, 6 months for non-retail. Earlier transfer = no MRR-MHP-compliant issuance = no securitisation.
• True sale: the assets transfer legally and economically. The originator cannot retain control beyond the MRR portion. Audit trail of the transfer is non-negotiable.
• Pool eligibility: prescribed exclusions — restructured loans, NPA loans, loans pending RBI inspection findings, etc.
• Tranching constraints: senior / mezzanine / subordinate / equity, with concentration limits per tranche class.
• Disclosure regime: at issuance and ongoing — pool composition, performance, MRR continuance, exception events.

Each of these requires specific platform plumbing. Let’s walk through an issuance end-to-end.

Phase 1: Pool selection and eligibility check

The structuring team identifies a candidate pool: ₹500 Cr of housing loans, average ticket ₹35 lakhs, average seasoning 18 months, geography concentrated in Karnataka + Tamil Nadu, all current.

What the platform must do:

• Apply RBI eligibility filter: drop NPAs, restructured loans, loans under inspection, loans in cooling-off, loans with MHP < 90 days for retail (or 180 days for non-retail). The drop-rate is often 8-15% of the gross pool. Surprises here lead to under-sized issuances.
• Compute concentration metrics: single-borrower, single-state, single-product, single-vintage. Most disclosure regimes require certain concentration caps (e.g. under 10% to single borrower, under 30% in single state for some tranching structures).
• Compute pool weighted-average characteristics: weighted-average maturity, weighted-average yield, weighted-average LTV. These flow into the rating agency’s analysis and the investor disclosure.
• Snapshot the pool: the issuance date pool composition is the pool for the lifetime of the PTC. Snapshotting needs to be byte-exact and auditable.

CortexData PTC ships RBI-compliant pool eligibility filters as default behaviour. Pool selection drops to a UI workflow that the structuring team operates directly.

Phase 2: Tranche structuring

The structuring team designs the tranche stack. Typical retail PTC:

• Senior tranche: 80-85% of the pool, AAA-rated, ~7.5% yield.
• Mezzanine tranche: 8-10% of the pool, A-rated, ~10% yield.
• Subordinate tranche: 5-7% of the pool, BB-rated, ~14% yield.
• Equity / first-loss tranche: 2-3% of the pool, retained by originator (the MRR).

Each tranche has its own waterfall position: senior gets paid first from every collection, then mezzanine, then subordinate, with equity absorbing first losses. The platform encodes the waterfall as code, runs it on every collection day, and updates investor positions atomically.

What kills issuances at this phase:

• Waterfall ambiguity: legal documents say one thing, the issuance memorandum says another, the model in the structurer’s Excel says a third. We’ve seen issuances where the first month’s payment showed three different distributions in three different systems. Investors lose confidence fast.
• Cash-trap logic: if performance triggers fire (delinquency above threshold, prepayment above threshold), the waterfall traps cash to senior. The conditions are precise and must be enforced atomically.

Phase 3: True sale and transfer

This is the legal-economic moment. The originator transfers ownership to the securitisation trust (typically a trust or SPV). Documentation includes:

• Asset transfer deed.
• Receivables purchase agreement.
• Trustee appointment.
• ISIN allocation (for listed PTCs).

What the platform tracks:

• The exact loans transferred, byte-exact, with their state at transfer time.
• The originator’s retained MRR (typically the equity tranche, plus any first-loss credit enhancement).
• The trustee’s oversight workflow.
• The servicing arrangement: who collects EMIs (typically the originator continues), who reports performance, who handles defaults.

The transfer creates two sets of books: the originator’s book (which now reflects the cash received from the issuance) and the trust’s book (which holds the pool and the PTC liabilities). Both need to be reconciled daily.

Phase 4: Investor onboarding

PTCs are sold to qualified investors:

• Mutual funds, pension funds, insurance companies (DII).
• Foreign portfolio investors (FPIs, with FEMA constraints).
• Banks (subject to their securitisation exposure caps).
• HNIs in certain structures.

The platform needs:

• KYC and AML for each investor.
• Suitability assessment: the investor’s risk profile vs. the tranche they’re buying. Selling subordinate tranches to retail HNIs without explicit suitability documentation is a SEBI risk.
• FPI eligibility: FPI investments in PTCs are subject to specific FEMA regulations and sectoral caps.
• Allotment workflow: bid receipt, pro-rata allotment if oversubscribed, certificate generation.
• Demat onboarding: NSDL or CDSL integration for dematerialised PTCs.

Phase 5: Cash-flow management and the monthly waterfall

This is where most platforms break.

Every month, the originator (acting as servicer) collects EMIs from underlying borrowers. The collections aggregate into a trust account. On the payment date:

1. Senior tranche gets paid its scheduled coupon + scheduled principal.
2. Mezzanine tranche gets paid its coupon + principal, if senior obligations are met and triggers haven’t fired.
3. Subordinate tranche gets paid, if senior + mezzanine are current and triggers haven’t fired.
4. Equity tranche (originator) gets the residual.

Triggers that re-route cash:

• Delinquency trigger: if 30+ DPD exceeds X% of pool, all cash goes to senior until the trigger cures.
• Prepayment trigger: if cumulative prepayments exceed Y% of pool, modify the waterfall.
• Servicer-event trigger: if the originator’s rating downgrades, the trustee may take over servicing.

Each event is a state transition in the platform. Each transition updates investor positions atomically. Each transition is audit-logged.

Phase 6: Ongoing reporting and MRR continuance

The 2021 framework requires ongoing disclosure:

• Monthly investor pack: collections, distributions, pool performance, prepayment rate, default rate.
• Quarterly RBI securitisation report: aggregate originator-level securitisation activity, MRR continuance, performance.
• Material-event notification: trigger events, servicer changes, rating changes.

CortexData PTC generates the investor pack and the RBI quarterly report from the source-of-truth platform data — not from a parallel reporting database that drifts.

Compliance traps we keep seeing

After a few years of working with NBFC structuring teams, here are the patterns that keep going wrong:

1. MHP miscalculated: confusion between the disbursement date and the loan’s effective book date. Loans transferred too early get disqualified by RBI’s post-issuance review.
2. MRR continuance unmonitored: the originator’s MRR can be eroded if equity-tranche performance is poor. Continuous monitoring is required, not just an issuance-time check.
3. True-sale documentation incomplete: in haste to close issuance, originator retains some economic interest beyond the MRR (e.g. cash-flow guarantees, performance call options). RBI views these as “control retained” → not a true sale → not a compliant securitisation.
4. Investor reporting drifts from platform reality: investor pack is generated from a parallel Excel that the structurer maintains. Months later, the Excel drifts from the platform’s actual collections. Investor finds the discrepancy, files an SEBI complaint, the issuance is at risk.
5. Tranche concentration breached: secondary trading takes a tranche above its concentration cap. Without platform enforcement, this is unnoticed until the next disclosure cycle.

The platform-side imperative

Treasury and structuring teams that have CortexData PTC typically launch their next issuance in 6-8 weeks (vs. 4-6 months without a platform). The reason isn’t novel: every operational primitive in this post — pool eligibility, MRR/MHP enforcement, waterfall-as-code, investor onboarding, monthly distribution, RBI reporting — is built and battle-tested in the platform.

If you’re structuring your next issuance, request a demo. We’ll walk through your pool on the platform and show you the eligibility, structure, and reporting end-to-end.