A cross-default clause is a contract provision under which a default on specified other indebtedness can create a default or Event of Default under the agreement being reviewed. It connects separate obligations so lenders do not have to wait for a borrower to miss payment on each facility before obtaining contractual rights.
The clause does not necessarily make every loan immediately payable. Thresholds, covered entities, grace periods, notice, lender voting, waiver, and acceleration provisions determine the actual consequence.
Key Takeaways
- Cross-default is defined by the contract; there is no single universal trigger.
- The clause commonly applies only to Material Indebtedness above a stated threshold.
- It may cover payment defaults, other defaults that permit acceleration, or both.
- Cross-acceleration is narrower when it requires the other debt to be accelerated or become due early because of default.
- A trigger can create an Event of Default without automatic acceleration.
- Waiving the original default does not automatically waive a resulting default under another agreement.
- The most useful analysis is a contract-by-contract matrix of obligors, debt, thresholds, cures, triggers, and remedies.
How the Clause Works
A typical sequence is:
- The borrower or a covered subsidiary breaches another debt agreement.
- Any notice and cure period under that other agreement runs.
- The cross-default clause is tested against its own definition of Indebtedness, Material Indebtedness, threshold, obligors, and exclusions.
- If the test is met, a Default or Event of Default arises under the reviewed agreement.
- The agreement’s remedy provisions determine whether lenders can stop further draws, charge default interest, control cash, accelerate, or enforce collateral.
- Required lender voting and notice rules determine who can take action.
Some agreements treat specified insolvency or bankruptcy events as automatic Events of Default. Payment and covenant cross-defaults often have more contractual steps. The final executed document and applicable law control.
Cross-Default vs. Cross-Acceleration
| Provision | Trigger | Relative breadth |
|---|
| Cross-default | A specified default exists under other covered debt, often after grace periods and above a threshold | Can trigger before the other debt is accelerated |
| Cross-acceleration | Other covered debt is accelerated or becomes due before scheduled maturity because of default | Usually requires an additional enforcement or automatic-acceleration event |
The labels are not enough. A clause titled cross-default may contain cross-acceleration language, and a provision can combine both tests.
Clause Components
Covered Indebtedness
The definition may include loans, notes, bonds, finance leases, guarantees, reimbursement obligations, and derivatives, while excluding trade payables, intercompany debt, nonrecourse debt, or disputed obligations. Terms capitalized in the clause must be traced to their definitions.
Covered Obligors
The clause may cover only the borrower, the borrower and guarantors, Material Subsidiaries, or the entire corporate group. Debt at an uncovered subsidiary may not trigger the provision even if consolidated financial statements include it.
Threshold and Aggregation
A minimum amount limits immaterial cascades. The threshold may apply to one obligation or the aggregate principal amount of several defaults. Currency-conversion rules and timing can matter.
Trigger Standard
Some clauses trigger only for nonpayment after a grace period. Others include any default that permits holders of the other debt to accelerate. Cross-acceleration clauses require actual or automatic early maturity under defined conditions.
Remedy and Voting
An Event of Default can block new borrowing immediately yet require a specified lender majority to accelerate. Bond indentures may use trustee and holder-direction mechanics. Collateral enforcement can have separate notice, standstill, and intercreditor rules.
Worked Example: Threshold, Cure, and Acceleration
Assume a company has:
- Facility A: $50 million revolving loan with a $10 million Material Indebtedness threshold.
- Loan B: $25 million term loan with a 15-day payment grace period.
- Lease C: $3 million obligation.
First, the company misses a payment under Lease C. Even if that failure is a default, the $3 million obligation is below Facility A’s $10 million threshold, so the assumed cross-default does not trigger.
Later, the company misses a payment under Loan B. During Loan B’s 15-day grace period, assume its payment default has not yet matured into the condition specified by Facility A. If the payment remains uncured after day 15, the $25 million principal amount exceeds the threshold and an Event of Default arises under Facility A.
Facility A is not automatically due solely because the Event of Default exists. Assume holders of more than 50% of commitments must direct acceleration. Until they do, further borrowing may be blocked and default interest or other rights may apply according to the contract.
If Facility A used a cross-acceleration clause instead, the trigger might not occur until Loan B’s lenders actually accelerate Loan B or it otherwise becomes due early under the defined language.
This is an illustrative contract, not a statement of any standard form or legal outcome.
Why Lenders Use Cross-Default
The clause can provide early warning and prevent one creditor group from enforcing while another remains contractually unable to respond. It can also bring lenders into a coordinated waiver, forbearance, or restructuring discussion.
The protection has limits. Broad triggers can create a liquidity cascade, reduce negotiation time, and give one small or disputed obligation disproportionate influence. Thresholds, cure periods, materiality, exclusions, and cross-acceleration language are common ways to define that risk.
Borrower and Creditor Analysis
Borrower Perspective
- Map all debt and guarantees to every cross-default definition.
- Centralize payment, covenant, and notice calendars.
- Monitor thresholds in the required currencies and aggregation periods.
- Address the original default and each connected agreement separately.
- Identify lender groups, voting requirements, and waiver conditions before a breach.
Creditor Perspective
- Verify that the other obligation and obligor are covered.
- Confirm the default survived applicable grace and was not cured or waived.
- Determine whether the clause creates a Default or Event of Default.
- Review draw stops, default interest, acceleration, collateral, and intercreditor limits.
- Assess whether enforcement preserves more value than a coordinated forbearance.
Risks and Limitations
- Cascade risk: One default can expose multiple facilities and create a sudden refinancing need.
- Definition risk: Capitalized terms, exclusions, and entity scope can produce a different result from a plain-language reading.
- Threshold risk: Aggregation and currency conversion can move obligations above or below the trigger.
- Waiver risk: A waiver may apply only to one agreement, event, period, or consequence.
- Acceleration risk: Different creditor groups can have different voting and enforcement incentives.
- Dispute risk: Whether a default occurred, remained uncured, or permitted acceleration may be contested.
- Liquidity risk: Draw stops and early maturity can create distress even when the borrower was current under the reviewed facility.
- Intercreditor risk: Standstills, turnover, collateral priority, and remedy-control provisions can limit practical enforcement.
How to Review a Cross-Default Clause
- Copy the operative clause and every incorporated definition.
- Identify covered debt instruments, obligors, subsidiaries, guarantees, and exclusions.
- Record thresholds, aggregation, currency, notice, and grace periods.
- Distinguish payment default, default permitting acceleration, and actual acceleration.
- Determine when a Default becomes an Event of Default.
- Map draw stops, default interest, acceleration votes, collateral remedies, and automatic events.
- Check waivers, amendments, forbearance, and intercreditor restrictions across all agreements.
- Model the cash needed if each connected facility is blocked or accelerated.
Cross-default consequences depend on the executed documents and governing law. This article is educational and is not legal, lending, restructuring, or investment advice.
- Default: Failure to perform a contractual obligation.
- Loan Covenant: A contractual promise, restriction, or condition.
- Financial Covenants: Quantitative tests tied to borrower financial measures.
- Acceleration: Making debt due before scheduled maturity under contractual rights.
- Liquidity Crisis: Acute inability to meet time-sensitive cash obligations.
- Refinancing: Replacing existing debt with new funding.
Primary Documents and Official Sources
FAQs
Does a cross-default automatically accelerate every loan?
No. It may create a Default or Event of Default, but acceleration can require notice, lender voting, trustee action, or another contractual step. Some specified events can be automatic, so the document must be read in full.
What is the difference between cross-default and cross-acceleration?
Cross-default can trigger when a covered default exists under other debt. Cross-acceleration generally requires that the other debt has actually been accelerated or become due early because of default. Exact wording controls.
Can a small default trigger a cross-default clause?
It depends on the threshold, aggregation rules, covered debt definition, and grace period. Many agreements exclude obligations below a Material Indebtedness amount, but there is no universal threshold.