The waterfall is the priority of payments clause executed on every payment date. Cash collected during the period flows in and is distributed in a strictly defined sequence. No item lower in the priority list receives anything until every item above it is satisfied in full. When cash runs out mid-waterfall, everything below that point receives zero — that period.

The waterfall is not a suggestion — it is a legal contract. The trustee executes it mechanically based on the servicer's certified figures. Disputes about whether a covenant was in breach, or whether an item should have been paid, are resolved by reference to the exact indenture language. This is why the definitions section (Article I) and the priority of payments section (Article IV) are the two most critical sections to have memorised.

Two important structural variations affect how the waterfall behaves: combined vs. split waterfall (some deals run interest and principal as two separate sequential waterfalls — interest paid to all classes first, then principal; others combine them so Class A principal must be fully repaid before any junior interest is touched) and OC reinstatement mechanics (if the OC ratio is below target, available principal is diverted to repair OC before being passed to junior noteholders — this is effectively a cash trap that accelerates senior paydown when the pool is under stress).

Every ABS deal operates on a strict monthly calendar. Collections are gathered during a collection period, calculated on a determination date, and distributed on a payment date. Miss any step or miscalculate any date and the deal is in technical breach.

The standard sequence for a monthly-pay auto ABS: the collection period runs from the last business day of month T−1 to the last business day of month T. The determination date is typically the 15th calendar day of month T+1 — the servicer has this time to tally collections, calculate pool statistics, and prepare the servicer report. The record date is the business day before the payment date — noteholders of record on this date are entitled to that month's distribution. The payment date is typically the 15th or 16th calendar day of month T+1 (often the same day as or one day after the determination date).

This 45–50 day lag between when an obligor makes a payment and when the noteholder receives their distribution is structural — it's the time required to aggregate, verify, and remit. During this lag, the servicer holds the collected funds in a segregated collection account. Commingling risk: if the servicer mixes these funds with its own operating cash, a servicer insolvency during the lag period could mean noteholders never get their distributions. This is why daily or weekly sweeps from the servicer's collection account to the trust's segregated account are a key covenant.

Click each date on the timeline below to see exactly what happens on that day.

The determination date is when the servicer runs all the numbers for that payment period. Every figure in the servicer report and the waterfall calculation starts here. This is the most calculation-intensive day in the deal administration cycle.

The servicer must compute: (1) Available funds — total collections in the collection account (interest, principal, prepayments, recoveries) minus any amounts exempt from distribution, (2) Pool balance — beginning balance minus scheduled principal collected, prepayments, and defaults during the period, (3) Delinquency buckets — number and dollar amount of loans 30+, 60+, 90+ days past due, (4) Defaults and recoveries — loans that crossed the charge-off threshold during the period; recovery amounts received, (5) CNL ratio — cumulative net losses since deal close divided by original pool balance, (6) OC ratio — current pool balance minus outstanding note balance, divided by pool balance, (7) Reserve account balance — current balance vs. required minimum, (8) Covenant tests — is the CNL ratio below the trigger table? Is delinquency below the threshold? Is OC above the floor?, (9) Waterfall inputs — interest accrued on each class, scheduled principal per class, OC reinstatement amount if needed, reserve top-up if needed.

These calculations must be certified by a servicer officer — the "officer's certificate" is the servicer's attestation that all figures are accurate and all covenants are in compliance. For public deals, this certificate is required under Reg AB II. For private deals, it's a contractual requirement in the SSA. A false certification is not just a breach of contract — it's potentially fraud.

The servicer report is the primary data output from every payment period. It is the input to the waterfall, the source of covenant compliance checks, and the basis for all investor reporting. For public deals, it's published on Bloomberg and accessible to all noteholders. For private deals, it's typically a PDF or Excel file emailed directly to the fund and trustee/collateral agent.

