Cross-Default Clauses: How One Missed Payment Sinks Every Loan

In its basic form, a cross-default provision says that if you default on another specified obligation, whether that's a different loan, a material lease, or another named contract, the lender holding the cross-default clause can treat that as a default under its own agreement too, even though you've made every payment on that specific loan on time. The lender isn't waiting to see whether the other default actually affects your ability to pay them; the clause itself is the trigger, regardless of how minor or unrelated the original problem might turn out to be once it's actually resolved.

A lender's real concern is your overall financial health, not just performance on the specific agreement in front of them. A default elsewhere is often an early warning sign of broader trouble, and a cross-default clause lets a lender act on that signal, rather than waiting for the same trouble to eventually show up in missed payments on their own loan. From the lender's perspective, this is protective; from the borrower's, it means one problem can cascade into several agreements at once.

The scope of what counts varies enormously by how the clause is drafted. Some agreements limit the trigger to defaults on debt above a specified dollar amount; others sweep in any material contract default, or even an unpaid judgment against the company. A broadly drafted clause with no dollar threshold can technically be triggered by a genuinely minor dispute with a vendor, which is exactly the kind of language worth pushing back on before you sign, not after a small dispute unexpectedly cascades.

Read the definition of a triggering event as closely as you'd read the interest rate section, since this is one of the clauses most likely to be copied from a standard template without much thought from either side during a fast-moving closing.

Push for a dollar threshold below which a default elsewhere doesn't trigger the clause at all, so a genuinely minor issue can't cascade into a major one. Also push for a cure period that mirrors whatever cure period exists under the underlying obligation that defaulted, so you're not immediately in cross-default on this loan while you're still within your rights to cure the original issue elsewhere. Lenders will often agree to both if you ask before signing, since neither meaningfully weakens their real protection against genuine financial distress.

Before signing, ask for these protections:

• A dollar threshold below which a default elsewhere doesn't trigger the clause, so a minor issue cannot cascade into a major one.
• A cure period that mirrors the one under the underlying obligation, so you aren't in cross-default while still entitled to cure the original issue.
• A carve-out for obligations you are disputing in good faith, so an unresolved dispute alone cannot trigger default.
• A narrower trigger, such as cross-acceleration, that applies only once the other lender has actually accelerated its loan.

Once you have more than one lender, or meaningful obligations under leases and other material contracts, map out which agreements have cross-default clauses and what they're tied to. A single missed payment or dispute anywhere in that map can ripple across every agreement with a cross-default clause pointing at it, so knowing the full picture in advance, rather than discovering it mid-crisis, changes how urgently you treat a small problem the moment it appears.

Update the map every time you sign a new financing, lease, or major contract, not just once at the start of the year. A cascade risk that didn't exist six months ago can appear the moment a new agreement with its own cross-default language gets added to the pile, and a stale map won't show you that until it's already a live problem.

For example, suppose a company has a bank term loan, a venture debt facility and an office lease, each with its own cross-default language. A simple map lists every agreement in one column, what each cross-default clause points at in the next, and the cure period attached to it. A common mistake is treating a small vendor dispute as isolated. The fix is to check the map the moment a dispute or missed payment appears, identify which clauses it could touch, and call the affected lenders first with a plan. Name one owner for the map, such as the controller, so it gets updated with each new agreement.