← Back to the signal library
C4

Cascading Liquidity Failure

Composite / composite / Immediate

What it detects

A combination of immediate liquidity risks creates a scenario where multiple failure modes can activate simultaneously.

When it fires

Liquidity Shock Risk (S3) + (Collections Deterioration OR Customer Concentration) + Runway below critical threshold

Why it matters

Each of these liquidity risks is survivable on its own, but this composite fires only when several hit at the same time, and simultaneous pressure is what turns a hard stretch into a genuine crisis. When short runway, slow collections or heavy client concentration, and failing stress scenarios all line up, one more bad event can cascade into the next with no slack left to absorb it. That convergence is the warning: the individual problems are no longer independent, they are compounding, and the timeline to a cash emergency is much shorter than any single signal suggests.

What it looks like in practice

Runway is [redacted] months. Your biggest client ([redacted]% of revenue) has $[redacted]K in AR at [redacted] days past due. Two of eight stress scenarios produce emergency-level runway. If the big client pauses payment for another month, you enter the red zone. If they churn, you're in crisis within [redacted] days.

Severity levels

  • CRITICAL

Thresholds

Exact thresholds, formulas, and severity bands are omitted from this public view. The full methodology, with every figure, is available in the authenticated app.

How it connects

Cash operations become unrecoverable when the first shock hits — there is no buffer to absorb a second concurrent event. Worst-case scenario runway is [redacted] months.

Why these together

Liquidity Shock Risk says the stress scenarios already push runway to a critical level; slow collections or a concentrated client list says a single counterparty can trigger that shock; a short runway says there is no buffer to absorb it. Any one of these is survivable. Together they mean the first bad event cascades into the next with no slack left, which is why this composite fires only when Liquidity Shock Risk is at high or critical severity, at least one of Collections Deterioration or Customer Concentration is active, and runway is below the composite's own runway gate.

Built from these checks

  • Liquidity Shock Risk: the scenario read. It must be at high or critical severity, establishing that the stress presets already push runway to a critical level.
  • Collections Deterioration: one of the two counterparty reads. Slowing collections is a trigger that can start the cascade; either this or Customer Concentration must be active.
  • Customer Concentration: the other counterparty read. A large client pausing or leaving is the other trigger; either this or Collections Deterioration must be active. The runway gate itself reads the runway figure, not the Runway Compression signal.

Sources

SEE IT ON REAL NUMBERS

The exact thresholds, the formula, and your own figures are in the authenticated app. See it against a real, simulated dataset for Integra Executive Services, our public demo company, or connect your own QuickBooks Online account.

Get accessSee the nightly proof