A complete servicer report contains: pool statistics (beginning and ending balance, WAC, WAM, number of loans), collection activity (interest collections, principal collections, prepayments, gross defaults, recoveries), delinquency table (30/60/90/120+ day buckets by count and balance), note balance schedule (outstanding balance per class, principal paid this period), reserve account status (beginning balance, draws, deposits, ending balance), OC and coverage ratios, covenant compliance certificate (pass/fail on each test), and interest and principal distribution amounts per class.

Validating the servicer report means cross-checking internally consistent: does beginning balance + new additions − principal collected − defaults = ending balance? Does the CNL ratio in the certificate equal cumulative net losses ÷ original pool balance? Do the distribution amounts match what a waterfall run produces from the reported available funds?

Red flags in a servicer report: (1) Pool balance declining faster than CPR + CDR assumptions would predict — possible misclassification of delinquencies as current. (2) Recovery amounts unusually high in one month — possible timing manipulation (pulling forward future recoveries to mask current losses). (3) Delinquency counts inconsistent with prior month roll-rate — if 60+ day bucket shrinks while 30+ day grows, the servicer may be extending payment terms without proper disclosure.

Performance triggers are pre-defined thresholds that, when breached, change the deal's behaviour — typically by directing more cash to senior noteholders at the expense of junior and equity. They are the deal's self-correcting mechanism: as performance deteriorates, the structure automatically deleverage.

There are two types: soft triggers (also called performance triggers or amortisation triggers) change the waterfall mechanics without declaring a default — typically activating turbo principal payment to Class A. Hard triggers (also called early amortisation events or rapid amortisation events) end any revolving period and switch the deal to accelerated sequential principal repayment. Neither is an Event of Default — the deal is still performing, just under a modified distribution regime.

The most common trigger metrics: CNL trigger table (the allowed CNL ratio steps up over the deal life — e.g., 1.5% in months 1–12, 2.5% in months 13–24, 3.5% in months 25–36 — because losses naturally accumulate over time), delinquency ratio trigger (60+ or 90+ day delinquencies as % of current pool balance — typically 3–5% for prime auto), and reserve account floor (if the reserve drops below the required minimum and cannot be topped up from excess spread, a hard trigger trips).

The CNL trigger table is particularly important to understand. It is not a fixed number — it steps up as the deal ages because losses accumulate over time and the table is designed to catch abnormal acceleration rather than the normal buildup of losses. A CNL ratio that tracks just below the trigger table every month is not "passing" — it's a yellow flag that the deal is performing at the edge of its structural tolerance.

An Event of Default (EoD) is a qualitatively different animal from a performance trigger. A trigger changes the waterfall mechanics. An EoD puts the deal in formal default — noteholders have the right to accelerate, and the trustee is obligated to take enforcement action. This is the nuclear option in ABS, rarely invoked, because acceleration on an amortising pool triggers a forced wind-down that is rarely in anyone's economic interest.

Standard EoD events in an auto ABS indenture: (1) Failure to pay interest to Class A noteholders on any payment date and failure to cure within 5 business days, (2) Failure to pay principal by the legal final maturity date, (3) Servicer default not cured within the contractual cure period (typically 60 days), (4) Bankruptcy or insolvency of the issuer/SPV, (5) Material misrepresentation in the servicer's officer's certificate that is not cured, (6) Failure to maintain required insurance on the collateral (for deals where insurance is required), (7) Rating agency downgrade to below investment grade of the senior tranche (in some deals).

Upon an EoD: the trustee may declare the notes immediately due and payable (acceleration). The trustee can also, if directed by the requisite percentage of noteholders (typically 25–51% by outstanding balance), sell the collateral, apply all collections to senior principal, and wind down the deal. In practice, noteholders rarely direct acceleration on a performing pool — the economic value of continuing to collect cash flows typically exceeds the proceeds of a forced sale at distressed pricing.

The distinction between "servicer default" (Article VIII) and "Event of Default" (Article VI) is critical: a servicer default triggers servicer replacement but does not trigger EoD rights against the notes. Only if the servicer default is not cured within the contractual cure period does it escalate to an EoD.